Skip to main content
GET
cURL

Authorizations

Authorization
string
header
required

Send Authorization: Bearer <key>. Testnet: lum_test_…; Mainnet: lum_live_…. A key works only on its own network, so pick the server that matches it (the other network answers 401). Publishable lum_pub_… keys call read-only methods only, from an allowed browser origin. Dashboard sessions and webhook keys are not accepted.

Path Parameters

id
string
required

The operation ID from the X-Lumeus-Operation-ID header (or Location) of the original 202 response. The example ID is a placeholder and answers 404.

Example:

"rpo_ue_00000000000000000000000000000000"

Response

The saved response, with its original status and body.

A JSON-RPC 2.0 response: result on success, error otherwise. A JSON-RPC error can arrive with HTTP 200 (for example from the node, or for one child of a batch). Gateway errors carry the code string in error.data and the request ID in error.request_id; they echo your id when the body is a parseable single request and use a null id when it cannot be determined. Preserve integer IDs exactly; avoid unsafe JavaScript numeric IDs. The gateway never answers 502 or 504.

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

The id of your call, echoed unchanged (a string id comes back as a string). null when the gateway cannot read the id, for example for invalid JSON.

result
object
required

The method result, as returned by stellar-rpc 29. Its fields depend on the method: see the method pages (for example getHealth or getEvents) or the components named after the method with a Result suffix (getHealthResult, getEventsResult, ...).

error
object
Example: