Wove · OAuth Scopes
Wove OAuth Scopes
OAuth 2.0
derived
Wove publishes 9 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Wove API on a user’s behalf.
Tokens are issued from https://api.wove.com/api/v1/external/auth/token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
Company
Scopes: 9
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.wove.com/api/v1/external/auth/token
https://api.wove.com/api/v1/external/auth/token
Flows
clientCredentials
clientCredentials
Scopes (9)
| Scope | Description | Flows |
|---|---|---|
| shipments:read | Read access to shipments (named in TokenRequest/TokenResponse scope examples). | |
| documents:read | Read access to documents (named in TokenRequest/TokenResponse scope examples). | |
| validation:create | Create document validation jobs (named in TokenRequest/TokenResponse scope examples). | |
| tariffs:read | Required for tariff lookup/search/batch-lookup operations (per-operation 403 responses). | |
| rates:read | Required for querying rates from query-bank sources (per-operation 403 response). | |
| sources:write | Required for uploading and processing rate/document sources (per-operation 403 response). | |
| tms-organizations:read | Read access to TMS organizations (per-operation 403 responses). | |
| tms-organizations:write | Create/update/import TMS organizations (per-operation 403 responses). | |
| tms-organizations:delete | Delete TMS organizations (per-operation 403 response). |