Skip to content

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

  1. A self-serve test API key from Admin -> Settings -> Developer. It starts with axyn_sk_test_ and is stored as AXYN_API_KEY. Contract: Credentials.
  2. Buyer JWT minted in your app via signInAnonymously() (not a static ops JWT). See Get started.
  3. Stripe test cards. Sandbox orders return a test PaymentIntent client secret.
  4. Optional: Postman collection from https://api.axyn.events/postman_collection.json.
  5. Optional: OpenAPI at https://api.axyn.events/openapi.json or Scalar at https://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

  1. Mint a test key in Admin Developer settings. Confirm it starts with axyn_sk_test_.
  2. GET /v1/events/{eventId} and GET /v1/events/{eventId}/tiers with catalog:read (you need a known sandbox event id; there is no public event list in the current OpenAPI).
  3. Mint a buyer JWT with the publishable key + Auth URL default.
  4. Optional: POST /v1/orders/preview-total to show the all-in before create.
  5. Create an order with buyer JWT + Idempotency-Key and the OpenAPI body (venue_id, venue_event_id, payment_method, lines).
  6. POST .../payments/start, then pay with a Stripe test card such as 4242 4242 4242 4242.
  7. POST .../verify-payment and GET /v1/me/tickets.
  8. 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.
  9. Optional: open the same pass on a second device and complete email step-up (sid confirm / resend). See Live pass.
  10. Optional: Send a pass from the ticket page, claim with the link or share code, and open the recipient live pass. See Transfer.
  11. Door: POST /v1/tickets/validate with x-scanner-token, or POST /v1/tickets/scan with a staff JWT. Never use the tenant API key. Copy-paste examples: Get started.
  12. Confirm you never logged raw secrets, ticket-url bearers, or claim tokens.
  13. 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 an axyn_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.

Next