API Reference

Errors & conventions

Every Stridge endpoint shares the same response conventions: a JSON error envelope on failure, predictable HTTP status codes, and limit/offset pagination on the list endpoints.

Error envelope

On failure, every endpoint returns the same JSON shape with the HTTP status echoed in the body:

Error response
{
  "success": false,
  "code": 400,
  "error": "invalid request"
}
FieldTypeNotes
successbooleanAlways false for errors.
codeintegerHTTP status code, echoed in the body.
errorstringHuman-readable message describing what went wrong.

success and error are always present; code mirrors the HTTP status.

Status codes

StatusMeaning
200Success — the body carries the requested resource.
400The request was malformed or failed validation.
401Missing or invalid X-API-Key on a protected endpoint.
404The referenced resource (e.g. a UDA or settlement id) does not exist.
500An unexpected error on Stridge's side — safe to retry with backoff.

Pagination

List endpoints page with limit and offset query parameters:

  • limit — page size. Default 50, maximum 200.
  • offset — number of items to skip. Default 0.

Walk a result set by holding limit fixed and advancing offset by limit each page:

Second page of 50
curl "https://api.stridge.dev/v1/uda?limit=50&offset=50" \
  -H "X-API-Key: $STRIDGE_API_KEY"

Filtering lists

List endpoints accept discrete filter parameters rather than a query language — combine them as query-string pairs, and results match all supplied filters. For example, List UDA addresses filters by owner, network_id, to_address, asset_symbol, and status (active or retired):

Active UDAs for one owner
curl "https://api.stridge.dev/v1/uda?owner=user_8a7f3c&status=active" \
  -H "X-API-Key: $STRIDGE_API_KEY"

The exact filters available are listed on each endpoint's reference page.