Nevola Engine API.

The Nevola Engine API lets digital content brands generate per-subscriber content under a contract that is async, replayable, and auditable by default.

Authentication

Send your API key as a bearer token. Sandbox keys start with nev_test_, live keys with nev_live_.

curl https://api.nevolagroup.com/v1/profiles/prof_01HXY \
  -H "Authorization: Bearer nev_live_..."

Errors

Errors return a consistent JSON shape with code, message, request_id, and doc_url. HTTP status codes follow REST conventions.

{
  "code": "profile_not_found",
  "message": "No profile exists for the provided ID.",
  "request_id": "req_01HXY...",
  "doc_url": "https://nevolagroup.com/docs/#errors"
}

Rate limits

Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. The default tier allows 100 req/s sustained per API key, with a burst of 200.

Idempotency

All POST endpoints accept an Idempotency-Key header. Reuse the same key for the same logical operation, and Nevola returns the original response. Use a new key for a new operation.

SDKs

Official SDKs are available for Node.js and Python. Go is on the roadmap.

• @nevola/engine — Node.js / TypeScript
• nevola-py — Python 3.10+

Webhooks

Register webhook endpoints to receive delivery confirmations and async sequence results. All payloads are signed with HMAC-SHA256 in the Nevola-Signature header. Retries follow exponential backoff: 1s, 5s, 25s, 125s, 625s, with a dead-letter queue after 5 failures.

Versioning

The API is versioned via the URL path (/v1/...). Breaking changes ship as a new major version; backward-compatible additions go into the current version. Deprecation notices arrive at least 12 months before removal.

API reference

Every endpoint, request shape, response, and error code. Generated from the OpenAPI 3.1 specification.