Skip to main content
POST
Legacy A2A gateway - JSON-RPC 2.0 dispatch (POST)

Authorizations

Authorization
string
header
required

User-bound credential carrying an identity: either a session JWT or a user access token (at:*) generated from the user settings UI. Send as Authorization: Bearer <token>. Org API keys (iak_*) are not accepted here - they carry no user identity. Use the x-prismeai-api-key header instead (see OrgApiKeyAuth).

Body

application/json

Legacy /v1/a2a JSON-RPC request. params.id MUST be present - it identifies the target agent for gateway dispatch.

jsonrpc
enum<string>
required
Available options:
2.0
method
string
required

A2A method name (e.g. message/send, tasks/get).

Maximum string length: 64
params
object
required
id
string

JSON-RPC request id - echoed back in the response.

Maximum string length: 128

Response

JSON-RPC 2.0 response. result is the forwarded result envelope; alternatively error carries a JSON-RPC error object when the dispatch failed.

A2A JSON-RPC 2.0 response.

jsonrpc
enum<string>
Available options:
2.0
id
string | null

Echoes the request id (string or null per JSON-RPC 2.0).

result
object
error
object