API Redirect Statuses
When TapResearch redirects a participant back to your platform, we include a status value that explains why the participant returned. Redirects fall into three stages: session checks, pre-match checks, and post-match outcomes.
For session checks and pre-match checks, all redirects return with a blank tid (match ID) because no reward is issued. Post-match outcomes always include a tid since most result in a reward and the value supports de-duplication.
1. Session Checks (Immediate Returns)
These checks run as soon as the participant loads the entry URL. If anything looks suspicious — unusual activity patterns, mismatched regions, unsupported devices, or risky behavior — the participant is returned immediately.
| Code | Status | Description |
|---|---|---|
| 19 | ZIP / IP Mismatch | The participant’s ZIP code doesn’t match their detected IP region. |
| 20 | Device/IP Activity Limit | This device or IP has exceeded safe activity levels in the past 24 hours. |
| 21 | IP Blocked | The participant’s IP is blocked due to risk or abuse. |
| 29 | IP Activity Limit (Completed) | This IP has too many recent completions across surveys. |
| 30 | IP Activity Limit (Participant) | This participant’s IP has had too many sessions. |
| 31 | Unsupported Device | The participant opened a mobile-only integration on desktop. |
| 32 | Modified User Agent | The participant changed their browser/user agent mid-session. |
| 33 | Underage | The participant does not meet the minimum age requirement. |
| 34 | Quality Blocked | Past behavior indicates quality risks; session blocked. |
| 38 | Fraud Blocked | Fraud-like signals detected. |
| 52 | Location Validation Block | Participant failed location checks (used to detect VPNs/proxies). |
2. Pre-Match Checks (Before the Survey)
These checks happen after session checks pass but before matching the participant to a live survey.
| Code | Status | Description |
|---|---|---|
| 5 | Unqualified | The participant did not qualify before entering the survey. |
| 6 | Over Quota | The quota closed before the participant entered the survey. |
| 8 | Traffic Throttled | System predicted the participant would hit traffic limits. |
| 27 | Entry Term | The participant failed partner-level eligibility checks. (Only pre-match code that may include a tid.) |
3. Post-Match Outcomes (After Matching or Survey Interaction)
These statuses reflect what happened after a match attempt or after the participant interacted with the survey.
| Code | Status | Description |
|---|---|---|
| 1 | Complete | The participant completed the survey. |
| 2 | Disqualified | The participant was screened out based on targeting requirements. |
| 3 | Over Quota | The survey reached its quota while the participant was in progress. |
| 4 | Survey Quality Term | Participant failed survey-level quality or consistency checks. |
| 10 | System Quality Term | Internal system-level quality checks triggered a termination. |
| 41 | Invalid Security Hash | The participant returned with an invalid or tampered security hash. |
4. Profile Completion
For partners who rely on TapResearch to collect participant profile data instead of calling /players/impanel.
| Code | Status | Description |
|---|---|---|
| 61 | Profile Complete | The participant finished the TapResearch profile flow and is ready for survey matching. |