Skip to content

More

Changelog

Reference only. Not a decision unless cited in product/DECISIONS.md.

Changelog

Notable API and docs changes for partners.

2026-11-14

  • Door time, pass entry times and minimum per order (ENG-3339). Event create and PATCH /v1/events/{eventId} take doors_open (ISO or null): scans before it are refused not_yet_valid; null opens the door at starts_at; after the end is refused doors_open_after_end. PATCH /v1/events/tiers/{tierId} on a series pass takes admit_times (occurrence_event_id, admit_opens_at): the pass's entry time per show, which wins over the show's door time. A min_per_order above max_per_order is refused min_per_order_exceeds_max_per_order.

  • Ticket types say when they share a show's capacity. In GET /v1/events/{eventId}/tiers and GET /v1/productions/{productionId}, every day ticket type of a show with a capacity limit now carries show_remaining (seats left on the whole show, after day tickets, pass-held seats and claim blocks) and show_capacity (the show's capacity), the same numbers on every type of that show. Those types share one limit: when you add their seats left, never pass show_remaining. Omitted on shows with no capacity and on pass types. Nothing else changed.

2026-11-10

  • Series catalog: a shared seating area counts once. In GET /v1/productions/{productionId}, each show's ticket types now report seats left the way that show's own GET /v1/events/{eventId}/tiers already does. A type linked to an area (section_id set) carries area_remaining, the area's seats left (the same number on every type that shares the area), plus section_name and location_note. Its inventory_available and inventory_total now report the area too: available is the area's seats left, and total is that plus the type's own sold and held. A type on a show with a capacity limit, or with seats held by a series pass, may also carry area_remaining. Pass types are unchanged. Count a shared area once, from area_remaining.

2026-11-06

  • Seat holds: 40 chairs per IP address per event. POST /v1/seats/hold answers 429 seat_hold_limit_exceeded when the hold would leave one IP address holding more than 40 chairs of the event at once, across every session and hold_owner. A chair stops counting once its hold ends (released, expired, sold). The request limits (60 per session and 120 per IP a minute, 429 rate limit exceeded) are unchanged, and so is the ttl_seconds range. A server that holds seats for its buyers attests each buyer's IP. See Errors.

2026-10-21

  • Funnel report: email tools count as Email. In GET /v1/tenants/{tenantId}/dashboard/funnel-report, a visit tagged with an email tool's own name as utm_source (mailchimp, klaviyo and others) is Email unless its medium is paid or social; more webmail sites (Outlook 365, AOL, iCloud, Zoho, GMX, web.de) are Email too; and a landing address with Mailchimp's mc_cid and no UTMs is Email › mailchimp › that id. The rule runs when the report is read, so past visits move as well.
  • Funnel report: when a campaign landed. A channels link row, and a campaign row under a source / medium row, carries landed_day and landed_window (visitors, buyers) once it has landed: its first day with 25 or more visitors credited to it first, or 10 or more that are at least 25% of that day's visitors, counted over the whole run. The report also says email_nudge: Direct holds 40% or more of 100 or more visitors and Email has under 100. GET / PUT /v1/tenants/{tenantId}/email-nudge read and set whether the signed-in member hid that nudge on one event or series.

2026-10-20

  • Page addresses keep campaign values only. A stored landing or checkout address now keeps a value only for utm_*, axl, gclid, fbclid, msclkid, ttclid, mc_cid, org and event. Every other parameter keeps its name and loses its value, so an email tool's per-subscriber id (mc_eid, _kx, ...) is never stored. Addresses already stored are cleaned the same way. See Checkout attribution.

2026-10-15

  • Commerce pixel: name the order on checkout_start. If your own server or page creates orders (headless), pass the order id on the checkout step: axyn('checkout_start', { seriesId, orderId }) (also accepted on payment_open). AXYN then links that order to the visit it came from, so the organizer's Conversion counts it as tracked instead of "untracked". Only an order of the same organizer, for the same event or series, created in the last hour and not linked yet is linked; the id is not stored on the funnel record. Sending funnel_session_key on order create still works. See Partner commerce insights & privacy.

