List running campaigns
Returns the campaigns that are running right now, by the same test the checkout applies: the campaign is active and today falls inside its date window. A campaign that is scheduled, paused, ended or still a draft is not returned, so an offer advertised here is one the checkout will honour.
A campaign is a discount with a budget behind it. It stops discounting once that budget is spent, which is the difference between a campaign and a promotion — a promotion runs until its end date. The budget itself is never exposed.
Use applies_to to tell where an offer is valid: online for a storefront, pos for a
till, all for both. Pass the campaign id to the order you create and the discount is
applied and validated server-side.
Authorizations
API Key Authentication
Use your API key in the Authorization header:
Key Types:
Secret Keys (Server-Side Only):
- Format:
tybrite_sk_live_*(production) ortybrite_sk_test_*(sandbox) - Full read/write access to all endpoints
- ⚠️ NEVER expose in client-side code or public repositories
- Required for: write operations, authentication, payment verification, AI recommendations
Publishable Keys (Client-Safe):
- Format:
tybrite_pk_live_*(production) ortybrite_pk_test_*(sandbox) - Read-only access (GET requests only, plus POST semantic search)
- ✅ Safe for client-side JavaScript, mobile apps, and public code
- Allowed for: browsing products, search, CMS content, pricing queries
Endpoint-Specific Requirements:
- Authentication endpoints (
/v1/auth/*): Secret key required - Payment verification (
POST /v1/payments/verify): Secret key required - AI Recommendations (
POST /v1/recommendations): Secret key required - Semantic Search (
POST /v1/search): Both key types allowed (read-only operation) - All write operations: Secret key required
- All read operations: Both key types allowed
Using a publishable key for restricted operations returns 403 Forbidden.
Query Parameters
Maximum number of campaigns to return.
1 <= x <= 100Response
The campaigns currently running.

