The API is the product
Avortyx’s own dashboards and forms call the same endpoints you do. There is no second-class integration layer that lags behind the app: when a feature ships, it is already in the API.
Work with calls, leads, buyers, offers, schedules, numbers, recordings, suppression lists and more through a RESTful interface that returns JSON.
Two kinds of token
- Company Access Tokens — a public and private key pair for one company, using basic authentication. Every pair has its own permissions, so a reporting job can read calls without being able to touch buyers.
- Developer Access Tokens — a token tied to a person, carrying that user’s permissions across every company they can access. Useful for internal tools that work across accounts.
Least privilege, by default
Give each key only what it needs, or full access when it really needs it. Tokens can be limited to a single agent (collaborator) and paused in an instant without being deleted.
Restricted and recorded
Every key is protected and every use is visible:
- IP whitelists — keep a token usable only from addresses you approve (see API IP Whitelist).
- Encrypted keys — private keys and developer tokens are encrypted at rest, never kept in plain text.
- Locked lead posting — require a valid token on lead-post endpoints too, so nobody can push leads in without credentials.
- Security logs — each API session is logged with its IP address, country, ISP and network (ASN), and refused attempts from blocked IPs are recorded too.
