Scopes

What each scope grants.

Scopes are attached to an API key at issue time and enforced identically across REST routes and MCP tools. A request missing the required scope returns 403.

Org scoping

All data is scoped to the org that owns the key. A key only ever sees its own org's data — there is no org parameter anywhere in the API.

Reference

products:read

Catalog reads.

products:write

Create and update products.

orders:read

Order reads.

orders:write

Create orders, acknowledge, update status.

inventory:write

Bulk stock updates.

warranty:read

Claim tracking.

warranty:write

File and update claims.

telematics:read

Connection health.

telematics:write

Run and replay connections.

edi:write

Submit raw X12 interchanges.

storefront:read

Storefront MCP reads.

storefront:write

Storefront bookings, orders, quotes.

per-object

Dynamic objects declare their own read/write scopes.

Need a scope you don't have? Keys are issued by the platform operator — contact your TreadReady representative and we'll reissue with the scopes you need.