Skip to main content
This documentation covers the Tyviso Events API — GET and POST requests for Offers, Rewards Events, Gift After Purchase, Giveaways, and more, straight from your website or app. Pull your Tyviso data into your own reporting stack: one API key, one header, JSON or CSV out.

Authentication

X-API-Key — one header on every request. Your key is scoped to your partner ID.

Endpoints

10 across 5 groups — Campaigns, Offers API, Events, Giveaways, and More.

Formats

JSON · CSV — event endpoints accept format=csv for spreadsheet pulls.

Quickstart

Three steps to your first payload — live in about five minutes.
Every API key maps to a single partner ID, so you only ever see your own data. Nothing here exposes another partner’s events.

​
Get started

Quickstart

If you can run cURL, you can be reading live event data inside five minutes.

Authentication

How your API key works, and the three headers every request needs.

Rate Limits & Support

What to do before you hit a limit, and how to get help fast.

​
Concepts

Core Objects

The Offer, Event, and Transaction shapes referenced throughout this reference.

Event Types

What type decides, and which endpoints support which types.

Errors

401, 404, and 422 — how they behave, and the one gotcha to watch for.

​
Endpoint reference

Campaigns

Get active offers, trigger campaign push notifications.

Offers API

The full feed behind your hosted Rewards page or widget.

Events

Reward events, Gift After Purchase events, push-notification widget data.

Giveaways

Giveaway flows, code claims, giveaway event history.

MyAdvertisers

Offers for a specific partner by partner ID.

More

Postback and Gruum conversion — supported, lower-traffic endpoints.
Last modified on August 26, 2026