Agiloft · OAuth Scopes
Agiloft OAuth Scopes
OAuth 2.0
searched
Agiloft publishes 1 OAuth 2.0 scope via the authorizationCode, authorizationCodePKCE, and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Agiloft API on a user’s behalf.
Tokens are issued from https://{hostname}/ewws/otoken.
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.
Contract Lifecycle ManagementContract ManagementLegalProcurementEnterprise SoftwareNo-CodeWorkflow AutomationDocument AutomationWebhooksSCIMCompany
Scopes: 1
Flows: authorizationCode, authorizationCodePKCE, clientCredentials
Method: searched
OAuth endpoints
Authorization URL
https://{hostname}/ewws/oauth
https://{hostname}/ewws/oauth
Token URL
https://{hostname}/ewws/otoken
https://{hostname}/ewws/otoken
Flows
authorizationCodeauthorizationCodePKCEclientCredentials
authorizationCodeauthorizationCodePKCEclientCredentials
Scopes (1)
| Scope | Description | Flows |
|---|---|---|
| permissions_for:{CONTACT_ID} | The only OAuth scope value Agiloft accepts. CONTACT_ID is the numeric id of the Agiloft contact record configured in the API application's "Associate this Application with Contact ID" field — for example permissions_for:222. The token then carries that user's group permissions. | authorizationCode, authorizationCodePKCE |
📄 Provider scope reference: https://help.agiloft.com/space/HELP/43714795/Control%20Access%20to%20REST%20API%20Operations
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.