Sign in required

Checking your Hub session...

Integrations

Webhook operations

Manage signed AffixIO delivery streams, receiver health, verification steps, and evidence exports from one private Hub console.

HMAC signed Replay aware SIEM ready

Back to stats

Delivery posture Checking endpoints The console will update after your Hub session is verified.

Active - Receiving deliveries

Total - On this account

Last delivery - Across all endpoints

Failing - Recent consecutive failures

Estimate - Events in range

Last download Never No download recorded here

Point AffixIO at an HTTPS receiver on your infrastructure. After you add the endpoint, the signing secret is displayed once. Store it before you leave the page.

Name the endpoint
A short name your team will recognise in delivery logs.
Receiver URL
Must be HTTPS. AffixIO POSTs a JSON body to this URL.
Choose events
Only subscribed events are delivered. You can change these later.

Events

Pause, rotate, or delete the endpoint at any time.

Endpoints Pause to stop deliveries without losing config · Rotate the secret if it leaks

Label	URL	Events	Last delivery	Status	Actions
Loading endpoints...

Verify a delivery HMAC-SHA256

Read the headers

Each POST carries X-Affix-Event, X-Affix-Timestamp, X-Affix-Delivery-Id and X-Affix-Signature.

Recompute the MAC

The signature is hmac-sha256=HEX of HMAC-SHA256(secret, "{timestamp}.{raw_body}"). Compare in constant time.

Reject stale timestamps

Drop deliveries where the timestamp is more than five minutes from now to block replays. Deliveries retry up to three times.

Build an export Streams from your session

Choose a time window and format. The file streams from your Hub session, so no API key is required while you are signed in.

What is included Account scope

Endpoints

GET /api/export/siem and GET /api/export/evidence on api.affix-io.com. Query params: since, until, format, limit.

Event types

Prove, verify, gate, attest, Merkle leaf, spend, revoke, key.revoked, webhook.delivery, plus raw API request rows where classified.

Retention

Events come from the live file-backed logs on the API host. Older rows roll off when each log hits its configured ceiling.