Developer Docs

API onboarding and webhook verification

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

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

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.

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

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

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

Webhook verification

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

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.