Skip to main content
PATCH
Update subscription

Authorizations

Authorization
string
header
required

Bearer token authentication

Path Parameters

token
string
required

Subscription token

Body

application/json
subscription
object
required

Response

Success

The updated subscription, plus which subscriptions the write covered and which it actually changed.

Both arrays are always present, including on a single-subscription write, which resolves and changes itself. A client forced to tell "the fan-out reported nothing" apart from "this server predates the field" would have to guess, and guessing wrong means reporting a fan-out that never happened. A no-op write resolves its bundle and changes nothing, so changed_subscription_tokens is empty while resolved_subscription_tokens is not.

subscription
object
required

Subscription rendered by SubscriptionBlueprinter

resolved_subscription_tokens
string[]
required

Every subscription token the write covered, ascending by subscription id. A subscription that joined the bundle after the write took its snapshot is deliberately outside the write and absent here.

changed_subscription_tokens
string[]
required

The subset of resolved_subscription_tokens whose stored row actually changed. Empty when the write was a no-op.

meta
object