Can this agent reach this number over RCS?
Folds in every reason a send might not land: the device has no RCS, the agent isn't launched on that carrier, or the number simply hasn't used RCS lately. Point-in-time — Google only answers for numbers seen on RCS in roughly the last 31 days, so never cache it as a permanent fact.
false is not a dead end: the send falls back to SMS. The value is knowing before you send.
Not available on a sandbox key. It asks Google about a real agent, and a sandbox account has none — it answers 409 AGENT_NOT_MAPPED until sync-google has run, which is irreversible. Sending needs none of this: POST /v1/conversations resolves a channel and simulates delivery in sandbox, so treat this as a go-live check rather than a build-time one.
Request
- Base URL: https://api.cadencercs.com
- URL: https://api.cadencercs.com/v1/agents/{id}/reachability
- Auth: HTTP bearer
Path parameters
Agent id.
Query parameters
E.164 number to check.
Response
Point-in-time answer.
Changes
No recorded changes to this operation across all 1 revision of this API.