Skip to main content
The LumeScope Actions API gives you a decoded view of every Cascade and Sense action registered on the Lumera network. Rather than parsing raw chain transactions yourself, you query a pre-indexed store. The store tracks each action through its full lifecycle, from the initial register transaction through finalize and approve. Three endpoints cover the most common needs. You can list actions with filters, fetch the full detail for a single action, and retrieve aggregate counts across the network.
All Actions API endpoints are read-only and require no authentication. The base URL for mainnet is https://api.lumera.io. Substitute https://api.testnet.lumera.io for testnet.

GET /v1/actions

Returns a paginated list of Cascade and Sense actions with fully decoded metadata. Use the query parameters to filter by type, creator, state, and block height range.

Query parameters

string
Filter by action type. Accepted values are cascade and sense. Omit to return both types.
string
Filter by the Bech32 address of the account that created the action.
string
Filter by action state. Common values are registered, finalized, and approved.
string
Filter actions associated with a specific SuperNode address.
integer
Return only actions created at or after this block height.
integer
Return only actions created at or before this block height.
integer
default:"20"
Maximum number of actions to return per page.
string
Opaque pagination cursor returned by the previous response. Pass this value to fetch the next page.
boolean
default:"false"
When true, each action in the list includes its full transaction lifecycle (register, finalize, approve tx hashes and heights).

Example request

Example response

Response fields

array
Array of action objects matching the query.
integer
Total number of actions matching the query filters, across all pages.
integer
Current page number (1-indexed).

GET /v1/actions/{id}

Returns the full details for a single action, including its complete transaction lifecycle. Use this endpoint when you need register, finalize, and approve transaction hashes and block heights for a specific action.

Path parameters

string
required
The unique action ID. This is the same id value returned by GET /v1/actions.

Example request

Example response

Response fields

string
Unique action identifier.
string
The action type, either cascade or sense.
string
Current lifecycle state.
string
SHA-256 content hash of the stored data.
string
Bech32 address of the account that registered the action.
string
RFC 3339 timestamp of the registration transaction.
string
RFC 3339 timestamp of the finalization transaction.
string
RFC 3339 timestamp of the approval transaction.
object
Transaction lifecycle for this action.

GET /v1/actions/stats

Returns aggregated action statistics across the entire network. Use this endpoint to build dashboards or monitor overall Cascade and Sense activity without paginating through individual records.

Query parameters

string
Scope statistics to a single action type, either cascade or sense. Omit to aggregate across both types.
string
Start of the time window as an RFC 3339 timestamp (e.g. 2024-01-01T00:00:00Z).
string
End of the time window as an RFC 3339 timestamp.

Example request

Example response

Response fields

integer
Total number of actions indexed by LumeScope, across all types and states.
integer
Number of Cascade actions.
integer
Number of Sense actions.
integer
Number of actions that have reached the approved state.

Combine GET /v1/actions/stats with time-window filters to plot approval rates over time and detect anomalies in SuperNode throughput.