API archive entry · source-reported
Avaza API Documentation
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. Not
Archive history
This history reflects directory observations and owner review, not a provider release log.
- First observed: Sep 20, 2026
- Last directory-field change: Sep 20, 2026
- Current source observation: Sep 20, 2026
Published source events
added
Sep 20, 2026 · Added from an approved API directory.
Where to check product changes
Use the provider documentation and status channels for releases, breaking changes, and outages.
Source reference
This page separates source-reported facts from questions that need live provider verification.