2026-10-14

  • Web SDK behaviour change. AxynProvider analyticsConsent now defaults to false. If your site passes nothing, the checkout funnel sends nothing to AXYN and stores nothing in the browser for analytics (no session key, no 30-day visitor id), even when the organizer turned on Analytics on partner embeds. Before, passing nothing counted as consent. To keep funnel analytics, pass analyticsConsent={true} once your cookie banner or consent tool records the visitor's Analytics consent, and false again if they withdraw it while the checkout is on the page (the stored ids are then removed; for a withdrawal elsewhere on your site, call clearFunnelVisitorKeys() from @axyn/web-sdk/telemetry). Global Privacy Control still always opts out. See Quickstart.
  • Funnel report: cities under each region. In GET /v1/tenants/{tenantId}/dashboard/funnel-report, a places region row can now have city children (key city:<CC>-<RR>:<city name>, label the city name) carrying optional latitude and longitude: the mean of that city's journeys' approximate points, rounded to 2 decimals. A city with fewer than 5 visitors folds into too_few in its region. The city comes from AXYN's network edge; the IP address is never stored. After 13 months the ids, page address and order link are removed; the city stays only in the saved counts (a city is saved only with 5 or more visitors), so a report over older dates still has cities. See Partner commerce insights & privacy.

2026-09-26

  • A partner server that calls checkout or token exchange for its buyers can now name each buyer's IP in X-Axyn-Client-IP, so the per-IP limits count each buyer instead of the server's one egress IP. Honored only for an x-api-key holding the new client_ip:attest scope, which AXYN grants. See Calling for your buyers from your server.
  • POST /v1/auth/federation/token-exchange is now limited per client IP (the same IP as the checkout limits) instead of per connecting address, so buyers behind one CDN edge no longer share a limit.

2026-09-23

  • Automatic discounts and series discounts. An organizer can set a quantity discount with no code on a show or a whole series, such as "2 for $6,000" on a pass or "4+ save 10% each", and can create discount codes for a series. Catalog ticket types gain offers[]; preview and order create apply automatic discounts with no input and return discount_lines[], offer_hints[], code_not_applied_reason and codes_not_applied; GET /v1/orders/{orderId} returns discounts[]. New GET/POST /v1/productions/{productionId}/coupons. On the Coupon resource, code, venue_event_id and max_redemptions can now be null. Existing codes behave exactly as before. See Discounts and coupons.
  • A venue's address now locks only once it has a street, a city and a time zone. PATCH /v1/tenants/{tenantId}/venues/{venueId} must leave all three set (400 venue_address_incomplete otherwise), and a venue that has a street and a city but no time zone can still add one. Before, street and city alone locked the venue, so a missing time zone could never be filled. Publish and resume still need only a street and a city. See Errors.
  • An expired coupon code now answers coupon_not_found on preview-total and order create, the same as a code that does not exist, so the error no longer tells a caller which guessed codes were real. coupon_expired is no longer returned.
  • POST /v1/orders/preview-total, voucher redeem and buyer refund requests are now limited per client IP (and per event on preview-total), counted across every server, instead of per buyer session. A fresh anonymous session no longer resets the limit. Preview-total allows 30 calls a minute from one IP for one event.
  • An event that is on sale, paused or sold out now keeps a venue with a street and a city. PATCH /v1/events/{eventId} that moves such an event to a venue with no address, or sets venue_id to null, answers 422 venue_address_incomplete or venue_required. Resuming a paused event runs the same check as publish. Before, both calls let a listed event end up somewhere guests could not find. See Errors.
  • POST /v1/tenants/{tenantId}/venues now refuses a timezone that is not a real time zone, like PATCH already did. A bad zone saved at create could never be fixed later.
  • Waitlist guide catches up with the API. The spec carries a public join, a status lookup (reference plus email), and a claim link that starts pay; organizer staff can list entries, make a soft-hold offer, and remove an entry. waitlist_join_mode now gates join (off refuses). TicketPanel still does not show Join, offers are made by staff, and AXYN sends no join or offer email yet. See Waitlist.
  • A waitlist claim link now fails closed once its hold can no longer be paid: an expired, cancelled, or failed hold answers 410 waitlist_claim_expired; a paid or refunded order answers 404. Before, a stale link could still show a price and bind a buyer to that order.

