Courier providers. Payment devices. Third-party integrators. Outbound webhooks you subscribe to. Inbound webhooks Andromeda calls on your endpoint, signed with HMAC-SHA256 so you can verify every byte.
Every event on the platform. Delivered, signed, idempotent, with a retry policy you can tune.
Courier providers deliver 订单 (Uber Direct first-party; others via Stuart or Andromeda-managed dispatch). Payment devices are Stripe Terminal readers bound to a location. Third-party integrators are external systems (your CRM, your accounting pipe, a bespoke BI tool) authorised against your tenant. Webhooks are the inbound channel for everything that happens — subscribe, receive, verify signature, acknowledge.
Subscribe to any subset. Every event carries the same outer envelope — eventId, eventType, occurredAtUtc, organizationId, data.
X-Andromeda-Signature: sha256=<hex>. Compute HMAC-SHA256 of the raw request body using your webhook secret and compare in constant time. Reject mismatches with 401 Unauthorized. Never trust the payload before verification.
Subscribe to a webhook. Verify a signature. Book a courier. Register a Stripe reader. Listen for an order event. Handle a retry cleanly.
Tell Andromeda where to deliver events. You pick the URL, the event types, and an HTTPS endpoint on your side that can respond within 5 seconds. The response includes the signing secret — shown once, store it safely.
PROTECT_BLOCK_11_ENDResponse — 201 Created
PROTECT_BLOCK_12_END
Compute HMAC-SHA256 over the raw request body using your stored secret, compare against the X-Andromeda-Signature header. Reject mismatches. Reject bodies older than 5 minutes to prevent replay.
PROTECT_BLOCK_14_END
Get a quote first (distance, ETA, price), then create the job. Andromeda handles the handshake with Uber Direct or Stuart; you just get status events back on the courier-job.status.changed webhook.
PROTECT_BLOCK_16_ENDStep 1 response — 200 OK
PROTECT_BLOCK_17_ENDStep 2 — book the job
PROTECT_BLOCK_18_ENDStep 2 response — 202 Accepted
PROTECT_BLOCK_19_END
Bind a Stripe Terminal reader to a location so in-store and kiosk 支付 route to it. Andromeda handles the Stripe Connect onboarding and reader registration; you just tell us the reader ID and where it lives.
PROTECT_BLOCK_20_ENDResponse — 201 Created
PROTECT_BLOCK_21_END
Andromeda retries on 5xx and timeouts. Use eventId as your idempotency key — upsert, don’t insert. Ack fast (200 OK under 5s), process asynchronously if you can’t.
PROTECT_BLOCK_23_ENDInbound payload shape
PROTECT_BLOCK_24_END
If your endpoint returns non-2xx or times out, Andromeda retries with exponential backoff for 24 hours. You can inspect every attempt, manually replay failed deliveries, and rotate the signing secret without downtime.
PROTECT_BLOCK_25_ENDResponse — 200 OK
PROTECT_BLOCK_26_ENDReplay a 外送
PROTECT_BLOCK_27_ENDRotate the signing secret
PROTECT_BLOCK_28_END
Auth, environments, your first API call.
产品s, modifiers, prices, allergens, deals.
Live 订单, history, refunds, webhooks.
Profiles, loyalty progress, marketing segments.
Sales metrics, operational reports, BI exports.
API surface, auth, the platform at a glance.
Test environment, sandbox tenant, sample data, real endpoints. No commitment.