For a quick start guide click here
If you signed up for our API through RapidAPI you can make your test calls on their platform. Your RapidAPI credentials will not work on this page.
Do not use your RapidAPI keys on this page.
If you signed up with us and have an account, you must first authenticate with your API Keys and retrieve a Json Web Token (JWT) from the /getToken endpoint to access the other endpoints.
Your JWT is a required argument to all endpoints.
Welcome to the autogenerated documentation & test tool for Avaza's API.
API Security & Authentication
Authentication options include OAuth2 Implicit and Authorization Code flows, and Personal Access Token. All connections should be encrypted over SSL/TLS
You can set up and manage your api authentication credentials from within your Avaza account. (requires Administrator permissions on your Avaza account).
OAuth2 Authorization endpoint: https://any.avaza.com/oauth2/authorize
OAuth2 Token endpoint: https://any.avaza.com/oauth2/token
Base URL for subsequent API Requests: https://api.avaza.com/
Blogpost about authenticating with Avaza's API: https://www.avaza.com/avaza-api-oauth2-authentication/
Blogpost on using Avaza's webhooks: https://www.avaza.com/avaza-api-webhook-notifications/
The OAuth flow currently issues Access Tokens that last 1 day, and Refresh tokens that last 180 days
The Api respects the security Roles assigned to the authenticating Avaza user and filters the data return appropriately.
Support
For API Support, and to request access please contact Avaza Support Team via our support chat.
User Contributed Libraries:
Graciously contributed by 3rd party users like you.
Note these are not tested or endorsesd by Avaza. We encourage you to review before use, and use at own risk.
Use these REST APIs for managing OAuth2 servers configuration in your Azure API Management deployment. OAuth 2.0 can be used to authorize developer accounts for Azure API Management. For more information refer to [How to OAuth2](https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-oauth2).
Use these REST APIs for performing operations on Backend entity in Azure API Management deployment. The Backend entity in API Management represents a backend service that is configured to skip certification chain validation when using a self-signed certificate to test mutual certificate authentication.
Use these REST APIs for performing operations on Cache entity in your Azure API Management deployment. Azure API Management also allows for caching responses in an external Azure Cache for Redis. For more information refer to [External Redis Cache in ApiManagement](https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-cache-external).
Use these REST APIs for performing operations on Certificate entity in your Azure API Management deployment. Certificates can be used to setup mutual authentication with your Backend in API Management. For more information refer to [How to secure backend using Mutual Auth Certificate](https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-mutual-certificates).