asetavo.
Book a demoStart free
Developers

Build on Asetavo.

A clean REST API with Bearer auth, webhooks, and a consistent response envelope. Endpoints for assets, tags, events and more.

Get API access
curl — list assets
$ curl -H "Authorization: Bearer $TOKEN" \
  https://api.asetavo.com/v1/assets

{
  "success": true,
  "message": "OK",
  "data": [{ "id": "A-1182", "name": "55\" TV" }],
  "meta": { "page": 1, "total": 4812 }
}
1
Get an API key
Create a scoped key in your workspace settings.
2
Authenticate with Bearer
Send the key in the Authorization header.
3
Make your first call
List your assets with a single GET request.

Authentication

All requests use a Bearer token in the Authorization header. Keys are scoped per workspace and can be rotated anytime.

GET/v1/me
Return the authenticated workspace and token scope.

Assets

Create, read and update the assets in your register.

GET/v1/assets
List assets.
Params: page, limit, category_id
POST/v1/assets
Create an asset.
Params: name, category_id, cost
GET/v1/assets/{id}
Retrieve a single asset.
POST/v1/assets/{id}/checkout
Check an asset out to an assignee.
Params: assignee_id, due_date

Tags

Commission and look up QR, barcode, RFID and NFC tags.

GET/v1/tags
List tags.
Params: type, assigned
POST/v1/tags/commission
Bind a tag to an asset.
Params: epc|code, asset_id

Locations

Manage the location and zone hierarchy.

GET/v1/locations
List locations and zones.
POST/v1/zones
Create a zone from locations and readers.
Params: name, location_ids[], reader_ids[]

Events / Ingest

Ingest reader events. Reader events are HMAC-signed.

POST/v1/reader-events
Ingest a signed reader event.
Params: reader_id, epc, ts, signature

Webhooks

Subscribe to asset movements, alerts and checkouts. Deliveries are signed and SSRF-safe.

GET/v1/webhooks
List webhook subscriptions.
POST/v1/webhooks
Create a subscription.
Params: url, events[]
signature header
X-Asetavo-Signature: sha256=...

Rate limits

Requests are rate-limited per workspace. Respect 429 responses and the Retry-After header with exponential back-off.

Errors

Errors return a consistent envelope with success:false, a message and an error code. HTTP status codes follow REST conventions.

SDKs for Node and Python are on the roadmap — for now, the REST API is fully usable via any HTTP client.

Ready to build?

Grab an API key and make your first call in minutes.

Get API accessSee the platform

Bearer auth · consistent envelope · signed webhooks