Skip to content

Filters and currency

Add query parameters to the feed URL to narrow what it returns or to render it in another currency.

Terminal window
curl "https://feeds.ticpro.com/example-partner.json?token=YOUR_FEED_TOKEN&dateFrom=2027-03-01&league=Premier%20League&currency=EUR"

Filters only narrow what TicPro set up for your feed. A filter on something the feed already fixes is dropped, so you can never widen a feed.

Key Narrows by
name Event name
seatType Seat type
type Event type
category Ticket category
ids Event ids
dateFrom, dateTo Event date range
dateConfirmed Whether the date is confirmed
priceMin, priceMax Price range
requirePrice Only events with a price
referenceMapPair Reference pair

Any other key is read as a segment key, for example ?league=Premier League. Which segment keys your feed supports depends on its setup. An unknown key returns 400 with the list of valid keys.

These are accepted and ignored, so a URL built for another system still works: market, includeSoldOut, includeUnpriced, hasPrice, skip, take, pageSize, sort, facets, facetMode, facetGroups, filterCounts, stats and culture. Tracking parameters starting utm_, gclid, fbclid and msclkid are ignored too.

?currency=EUR renders the feed in that currency. It takes a three-letter code.

The feed is refused with 400 when the code is not valid, or when it differs from the feed’s saved currency and the feed has a saved price filter, because that filter would then be read in the new currency. The saved currency itself is accepted and changes nothing.

Message Cause
Unknown filter "<key>". Filter keys: … The key is not a filter or a segment key. The message lists the valid keys.
Filter "<key>" has no usable value. The value is not empty but reduces to nothing once read, for example only commas. A parameter with an empty value (?league=) is ignored and returns the saved feed.
Currency must be a three-letter code, for example EUR. Invalid currency.

See Errors for all status codes.