This documentation covers SEARCH, REVIEW, PREDUPE, and ACTIVITY. ACTIVITY and ACTIVATION are hosted on
resdefio.com and have their own base URL and x-api-key authentication. VERIFY is documented separately.1. What is Research Defender?
Research Defender protects survey data quality by identifying fraudulent, duplicate, and low-effort respondents before and during a survey. It combines digital fingerprinting, duplication detection, and open-end text analysis into a set of API products you call as respondents move through your survey flow.2. The Products
SEARCH
Fingerprinting, bot/click-farm detection, and duplication scoring.
REVIEW
Open-end text quality analysis.
ACTIVITY
Participation statistics to identify professional survey takers.
PREDUPE
Detect prior survey attempts before the respondent enters.
3. How It Fits Your Survey Flow
- At entry, call SEARCH (optionally with PREDUPE parameters) to fingerprint the respondent, detect duplicates, and check for fraud signals before they enter the survey.
- Check participation with ACTIVITY to flag respondents with abnormally high survey participation across the ecosystem.
- During the survey, use REVIEW to analyze open-ended responses for copy/paste, profanity, low engagement, and LLM-generated text.
- Apply your term logic based on the scores returned. Research Defender publishes recommended term logic for each product.
4. Protecting Your Integration
Nefarious respondents may attempt API suppression or link manipulation to bypass security checks. SEARCH offers three secured integration options to protect against this:- Server-to-server — the browser gets a token from GETTOKEN, and your server calls the SEARCH API with it, so scores and flags never reach the respondent.
- Encrypted — integrated client-side, but the results come back encrypted and are decrypted on your server.
- URL validation — integrated client-side, with a
validationvalue signed by your private key so SEARCH rejects any URL changed on the fly.
5. Next Steps
Environments & Authentication
Base URLs and how publishable and private keys are used.
API Reference
Parameters, response schemas, and a live playground for every endpoint.
