---
title: "Adopt a brand that already exists at Google"
method: POST
path: "/v1/brands/{id}/link-google"
tags: ["Google & carriers"]
---

# Adopt a brand that already exists at Google

`POST /v1/brands/{id}/link-google`

## Request

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

An agent created in Google's console leaves our brand row with no `rbm_brand_id`, and every Google-side operation needs it. The symptom is severe and silent: verification and carrier launch both fail for a brand that looks completely set up. Back-fills agent links too.

## Path parameters

- `id` string, required

## Request body

- object
  - `rbmBrandId` string: Match explicitly. Omit to match on display name.

## Response `200`

Linked.

- object
  - `ok` boolean, required
  - `rbmBrandId` string, required
  - `agentsLinked` string[]
  - `googleAgents` object[]
    - `rbmAgentId` string
    - `displayName` string

## Other responses

- `401`: Not signed in, and no account-linked API key was sent.
- `404`: No such brand here, or no matching brand at Google. The error lists what is available.
- `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)