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. Note these are not tested or endorsesd by Avaza. We encourage you to review before use, and use at own risk. - PHP OAuth Client Package for Azava API (by Debiprasad Sahoo)
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- apisguru:avaza.com
- Listed in
- APIs.guru
- Publisher
- avaza.com
- Latest version
- v1
- Published
- 2023-03-06
- Evidence
- Listed only, not analyzed yet
What a full analysis of Avaza API Documentation checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.