Integrate the Survey Feed API with AI
Copy the prompt below into your AI assistant — Claude, ChatGPT, Cursor, Codex, or whatever you use. It points the agent at our full, always-current Survey Feed API reference, so it works from the real documentation instead of guessing.
I'm integrating TapResearch into my app using the Survey Feed API. Read the full reference documentation at https://supply-docs.tapresearch.com/llms-survey-feed-api.txt first — it's the current, authoritative source — then help me implement it step by step, matching my project's existing structure and conventions. Follow the best-practices and testing guidance in the docs, and call out common mistakes as we go. If something isn't covered in the docs, tell me instead of guessing. Use placeholders like API_TOKEN for any credentials — don't ask me to paste real tokens or keys into this chat, and keep server-side keys out of client code and version control. Show me where to add my API token and placement tag from the TapResearch dashboard. When the integration is in place, help me write and run a smoke test for each step and debug anything that fails — I'll confirm each step is passing in the TapResearch dashboard.
Your agent reads the live docs bundle, so it always has the current integration steps — no stale copy, nothing to keep in sync.
Using a terminal or IDE agent (Claude Code, Cursor, Codex)? The Add to AGENTS.md line drops into your repo so the agent picks it up automatically. No web access in your agent? Open the full docs bundle and paste it in directly.
The Survey Feed API is the full-control path — fetching surveys, rendering them, and handling reward callbacks yourself — so there's the most to build here. Your agent can work through it with you. Review what it writes, and reach for the rest of these docs whenever you want the details yourself.
After you integrate: verify it's working
Run through these checks with help from your AI agent — it can write and run them and debug failures, but it can't see your account. So your app's Integration tab in the Publisher Dashboard is what confirms each step actually passed.
These checks register from real activity — a test postback on its own won't complete them. Add a test device first (More → Test devices).
- API request received — Make your first authenticated fetch-surveys request. The Integration tab marks this once it sees the request.
- Surveys rendered & entered — Render a fetched survey and open it in your webview so a session reaches the survey.
- Reward callback configured — Set your server-to-server postback URL.
- Survey complete & reward redeemed — Complete a test survey and confirm your callback endpoint receives the signed reward and redeems it.
If a step doesn't check off, it's the fastest signal of where the integration broke. For deeper testing guidance, see Testing & QA.