Google & carriers

Our partner record at Google

Where the partner half of the verification contact comes from. Read rather than held in env, so changing the partner email in the Console changes what verification requests send.

partnerWebhookKnown: false means partners.get returned no capabilities block — not that no webhook is registered.

partnerWebhookKnown: true with partnerWebhook: null is the readable case and it is worth acting on: Google has no partner-level URI to push inbound messages to, so replies to any agent under this partner that lacks its own webhook are dropped. Outbound is unaffected, which is what makes it easy to miss. This is deployment-level configuration, not something an API caller can set — GET /v1/agents/{id}/launch-readiness reports the same fact as a blocking inbound check, alongside when inbound was last actually received.

get/v1/partner

Request

  • Base URL: https://api.cadencercs.com
  • URL: https://api.cadencercs.com/v1/partner
  • Auth: HTTP bearer

Response

Partner record.

namestring nullable
displayNamestring nullable
companystring nullable
contactEmailsstring[]
technicalContactobject nullable
partnerWebhookstring nullable

The partner-level inbound webhook, when readable.

partnerWebhookKnownboolean

False means Google returned no capabilities block, not that none is set. True with a null webhook means Google genuinely has none, and inbound is dead.

webhookNotestring

Changes

No recorded changes to this operation across all 1 revision of this API.