2026-09-22

  • Reloading in the middle of checkout no longer breaks pages your server builds. The SDK used to read the buyer's saved order while the page was still being built. The server could not see that order, so the server and the browser drew different screens, and React stopped with a "Hydration failed" error. Now the SDK reads the saved order right after the page loads, before the buyer sees anything.

  • PaymentReturn now waits for that saved order before it checks the payment. Before, a buyer who came back from Stripe could see their paid order marked as failed, because the check ran before the order was loaded.

  • New: useCheckoutSession() returns hydrated. It is false until the saved order has been loaded. If your own code looks for an order when the page loads, wait until hydrated is true. If your tests build a fake useCheckoutSession() value, add hydrated: true. See Stripe wrappers.

  • Reserved seats follow their ticket (ENG-1723). Void and refund approve release the seat in the same step: back to its house hold or open sale, or off sale when the event is cancelled, the ticket was scanned, or a door may still hold the old barcode. Void takes optional seat_destination, seat_house_hold_id, seat_off_sale_note and confirm_door_risk, and returns released_seats. Void now documents void_reason (the field the route always read). House-hold release and delete return seats_released and by_ticket_type. New GET /v1/events/{eventId}/seats/{seatId}/history. New read-only seat-release-preview for a ticket or refund request names each seat and its default destination before staff confirm. Seats a buyer drops from the cart go back to their house hold. See Seat lifecycle.

  • New: PATCH /v1/tenants/{tenantId}/venues/{venueId} adds an address to a venue that was saved without one. You can create a venue with just a name, but an event cannot go on sale until its venue has a street and a city. Before, there was no way to add them later, so the event was stuck. Now you send the street, city and the rest. It only fills in empty parts and never changes a part the venue already has. After the venue has a street and a city, the address is locked and this call answers 409 venue_address_locked. The Admin "New place" form now asks for the street and city up front. See Errors.

  • New: a named venue fee on an event. Set venue_fee_cents, venue_fee_label and venue_fee_reason on POST /v1/events or PATCH /v1/events/{eventId} and every paid ticket carries it. It is already inside all_in_price_cents, the event price summary and preview totals, so do not add it yourself. It is never part of fees_cents, and AXYN charges no fee on top of it. The preview response returns the amount, the label and the reason so you can show the line. Series passes pay it once per night they admit, each at that night's fee, and discounts never reduce it. Each ticket records its share as venue_fee_cents. Guardrails: at most 15% of the cheapest paid single-show ticket (passes do not count), a label from a fixed list, a required reason, nothing on free tickets or comps, and no raising it once a ticket has sold. Set it with PATCH after the event has ticket types; create refuses it, because the cap needs a cheapest paid ticket to measure against. Always send venue_fee_cents, even when you are only fixing the wording. Duplicating an event does not copy it. Orders exports and settlement gain a venue_fee_cents column. See Pricing.

2026-09-21

  • Accreditation. People apply for a Media, Industry, Artist or Sponsor pass with an apply link; staff approve, decline or waitlist; approve issues the ordinary Live Pass with no checkout. Public apply and status calls take no API key (the link and a status token are the credentials). Works for a single show or a whole series. Opt-in SDK components AccreditationApplyForm and AccreditationStatusCard. Never part of Get tickets. See Accreditation.

  • Find N and the orphan rule work with odd/even numbering (ENG-1716). Chairs sit together when their numbers differ by the row's stride (1 for 101–117, 2 for odd or even wings), so seats 12 and 14 are a pair. Voids and sold or blocked chairs are gaps. GET /v1/events/{eventId}/seat-map seats now come back in room row order (A…Z, AA, BB, then seat number) instead of text order. No field changes. See Seating.

  • Waitlist guide. Join, offer, and claim are not a sold Partner API yet. Guests pay only if they claim, once that API exists. waitlist_join_mode records organizer intent only; TicketPanel does not show Join. Find N type: waitlist is a miss enum, not signup. See Waitlist.

