---
title: "PUT Webhook Topic Subscription"
method: PUT
path: "/partner/webhooks/subscriptions/{topic_id}"
tags: ["Technology Partners Webhooks"]
---

# PUT Webhook Topic Subscription

`PUT /partner/webhooks/subscriptions/{topic_id}`

Use this PUT method to subscribe your application to a `topic_id` or to update the callback URI for an existing subscription. Possible `topic_id` values include:

 * `1` - Billing tier upgrade.
 * `2` - Billing tier downgrade.
 * `3` - Account cancelled.
 * `4` - Account disabled.

After you subscribe your application, Constant Contact will automatically start sending POST notifications for your chosen topic to your application's callback URI. This is an example of the POST notification request body:

  ```
  {"url":"https://api.cc.email/v3/partner/accounts/a07e1my9tbw0/plan",
  "api_key":"90ed8738-5190-44a3-bc12-c172930db12c",
  "event_type":"tier.increase"}
  ```
</br>
If your application does not return a success response after receiving a notification, Constant Contact will retry sending the POST notification at 1 minute intervals for up to an hour.

## Path parameters

- `topic_id` string, required

## Request body

- WebhooksSubscriptionBody
  - `hook_uri` string — The callback URI you would like to use to receive webhook notifications. Constant Contact will automatically send POST notifications about your chosen topic to this URI.

## Response `200`

Request successful.

- WebhooksSubscriptionPutResp
  - `topic_id` integer — Identifies the topic using an integer to indicate the type of topic.
  - `hook_uri` string — Your webhook callback URI. Constant Contact automatically sends POST requests to this URI to notify you about the topic.

## Other responses

- `400` — Bad request. Either the JSON was malformed or there was a data validation error.
- `401` — The Access Token used is invalid.
- `403` — Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
- `404` — The requested resource was not found.
- `500` — There was a problem with our internal service.

---

[API](https://skmtc.net/cc/apis/appconnect-v3.md) · [All operations](https://skmtc.net/cc/apis/appconnect-v3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cc/appconnect-v3/versions/4b4a534c818d/schema)