---
title: "Read this agent's Google inbound routing"
method: GET
path: "/v1/agents/{id}/webhook"
tags: ["Google inbound routing"]
---

# Read this agent's Google inbound routing

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

## Request

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

**This is Google's inbound routing for one agent — it is not how you receive messages from Cadence.** It tells Google to push this agent's traffic to a URL of your own instead of to the partner-level endpoint that Cadence normally receives on, which means Cadence stops seeing that agent's replies and stops driving its flows.

If what you want is your application to learn about inbound replies, you want a `flow` (the server answers for you), `GET /v1/events` (SSE), or `GET /v1/conversations/{id}/answers` (polling) — see the guide at https://cadencercs.com/docs.html#receiving.

The verification token is input-only at Google and can't be read back.

## Path parameters

- `id` string, required

## Response `200`

Current routing.

- object
  - `webhookUri` string, nullable, required: Null when this agent uses the partner-level endpoint.
  - `integrationId` string, nullable
  - `integrations` object[]: Google's own view, best-effort.
  - `effective` string, required: Plain-language statement of where this agent's traffic goes.
  - `note` string

## Other responses

- `401`: Not signed in, and no account-linked API key was sent.
- `404`: No such agent on this account.
- `500`: Unexpected server error. The body is always JSON.

---

[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)