Skip to main content
POST
(account/entitlement creation, plan change, cancellation). On an entitlement event whose account is already associated with an org (established at sign-up via /v1/metering/entitlement with kind:'gcp', token:<account>), (re)link the GCP entitlement so the flush reports usage against it. Always 200 to ack the push (an un-acked message is redelivered). Approving the entitlement via the Partner Procurement API is the credentialed follow-on. Required scope: write

Request body

PubSubPush
PubSubMessage
required

Response

No response body — event acked (linked=true when the account was pre-associated).

Status codes