Scopes - Origin One API

Every API token carries a set of OAuth-style scopes. Each endpoint requires a specific scope; a request made with a token that lacks the required scope is rejected with 401 Unauthorized. Scopes follow a predictable resource.action naming convention:

Action	Meaning
`{resource}.list`	Read a paginated, filterable collection (`GET /{resource}s`).
`{resource}.read`	Read one record by ID (`GET /{resource}s/{id}`).
`{resource}.create`	Create a record (`POST /{resource}s`).
`{resource}.search`	Ranked or fuzzy search with its own contract (`POST /{resource}s/search`).
`{resource}.{action}`	A domain action with its own audit semantics, such as `order.cancel`.

Available scopes

Scope	Grants access to
`order.create`	Create a new order
`order.read`	Get an order by ID
`order.participant.read`	The `participant` block in Get an order and List orders responses (omitted without it)
`order.list`	List orders
`order.cancel`	Cancel an order
`agency.list`	List agencies
`agency.read`	Get an agency
`agency.jobCategories.read`	Get a job category
`clinic.list`	List clinics
`clinic.read`	Get a clinic by ID
`clinic.search`	Search for clinics
`company.list`	List companies
`company.read`	Get a company
`location.list`	List locations
`location.read`	Get a location
`package.list`	List packages
`package.read`	Get a package
`service.list`	List services
`service.read`	Get a service by ID

Request only the scopes your integration needs. Narrow tokens are easier to audit and limit the impact if a token leaks.

To add scopes to an existing token or request a new token, contact Origin One.

​Available scopes

Available scopes