Developer Docs

API onboarding and webhook verification

Start with public discovery endpoints, move into scoped private API keys, and verify webhook signatures for automation.

Developer platform Open API reference

Getting started

Integration path

1. Query public providers and datacenters without authentication to power search, location, and comparison use cases.

2. Generate scoped API keys from the dashboard for private account-bound workflows.

3. Register webhook endpoints and validate signed deliveries with your endpoint secret.

4. Use the live OpenAPI reference for request/response details and route discovery.

Reference endpoints

Core routes

GET /api/v1/providers

Public provider discovery with filters, sorting, and pagination.

GET /api/v1/datacenters

Public facility discovery for market and footprint analysis.

GET /api/v1/private/profile

Private API key validation route for integration handshakes.

GET /api/v1/docs

Live OpenAPI-powered API reference.

Providers example

curl "https://infrivox.com/api/v1/providers?pageSize=5&sort=rating_desc"

Datacenters example

curl "https://infrivox.com/api/v1/datacenters?pageSize=5&countryCode=NL"

Private API example

curl -H "X-API-Key: ivx_..." "https://infrivox.com/api/v1/private/profile"

GraphQL preview

Schema-aligned query planning

Use GraphQL planning to prepare query-first integrations that mirror the existing provider and datacenter catalog fields while the live REST API remains the production contract.

query ProviderCatalog {
  providers(pageSize: 5, sort: "rating_desc") {
    items {
      name
      slug
      verificationLevel
      countryCode
    }
  }
}

OAuth registry

Delegated authorization patterns

OAuth planning now covers authorization-code, client-credentials, and device-code flows so partner apps can move beyond long-lived static credentials when delegated access is required.

https://infrivox.com/oauth/authorize?response_type=code&client_id=ivx_app&redirect_uri=https://app.example.com/callback&scope=catalog:read

Webhook verification

Validate signed payloads

Read the raw request body, compute HMAC SHA-256 with your endpoint secret, and compare it to the signature header.

X-Infrivox-Signature: sha256=<hmac_sha256_of_raw_body>

Every delivery also includes the event name and delivery id headers for idempotency and debugging.

Next steps

Move from docs to production

Create API keys from the dashboard, then move to the webhook workspace to register signed delivery endpoints.

Use test deliveries before production event routing so downstream systems can confirm authentication, schema parsing, and retries.

API keys Webhooks API logs