Discounts

Discounts allow organizers to create checkout codes that reduce the price of eligible orders or items. A discount can be configured as a percentage or fixed amount, with optional usage limits, active dates, checkout availability, and restrictions for specific events, ticket types, products, or memberships.

Most integrations use this API to issue customer-entered discount codes for promotions, customer-specific offers, or fixed-amount credits.

Authentication

This endpoint requires authentication using a Showpass token:

Authorization: Token YOUR_API_TOKEN

Endpoints

The base URL for all discount endpoints is:

https://www.showpass.com/api/venue/{venue_id}/financials/discounts/

Path Parameters

Discount Types

Note: Most integrations should create type: 1 discounts. Other discount type values may appear on existing records returned by the API, but those values represent specialized or system-managed Showpass workflows and are not documented as public create workflows here.

Request Body (Create / Update)

Recommended create shape: For a standard checkout code, set type to 1, choose one discount value (percentage or amount), add redemption limits only when needed, and include item restrictions only when the code should apply to specific inventory.

Apply Methods

Allowed Checkouts

Default: If allowed_checkouts is omitted, the code can be used in both box office and public checkout.

Restricting Eligible Items

Use permission_type and event_discount_permissions to control which items a discount can apply to.

The default permission type is disc_level_ticket_type.

Common pattern: restrict a code to selected ticket types for one event.

Key fields in this shape:

• permission_type: set to disc_level_ticket_type.
• event: the event ID that the code applies to.
• tt_discount_permissions: the ticket types eligible for the discount.

{
  "permission_type": "disc_level_ticket_type",
  "event_discount_permissions": [
    {
      "event": 12345,
      "tt_discount_permissions": [
        {
          "ticket_type": 67890
        },
        {
          "ticket_type": 67891
        }
      ]
    }
  ]
}

Each event_discount_permissions entry can target one of:

Each nested tt_discount_permissions entry can target one of:

Note: Omit item restrictions when a code should apply broadly. Include nested permissions only when the code should apply to specific inventory.

Auto Discounts

Auto discounts are not customer-entered codes. They are automatically applied when a basket meets configured requirements.

Create an auto discount with type: 8 and a discount_rules array. Each rule defines a basket or item threshold and the discount that applies when that threshold is met.

Rules must follow these constraints:

• Auto discounts require discount_rules.
• Non-auto discounts cannot include discount_rules.
• All rules in one auto discount must use the same limit_type.
• Rule ranges cannot overlap.
• Each rule must use either amount or percentage, not both.
• The venue must have auto discounts enabled and be on an eligible pricing tier.

Response Fields

Filtering and Search

Search

Use search to match discount code or description:

GET /api/venue/{venue_id}/financials/discounts/?search=SKYLINE

Filters

Pagination

Results are paginated with a default page size of 20. The response includes count, next, previous, and results.

Ordering

Use ordering with updated, created, id, or is_public. Prefix the field with - for descending order.

GET /api/venue/{venue_id}/financials/discounts/?ordering=-created

Default ordering is newest first by ID.

Business Rules

• Code normalization — Submitted codes are uppercased. Generate URL-safe, checkout-safe code strings before sending them.
• Uniqueness — Codes are unique per venue, case-insensitively.
• Dates — ends_on must be after starts_on when both are provided.
• Type changes — type cannot be changed after creation.
• Used discounts — After a discount has been used, code, amount, and percentage cannot be changed.
• Delete behavior — DELETE soft-deletes the discount, sets is_public to false, and removes the discount from normal list and detail responses.

Error Responses

400 Bad Request

Returned for validation failures:

// Duplicate code for the venue
{
  "detail": "A discount with this code already exists."
}

// Invalid active date range
{
  "ends_on": ["End date must occur after start date"]
}

// Auto-discount rule sent with a standard discount
{
  "detail": "Discount Rules: Only auto discount can have rules."
}

Integration Patterns

The patterns below use standard customer-entered discounts (type: 1).

Event-Specific Promotion

Use this when a campaign should apply only to selected events or ticket types.

Recommended setup:

• percentage or amount
• Optional starts_on and ends_on
• permission_type: "disc_level_ticket_type"
• event_discount_permissions scoped to the intended event or ticket types

The API examples panel shows a complete request for this pattern.

Customer-Specific Code

Use this when an integration needs to issue a unique code to a single customer.

Recommended setup:

• Unique code
• limit: 1
• per_user_limit: 1
• Optional item restrictions if the code should only apply to specific inventory

Fixed-Amount Credit or Make-Good

Use this when a customer should receive a fixed dollar amount off a future purchase.

Recommended setup:

• amount set to the credit value
• percentage: "0.00"
• Redemption limits based on how the code should be redeemed
• Optional item restrictions if the credit should only apply to specific inventory

Retiring a Code

Use this when a code should no longer be redeemable.

Options:

• Set is_public to false with PUT when the record should remain retrievable by ID.
• Use DELETE when the code should be soft-deleted and removed from normal list and detail responses.