Requests
Endpoint
The public RPC API is available atMethods
Requests are eitherGET to read resources or POST to perform actions.
All requests must include the Content-Type header:
Authentication
Include the secret API token generated from Obselite dashboard in theAuthorization header as a Bearer token:
Routing
The routing convention is/{resources}/{action}.
Each resource will include CRUD operations:
| Method | Route | Purpose |
|---|---|---|
GET | /{resources} | Read all resources |
POST | /{resources}/create | Create a single resource |
GET | /{resources}/read | Read a single resource |
POST | /{resources}/update | Update a single resource |
POST | /{resources}/delete | Delete a single resource |
Responses
Methods
GET requests will either return a list of results with metadata or a single resource.
POST requests will return an error, the result of an action, or the new/updated resource.
Errors
| Property | Type | Description |
|---|---|---|
message | string | Human-readable description of the error |
code | string | Machine-readable error code for programmatic handling |
issues | array | List of specific validation or processing errors |
issues[].message | string | Detailed message for each individual issue |
Lists
Items
Theitems array contains the requested resources, sorted by createdAt in descending order.
Metadata
Themetadata object contains the request’s pagination information.
| Property | Type | Description |
|---|---|---|
count | number | Total number of items across all pages |
isFirstPage | boolean | Whether this is the first page of results |
isLastPage | boolean | Whether this is the last page of results |
limit | number | Maximum number of items per page |
nextPage | number | Page number for the next set of results (null if on last page) |
offset | number | Number of items skipped from the start |
page | number | Current page number |
pageCount | number | Total number of available pages |
previousPage | number | Page number for the previous set of results (null if on first page) |