Avarra

Avarra API

The production Avarra API, served from api.avarra.ai behind an AWS application load balancer. Every path under /v1/ is protected and returns a JSON 401 envelope without a bearer token; tokens are issued from /oauth/token using the OAuth 2.0 client_credentials grant with client_secret_basic or client_secret_post client authentication. The authorization server advertises itself through RFC 8414 metadata at /.well-known/oauth-authorization-server and publishes its signing keys at /.well-known/jwks.json, both anonymously. An anonymous /health endpoint returns {"status":"ok"}. Avarra publishes no OpenAPI, no API reference and no developer documentation, so the operation surface behind the auth wall is not publicly described; access is granted through a commercial relationship rather than self-serve signup.

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/avarra/refs/heads/main/authentication/avarra-authentication.yml

Other Resources

🔗
WellKnown
https://raw.githubusercontent.com/api-evangelist/avarra/refs/heads/main/well-known/avarra-well-known.yml
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/avarra/refs/heads/main/conventions/avarra-conventions.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/avarra/refs/heads/main/errors/avarra-problem-types.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/avarra/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
aid: avarra-api
name: Avarra API
description: The production Avarra API, served from api.avarra.ai behind an AWS application load balancer.
  Every path under /v1/ is protected and returns a JSON 401 envelope without a bearer token; tokens are
  issued from /oauth/token using the OAuth 2.0 client_credentials grant with client_secret_basic or client_secret_post
  client authentication. The authorization server advertises itself through RFC 8414 metadata at /.well-known/oauth-authorization-server
  and publishes its signing keys at /.well-known/jwks.json, both anonymously. An anonymous /health endpoint
  returns {"status":"ok"}. Avarra publishes no OpenAPI, no API reference and no developer documentation,
  so the operation surface behind the auth wall is not publicly described; access is granted through a
  commercial relationship rather than self-serve signup.
humanURL: https://www.avarra.ai/product
baseURL: https://api.avarra.ai
tags:
- Sales Enablement
- Sales Training
- AI
properties:
- type: Authentication
  url: authentication/avarra-authentication.yml
- type: WellKnown
  url: well-known/avarra-well-known.yml
- type: Conventions
  url: conventions/avarra-conventions.yml
- type: ErrorCatalog
  url: errors/avarra-problem-types.yml