Get RPC operation result
Returns the saved response of a settled prepaid operation. Results are kept 24 hours, and each can be transferred three times in total, including the original response. While the operation is pending the answer is 202 with Retry-After 5; after expiry it is 410. Idempotency and recovery.
Authorizations
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
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.
"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.
2.0 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.