- Getting Started
- Scopes
- API Resources
- Access Roles API v2
- Branches API v1
- Categories API v2
- Category Entries API v2
- Contacts API v1
- Geozones API v2
- Gift Cards API v2
- Inventory API v2
- Products API v2
- Product Downloads API v2
- Product Fragments API v2
- Product Fragment Translations API v2
- Product Media API v2
- Product Prices API v2
- Product Specifications API v2
- Product Translations API v2
- Redirects API v2
- Specifications API v2
- Specification Values API v2
- Tag Groups API v2
- Webhooks API v2
- Webhooks
Getting Started
Evance Admin APIs use the OAuth 2.0 protocol for authentication and authorisation. However, the level of support for common OAuth 2.0 scenarios is subject to the type of App you build.
To begin, you will require OAuth 2.0 client credentials. Creating your credentials will depend on whether you have a Private App, or a Public App. Using your API client credentials, your client application requests an access token from Evance. Then uses the access token to access the Evance API.
Private AppsA private Evance app integrates with the Evance API on behalf of a single tenant account. |
Public AppsA public Evance app may integrate with Evance APIs on behalf of multiple tenants - coming soon. |
AuthenticationUnderstand how Evance implements the OAuth standard to ensure your apps authenticate securely before accessing data. |
Making RequestsYou may access data having passed Authentication using an Access Token. Discover how to used OAuth Access Tokens with Evance's API. |
Refresh TokensAn overview of Refresh Tokens and how to use them. |