API surfaces
6
REST, GraphQL, OAuth, session, private, and webhook delivery
Developer Platform
Public API, private API, and webhooks
Build against catalog, workflow, and intelligence surfaces with structured API access, webhook delivery, and operator-ready implementation paths.
Webhook events
6
Live event contracts available now
Auth models
4
Public, API key, JWT, and OAuth planning
Integration control
2
Docs plus dashboard control surfaces
Available now
Developer access registry
| Surface | Auth | Purpose |
|---|---|---|
| Private profile API | X-API-Key | Scoped account and operator automation |
| REST catalog APIs | Public or JWT | Provider, datacenter, claim, and workflow integrations |
| GraphQL preview | Planned JWT/API key alignment | Query-focused catalog access patterns for integrators |
| OAuth registry | OAuth 2.0 | Delegated access planning for partner and operator apps |
| Session APIs | JWT | Control-center and authenticated workflow access |
| Webhook delivery logs | Dashboard + signing secret | Test, verify, and monitor event delivery |
GET https://infrivox.com/api/v1/private/profile with X-API-KeyDashboard-issued API keys authenticate private integration workflows without exposing session cookies.
Webhook endpoints support signing secrets, real test deliveries, and delivery-log review from the dashboard.
Webhook platform
Live event delivery registry
| Event | Destination | Status |
|---|---|---|
provider.claim.reviewed | CRM / provider success | LIVE |
datacenter.claim.reviewed | facility operations | LIVE |
review.approved | trust & notifications | LIVE |
lead.qualified | sales pipeline | LIVE |
api_key.created | developer operations | LIVE |
api_key.revoked | security / developer operations | LIVE |
GraphQL preview
Query-oriented catalog access
GraphQL planning now mirrors the existing REST catalog so teams can prepare query-based integrations before a dedicated schema gateway is promoted live.
{ providers(pageSize: 5) { items { name slug verificationLevel countryCode } } }OAuth planning
Delegated access workflows
OAuth registry coverage now documents authorization-code, client-credentials, and device-code patterns for partner and operator apps that should not rely on static API keys alone.
Use this with the existing JWT and API-key model to design secure app onboarding before full delegated authorization rollout.