2026-09-20

  • Listings carry a waitlist_join_mode on /v1/events: off, sold_out, or always. off is the default and stays the default — a sold-out listing shows no waitlist button unless an organizer opts in. Unknown values are refused, never coerced. Organizers set it from the event Setup page under "Make it sell".
  • Who it is for: optional freeform listing line (max 280) on a series (GET|PATCH /v1/productions, who_it_is_for) and on an independent event (who_it_is_for on Event / EventInput). A child show may set who_it_is_for as an override; empty inherits the series line. Partner catalog show rows expose who_it_is_for_override when that night differs. Buyer EventDetail.who_it_is_for is the effective line; who_it_is_for_override is set only when this show differs. Hide when empty. This is listing copy, not a door ID check. Do not fail checkout on this string.
  • Buyer refund policy on a series. PATCH /v1/productions/{productionId} now takes refunds_enabled, refund_policy and refund_window_hours (the same presets events take) and writes them onto every date in the series. A date inside a series no longer sets its own: those three keys are rejected with HTTP 400 on POST /v1/events and PATCH /v1/events/{eventId} while the event has a production_id, and a date joining a series adopts the series policy.
  • Listing house_rules (plain text, optional) on series productions and independent events. Not on the venue. Buyer EventDetail and series GET return the key. Hide the section when empty. Child series dates cannot write it. See House rules.
  • Listings carry optional "Getting in" copy: getting_in_parking, getting_in_access, and getting_in_arrival on /v1/events and /v1/productions. Each is plain text up to 200 characters, or null. Blank stays hidden on the buyer page. See Getting in copy.

2026-09-16

  • Event hours: GET /v1/events/{eventId} now includes optional doors_open (ISO). Duration is still not a stored field. Partners format length with @axyn/web-sdk formatEventHoursParts / formatSeriesHoursOverview from the start and end they already receive. See Hours and duration.

2026-09-08

  • Checkout POST /v1/orders/preview-total now returns HTTP 409 capacity_unavailable when the requested ticket quantity is above remaining sellable. Order create already used that code. Listed-price and upgrade quotes stay price-only so a sold-out type can still show its all-in amount.

2026-09-04

  • Door-night and upgrade emails open the public Live Pass (/p/{share_code}), not the hosted confirmation page. Confirmation stays the same-browser checkout receipt.

2026-08-20

  • Buyer self-serve upgrades: guest-first eligibility, issue, pay, and cancel on /v1/ticket-url/{token}/upgrade-* plus JWT /v1/me/tickets/{ticketId}/upgrade-*. Organizer paths stay at /v1/tenants/{tenantId}/events/{eventId}/tier-upgrade-paths. Event defaults seed new drafts with allow_upgrades and upgrade_cutoff_hours on GET|PATCH /v1/tenants/{tenantId}/workspace-defaults. @axyn/web-sdk UpgradeFlow dogfoods the sold /v1 shapes. Same Live Pass URL after pay. Staff can send a 72-hour guest invite (POST /v1/tenants/{tenantId}/tickets/{ticketId}/upgrade-invites; guest opens /v1/upgrade-invites/{token}). Partner outbound ticket.upgraded is not live; poll the ticket you already hold. See Upgrade.

2026-08-15

  • Door team roster: staff list joined scanners for an event (GET /v1/tickets/scanner-roster?event_id=) and assign or clear a lane (PATCH /v1/tickets/scanner-tokens/{tokenId}/lane). Assigning a lane clears it on other active tokens for that event (organizer override). Volunteers poll GET /v1/tickets/scanner-tokens/me for assigned_lane_id (40 calls per token per minute; door poll is 5s). See Keys & login.

2026-08-14

  • Door join codes: staff fetch or mint one 6-digit code per event (GET /v1/tickets/scanner-join-codes?event_id=), rotate it (POST /v1/tickets/scanner-join-codes/rotate), and volunteers redeem it with no login (POST /v1/tickets/scanner-join-codes/redeem) to mint a unique scn_ device token. Redeem is capped at 10 guesses per IP per minute (30 per 15 minutes) in a shared Postgres attempt log, and 40 devices per active code. After join, PATCH /v1/tickets/scanner-tokens/me stores first + last name on the token label. See Keys & login.

2026-08-13

  • Organizer seating: venue house GET/PUT, apply/save (copy, not a live link), and POST /v1/events/{eventId}/seating:ready. Seated layouts (section_and_type, reserved_seat) must be seating-ready before publish. GA (general) skips the seating gate. See Organizer seating. Publish 422s: seating_not_ready, seating_inventory_required, seating_tiers_required.

