Ticket products

Retrieve an event’s ticket products and understand purchased ticket records.

A product describes something offered by the ticket shop. An attendee’s order line records a purchase of a product. They share a product UUID, but a purchased ticket can retain its original title and price after the product changes.

List products

curl --user "$PAYDRO_EMAIL:$PAYDRO_PASSWORD" \
  --header 'Accept: application/json' \
  "$PAYDRO_ORIGIN/$EVENT_ID/products/index.json"

The response is a JSON array of product objects. Common fields include id, category_id, title, description, price, stock, visible, available_from, available_till, and package_flag. Additional pool, package, and metadata information may be present.

Interpret availability

A product’s stock and availability fields describe the current offer. They do not reserve inventory for your integration. Let the Paydro ticket shop validate availability during checkout, particularly when products share pools or belong to packages.

Read product availability for computed current_stock, unlimited capacity, pending holds, shared-pool usage and sales-window rules. Use product management to create, edit, remove and reorder tickets.

Match purchases

Match an attendee’s product_id or compact pid to the product ID. Keep the archived purchased product label when showing historical tickets. A product can be changed or removed while an order line remains relevant.

Use the shop for sales

Use ticket shop embedding for visitor registration and payment. The reference includes organizer product management; visitor checkout and inventory reservation still use the ticket shop.