More
Testing
Reference only. Not a decision unless cited in product/DECISIONS.md.
Testing
Prove your integration in sandbox before you touch production keys.
Who this is for
Venue engineers preparing a go-live checklist.
What you need
- A self-serve test API key from Admin -> Settings -> Developer. It
starts with
axyn_sk_test_and is stored asAXYN_API_KEY. Contract: Credentials. - Buyer JWT minted in your app via
signInAnonymously()(not a static ops JWT). See Get started. - Stripe test cards. Sandbox orders return a test PaymentIntent client secret.
- Optional: Postman collection from
https://api.axyn.events/postman_collection.json. - Optional: OpenAPI at
https://api.axyn.events/openapi.jsonor Scalar athttps://api.axyn.events/docs.
Sandbox uses the same production API and Auth hosts as live:
https://api.axyn.events and https://auth.axyn.events. The test key routes
traffic to your sandbox twin. Do not invent hosts or reuse another partner’s
credentials.
Quick smoke (catalog)
With your axyn_sk_test_... key and a known sandbox event id:
curl -sS "https://api.axyn.events/v1/events/$EVENT_ID" \
-H "x-api-key: $AXYN_API_KEY"
Then complete Get started with a buyer JWT from
signInAnonymously() against the default Auth URL,
https://auth.axyn.events.
Checklist
- Mint a test key in Admin Developer settings. Confirm it starts with
axyn_sk_test_. GET /v1/events/{eventId}andGET /v1/events/{eventId}/tierswithcatalog:read(you need a known sandbox event id; there is no public event list in the current OpenAPI).- Mint a buyer JWT with the publishable key + Auth URL default.
- Optional:
POST /v1/orders/preview-totalto show the all-in before create. - Create an order with buyer JWT +
Idempotency-Keyand the OpenAPI body (venue_id,venue_event_id,payment_method,lines). POST .../payments/start, then pay with a Stripe test card such as4242 4242 4242 4242.POST .../verify-paymentandGET /v1/me/tickets.- Open the hosted live pass from the ticket email (or confirmation bearer). Confirm the door code rotates; do not rely on a buy-time screenshot.
- Optional: open the same pass on a second device and complete email step-up
(
sidconfirm / resend). See Live pass. - Optional: Send a pass from the ticket page, claim with the link or share code, and open the recipient live pass. See Transfer.
- Door:
POST /v1/tickets/validatewithx-scanner-token, orPOST /v1/tickets/scanwith a staff JWT. Never use the tenant API key. Copy-paste examples: Get started. - Confirm you never logged raw secrets, ticket-url bearers, or claim tokens.
- Optional seated catalog: follow Organizer seating against sandbox (apply house, mark seating-ready, publish). Skip this on GA events.
Fixtures
If you use the Web SDK, its fixture clients are for embed UI work without a
live catalog. Headless API tests should hit your sandbox twin on
https://api.axyn.events
(Headless API).
AXYN first-party (axyn.events) — internal
GoFeast/AXYN dogfood on web-axyn uses golden tri-layout fixtures (GA,
area, reserved × six house shapes). Seeds and env vars:
ticketing-service/scripts/README-e2e-fixtures.md. Local orchestration:
./scripts/axyn-ui-e2e-local.sh --buyer-only plus
npm run test:buyer:e2e -w @seat/ticketing-service. Not part of partner
sandbox keys — internal DEV/staging QA only.
Common mistakes
- Using
axyn_sk_live_...keys in sandbox experiments. - Pointing at
https://sandbox.api.axyn.events; sandbox uses the production API host with anaxyn_sk_test_...key. - Asking ops for a static buyer JWT instead of minting anonymously.
- Skipping verify-payment and assuming the webhook alone is enough in test.
- Committing test keys to git.