Google & carriers

Request carrier launch

This is what makes an agent reach non-test devices. Reachability is carrier-scoped, so an agent launched on two carriers is invisible on a third.

carriers replaces the whole launch set at Google rather than adding to it — previously requested carriers are re-sent automatically, because omitting them would silently drop those launches while the request still succeeded.

Verification must have been submitted first, but it only completes during launch approval: requiring verified here would deadlock, since verification never starts until a launch exists.

post/v1/agents/{id}/request-launch

Request

  • Base URL: https://api.cadencercs.com
  • URL: https://api.cadencercs.com/v1/agents/{id}/request-launch
  • Auth: HTTP bearer

Path parameters

idstring required

Agent id.

Request body

carriersstring[] required

Carrier names, e.g. ["T-Mobile","AT&T"]. See GET /v1/carriers.

confirm'irreversible'

Response

Accepted by Google.

okboolean required
status'launching' required
carriersstring[] required

The complete launch set now on file.

carriedForwardstring[]

Previously requested carriers re-sent to avoid dropping them.

notestring
nextStepstring
warningstring

Google accepted the launch but our own records could not be updated. Do not retry — poll GET /v1/agents/{id}/launch for the authoritative state.

bookkeepingErrorsstring[]

Changes

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