---
title: "The agent's profile at Google"
method: GET
path: "/v1/agents/{id}/google"
tags: ["Google & carriers"]
---

# The agent's profile at Google

`GET /v1/agents/{id}/google`

## Request

- Base URL: `https://api.cadencercs.com`
- URL: `https://api.cadencercs.com/v1/agents/{id}/google`
- Auth: HTTP bearer

What the agent actually looks like to Google, and therefore to a consumer. `missing` is the point: it lists the fields launch review expects and you haven't set. An agent created in the console shows a bare info screen, and the only symptom is a message that arrives looking unbranded.

## Path parameters

- `id` string, required

## Response `200`

Live profile.

- object
  - `agentId` string, required
  - `rbmAgentId` string
  - `profile` object, required: Google's `rcsBusinessMessagingAgent` verbatim.
  - `missing` string[], required: Fields empty at Google that launch review expects.
  - `note` string

## Other responses

- `401`: Not signed in, and no account-linked API key was sent.
- `404`: No such agent on this account.
- `409`: This agent doesn't exist at Google yet.
- `500`: Unexpected server error. The body is always JSON.
- `502`: Google rejected the request.
- `503`: RBM not configured.

---

[API](https://skmtc.dev/cadencercs/apis/cadence-api.md) · [All operations](https://skmtc.dev/cadencercs/apis/cadence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cadencercs/apis/cadence-api/revisions/9438443c2081?raw)