Resolve Inbound Channel Credentials (M2M)
Return only the provider credentials agent-runtime needs to verify an inbound webhook or handshake signature for a channel key - same request body as channel-resolve. Mints no token and returns no agent config, so a request whose signature fails verification leaves no session credential behind; agent-runtime calls channel-resolve only after the signature checks out.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Body of POST /v1/bundler/channel-resolve.
(kind, key, provider) generalises WidgetPublicResolveIn's single embed_key to a channel-agnostic identifier: for telephony, key is the dialled E.164 number and provider is the telephony provider's stable name, so a second channel kind is a new resolution branch rather than a second route.
Response Body
application/json
application/json
curl -X POST "https://example.com/v1/bundler/channel-credentials" \ -H "Content-Type: application/json" \ -d '{ "kind": "string", "key": "string", "provider": "string" }'{ "channel_id": "bbe8aa76-a4bb-46f6-a785-df8e831cc459", "telephony": { "provider_type": "string", "account_id": "string", "auth_token": "string", "signing_secret": "string" }, "genesys": { "integration_id": "55d7337e-1d0a-49fc-9826-925ba40df035", "api_key_hash": "string", "client_secret": "string", "genesys_org_id": "4f9f2661-e1ff-4f37-8fb8-25e196548317" }}{ "detail": [ { "loc": [ "string" ], "msg": "string", "type": "string" } ]}