Survey Feed API

The Survey Feed API is the only TapResearch integration path where you send a participant's profile up front to impanel them, then fetch the surveys they qualify for and render those survey tiles inside your own UI. You stay in control of profiling, the survey list, and the participant experience end to end.

Creating your app

In the Publisher Dashboard, create a new app and select Survey Feed API. See the Setup checklist for the full flow.

Not the Eligibility API

The Survey Feed API returns survey data for a profiled participant. It is a different product from the Eligibility API, which answers a yes/no "does this user have an offer?" check. The two were historically both referred to as the "Supply API" — they are not the same surface. If you only need an eligibility check before sending a user, use the Eligibility API instead.

How it works

1. Look up countries & qualifications. Call /countries and /qualifications to learn what profile data you can collect.
2. Impanel the participant. POST their profile to /players/impanel so TapResearch can match surveys — or skip this and let TapResearch profile them.
3. Fetch surveys. Call /campaigns to get the surveys the participant qualifies for.
4. Render the tiles. Display the surveys in your own UI and send the participant into one.
5. Rewards arrive via postback. When the participant earns a reward, TapResearch notifies your backend with a server-to-server postback.

Two ways to profile

You pass profile data

Collect profiling data from your users and send it via the Impanel endpoint; TapResearch uses it to match surveys. Uses multiple endpoints — countries & qualifications, impanel, and campaigns.

Start with Impanel →

TapResearch handles profiling

Skip collecting profile data — GET /campaigns returns a profile tile that runs TapResearch's built-in profiler, or a list of surveys when pre-profile surveys are on. It's the only required endpoint.

Fetch surveys →

Pre-profile surveys

When TapResearch handles profiling, participants who haven't completed the TapResearch profiler yet can still see real surveys. Instead of returning only the profile tile, GET /campaigns returns a list of surveys.

How it works for the participant:

1. The participant opens any survey tile from the list.
2. They complete the TapResearch profiler.
3. They're redirected into the survey they originally chose — or, if their profiler responses mean they no longer qualify for it, into a different survey tile with similar metrics instead.

You don't need to do anything extra — render the tiles and use each survey's offer_entry_url as you normally would.

• On by default. Pre-profile surveys are enabled by default for Survey Feed API apps. To change this for your app, contact your TapResearch account manager.
• Fallback to the profile tile. If no surveys are available yet for a participant who hasn't been profiled, /campaigns returns just the profile tile, as before.
• Shorter lists in some countries. In some countries, the pre-profile list may be shorter until the participant is profiled.
• After profiling. Once the participant has completed the profiler, they get the normal survey list.

When to use it

Use the Survey Feed API when you want to:

• Render survey tiles inside your own UI, fully styled by you.
• Send participant profile data up front to target surveys (impanel) — or hand profiling to TapResearch.
• Stay in control of the survey list and participant experience end to end.

Reach for a different path if you need:

• A simple yes/no eligibility check before sending a user — use the Eligibility API.
• The fastest low-code launch — use the Hosted Link.
• Native mobile placements — use the SDK.

What you need

The base URL for every endpoint in this API:

https://api.tapresearch.com/supply_api/v4

• An API token for your app, from the Publisher Dashboard (Settings → API settings).
• For /players/impanel, a security hash (sech) generated server-side from your API secret. The secret should never be sent in any request — use it only to compute the sech. See Authentication.
• All requests must be made over HTTPS.

Next steps

Endpoint	Method	Description
/countries	GET	List supported countries and their IDs.
/qualifications	GET	Retrieve qualification questions per country.
/players/impanel	POST	Register a participant and store qualification responses.
/campaigns	GET	Fetch available surveys for a qualified participant.

• Authentication & request signing — the API token header and the sech security hash.
• Redirect URLs — where participants land after a survey, and how to verify the redirect.

After a participant completes a survey, rewards are reported to your backend — see Handling rewards for the postback payload and signature validation.

Support

For credentials, redirect configuration, or other questions, contact your TapResearch account manager or email developers@tapresearch.com.