2026-08-07

  • Fixed-amount coupons gain apply_mode: cart_ticket_subtotal (default, once on ticket face) or per_ticket (amount_cents × ticket qty). Create via POST /v1/events/{eventId}/coupons; immutable after create. Percent coupons ignore apply mode. See Coupons.

2026-08-04

  • Partner commerce pixel (headless Sales impressions): install no longer uses a browser API key. Enable Partner page insights in Admin, paste the snippet, gate axyn('consent') on Analytics — see Partner commerce insights & privacy and Headless API. Secret keys stay server-only (Credentials).

2026-07-24

  • Coupon stacking (per-tier opt-in): ticket tiers gain allow_multiple_coupons (default false). When every tier in the cart opts in, buyers may stack up to 5 distinct codes; allocations run in entry order against the combined cap (never more than 95% of ticket value, buyer always pays at least $5 of it). The checkout coupon field is now coupon_codes (array) on POST /v1/orders/preview-total and POST /v1/orders; the preview echo is coupon_codes. New typed 400s: coupon_duplicate, coupon_stacking_not_allowed. Orders record one redemption row per code with its allocated share of the discount.

  • Event coupons (organizer discount codes): GET/POST /v1/events/{eventId}/coupons, PATCH/DELETE /v1/events/coupons/{couponId}. Percent (max 95%) or fixed amount, total use limit, optional start/end window. Published codes are immutable — PATCH supports permanent deactivation only; DELETE only before first redemption. Reads and writes both require catalog:write scope (or event.write staff permission): codes never leak through buyer-facing read keys.

  • @axyn/web-sdk: coupon entry on the review step. New CouponCodeField (mounted by the embed review drawer automatically; hosted axyn.events pay uses TicketPanel, not this drawer), actions.applyCoupon / actions.removeCoupon + state.couponError on the checkout session, and a negative Discount line in OrderSummary. If a code is consumed between preview and place, the SDK drops it, re-prices, and explains why. Confirmation + ticket email itemize the discount.

  • Coupon redemption at checkout: optional coupon_code on POST /v1/orders/preview-total and POST /v1/orders. Preview and order responses carry discount_cents (+ coupon_code echo on preview); subtotal_cents keeps face value and the buyer pays subtotal - discount (+ fees) + tax. Discounts apply to tickets only (add-ons excluded), are capped so the buyer always pays at least 5% of ticket value and no less than $5 of it, and never touch the AXYN platform fee (calculated on face price). Typed 400s: coupon_not_found, coupon_inactive, coupon_not_started, coupon_expired, coupon_exhausted, coupon_not_applicable, coupon_below_minimum_charge. Redemption counts release automatically if a reservation expires or is cancelled before payment; paid orders keep the redemption (refunds do not restore it).

  • Live pass: rotating door code, device step-up (sid), mint / extend / confirm / resend for ticket-url bearer and /me routes.

  • Transfer: guest Send a pass (ticket-url bearer), signed-in holder path (JWT + API key on server/BFF), public claim by token or share code, pass_bearer → recipient live pass.

  • OpenAPI: …/live-qr/resend-step-up (bearer + /me); transfer issue/revoke bodies aligned to shipped fields (ttl_seconds, share_code, etc.).

  • Ticket delivery, Headless, Get started, Testing, and Anti-patterns updated for the same contracts. Secret API key still does not serve tickets.

2026-07-17

  • Headless install is two credentials only: AXYN_API_KEY + AXYN_PUBLISHABLE_KEY. API/Auth URLs are production defaults (https://api.axyn.events, https://auth.axyn.events).
  • Buyer JWT is minted in-app via signInAnonymously — not an ops-minted static token. See Credentials and Get started.
  • Anonymous white-label guest handoff documented: no AXYN login after pay; same-session /v1/me/tickets + hosted bearer email; confirmation = open pass. See Ticket delivery.
  • Public docs hardened: no internal ticket IDs, no sandbox Auth project URLs, no admin mint paths, no repo-only source paths.

2026-07-09

  • Developer docs program and docs.axyn.events portal scaffolded.
  • OpenAPI catalog sync and venue sandbox keys tracked as follow-on work.

API operation-level detail lives in the live OpenAPI at https://api.axyn.events/openapi.json. SDK history will land with @axyn/web-sdk publish versions.