Skip to main content
PATCH
/
integration
/
subscriptions
/
v1
/
{subscription_id}
cURL
curl --request PATCH \
  --url https://api.mottostreaming.com/integration/subscriptions/v1/{subscription_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "subscription_id": "<string>",
  "subscription": {
    "project_id": "<string>",
    "name": "<string>",
    "topic_id": "<string>",
    "https_url": "<string>",
    "filter": "<string>",
    "delete_after_use": true
  },
  "update_mask": "<string>"
}
'
{
  "subscription": {
    "project_id": "<string>",
    "name": "<string>",
    "topic_id": "<string>",
    "https_url": "<string>",
    "id": "<string>",
    "filter": "<string>",
    "delete_after_use": true
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.mottostreaming.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
subscription_id
string
required

Body

application/json
​
subscription_id
string
required
​
subscription
object
required

Subscription is used to define which events of the relevant topics should be sent to the callback URL. Limitations:

  1. This is only forward-looking, meaning that only events that occur after the subscription is created will be sent to the target.
  2. There may only be two (2) subscriptions per topic, unless the subscription filter specifies a specific id field OR delete_after_use is set to true.
  3. Delivery is not guaranteed; message delivery will be retried when encountering a non-2xx response, but if there are multiple subscriptions for the same topic and one subscription successfully received the message, it will not be redelivered to the others.
​
update_mask
string<field-mask>
required

Response

OK

​
subscription
object

Subscription is used to define which events of the relevant topics should be sent to the callback URL. Limitations:

  1. This is only forward-looking, meaning that only events that occur after the subscription is created will be sent to the target.
  2. There may only be two (2) subscriptions per topic, unless the subscription filter specifies a specific id field OR delete_after_use is set to true.
  3. Delivery is not guaranteed; message delivery will be retried when encountering a non-2xx response, but if there are multiple subscriptions for the same topic and one subscription successfully received the message, it will not be redelivered to the others.