Documentation overview

Find the path from first call to incident review.

Searchable guides, direct code examples, and connected operational references in one static documentation surface.

Search runs locally in the browser. No query is transmitted.

Choose a starting point.

Every guide leads toward a working sample page or a deeper reference surface.

Send the first event

Prepare a fictional request, inspect the response, and understand the sample identifiers.

Open quickstart

Authenticate requests

Explain signatures, test keys, scopes, and safe example practices.

Read authentication

Handle event delivery

Describe retries, replay, idempotency, and delivery-state concepts.

View event endpoints

Route by environment

Separate development, test, and live configuration in the content model.

Review environments

Inspect a request

Connect identifiers, policy results, region, latency, and response status.

View dashboard demo

Respond to an incident

Use service status, incident notes, and a clear resolution timeline.

Open status page

Send a sample event.

This example points to a reserved domain and does not connect to a real service. Replace the values only after connecting your own backend.

curl https://api.novahttp.example/v1/events \
  -H "Authorization: Bearer demo_key" \
  -H "Content-Type: application/json" \
  -d '{"type":"invoice.created","id":"evt_demo_813"}'

const response = await fetch(
  "https://api.novahttp.example/v1/events",
  {
    method: "POST",
    headers: { Authorization: "Bearer demo_key" },
    body: JSON.stringify({ type: "invoice.created" })
  }
);

import requests

response = requests.post(
    "https://api.novahttp.example/v1/events",
    headers={"Authorization": "Bearer demo_key"},
    json={"type": "invoice.created"},
)

Keep example credentials fictional.

The supplied strings are clearly marked as demo values. Never paste real keys, tokens, or production identifiers into template source or screenshots.

demo_keyfictional placeholder

Authorizationsample header

.examplereserved domain

Document the full response cycle.

Show success, validation errors, empty results, and retry guidance. A static successful response alone does not teach implementation.

response.statesDocumentation pattern

202Event acceptedcontinue

400Request invalidfix fields

401Signature missingcheck key

429Limit reachedretry later

Continue with the exact endpoint.

Move from the guide to the interactive local API reference, or choose an SDK pattern for implementation-specific examples.

Open API reference Choose an SDK

Ready to inspect request and response details?

Open API reference