Circles API
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of token balance rows.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of token balance rows.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Token metadata object.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Token metadata object.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of token metadata objects (one per input address).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of token metadata objects (one per input address).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Avatar info object (or null if not signed up).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Avatar info object (or null if not signed up).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of avatar info objects.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of avatar info objects.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Profile object (or null if none).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Profile object (or null if none).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of profile objects (one per input address; null when none).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of profile objects (one per input address; null when none).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
CIDv0 string (or null).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
CIDv0 string (or null).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of CIDv0 strings (one per input address; null when none).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of CIDv0 strings (one per input address; null when none).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Profile object.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Profile object.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of profile objects.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of profile objects.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of matching profiles.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of matching profiles.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Search result with detected searchType and matched profiles.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Search result with detected searchType and matched profiles.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Trust relations for the user.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Trust relations for the user.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of aggregated trust relation rows.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of aggregated trust relation rows.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of commonly-trusted addresses (empty if none).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of commonly-trusted addresses (empty if none).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Paginated list of group memberships.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Paginated list of group memberships.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Paginated list of group memberships.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Paginated list of group memberships.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Mint-limit rows for the group.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Mint-limit rows for the group.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Full network snapshot (shape illustrative — fields may vary).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Full network snapshot (shape illustrative — fields may vary).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Transaction rows.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Transaction rows.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Enriched transaction rows (shape illustrative; like circles_getTransactionHistory rows plus fromProfile/toProfile).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Enriched transaction rows (shape illustrative; like circles_getTransactionHistory rows plus fromProfile/toProfile).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Paginated list of token holders.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Paginated list of token holders.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Transfers carrying a non-empty data field.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Transfers carrying a non-empty data field.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of events with event name and values payload (hex-encoded numerics).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of events with event name and values payload (hex-encoded numerics).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Result with columns and rows (rows are positional arrays aligned to columns).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Result with columns and rows (rows are positional arrays aligned to columns).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Paginated query result.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Paginated query result.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of namespaces with their tables and column definitions.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of namespaces with their tables and column definitions.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Combined profile view.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Combined profile view.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Trust network summary statistics.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Trust network summary statistics.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Enriched trust relations grouped under results.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Enriched trust relations grouped under results.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Valid inviters with balances and enriched avatar info.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Valid inviters with balances and enriched avatar info.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Invitation origin record.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Invitation origin record.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Invitations grouped by source.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Invitations grouped by source.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of trust-based inviters (shape illustrative).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of trust-based inviters (shape illustrative).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of escrow invitations (shape illustrative).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of escrow invitations (shape illustrative).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Array of at-scale invitations (shape illustrative).
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Array of at-scale invitations (shape illustrative).
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Invited accounts with status and enriched avatar info.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Invited accounts with status and enriched avatar info.
JSON-RPC 2.0 request envelope. Sent via POST to the server root (/).
JSON-RPC protocol version. Always "2.0".
2.0Possible values: Request identifier echoed back in the response.
1The RPC method name (also selects routing on the single root endpoint).
Computed flow with the ordered list of transfers.
JSON-RPC 2.0 response envelope. On success result is present; on failure error is present instead (still returned with HTTP 200).
2.01Method-specific result. Present on success; see the example for each operation. (Type varies: string, object, array, boolean, …)
Computed flow with the ordered list of transfers.
Last updated
Was this helpful?