New Endpoint: Retry Respondents
POST /v3/retryRespondents- Retry specific quality checks for a list of respondents within a survey.
API v3 Released: OES v3 with Enhanced Category Detection and Effort Scale
🔥 OES v3 Now Available in ReDem API v3
We’re excited to announce the release of ReDem API v3, featuring a major upgrade to the OES (Open-Ended Scoring) quality check system. This release introduces improved category definitions, enhanced scoring accuracy, and a new effort scale metric.All version 3 endpoints are now accessible via the/v3 path (e.g., /v3/addRespondent), ensuring a clean separation from previous versions.🚀 What’s new in OES v3?
OES v3 introduces refined category definitions with clearer boundaries to reduce false positives and false negatives. The new categories are:- VALID_ANSWER: Responses that adequately address the question
- NO_ANSWER: Responses that provide no meaningful information
- BAD_LANGUAGE: Responses containing inappropriate or offensive language
- GIBBERISH: Responses that are nonsensical or incoherent
- OFF_TOPIC: Responses that do not address the question asked
- AI_SUSPECT: Responses that appear to be AI-generated
- WRONG_LANGUAGE: Responses in an unexpected language
- DUPLICATE_ANSWER: Responses that duplicate previous answers
- DUPLICATE_RESPONDENT: Responses that duplicate other respondents’ answers
Key improvements in OES v3:
- Clearer category boundaries: Refined detection logic reduces false positives and false negatives across all categories, providing more accurate quality assessments.
- Enhanced scoring system: OES v3 introduces an effort scale (LOW, MEDIUM, HIGH) that factors into the final quality score. For VALID_ANSWER and NO_ANSWER categories, the effort level directly influences the score calculation, providing more nuanced quality metrics.
🔄 Backward Compatibility: How do v1 and v2 work?
Version 1 and version 2 endpoints remain available but use the legacy OES v2 classification system, which has less precise category boundaries and does not include the effort scale metric.⛔ Deprecation Notice
- API v1: Will be deprecated within 7 days of this notice. Please migrate to v2 or v3 immediately.
- API v2: Will be deprecated on January 15th, 2026. We strongly encourage all teams and integrators to migrate to v3 endpoints before that date to take advantage of the improved OES accuracy and scoring system.
New Endpoint: Update Respondents Excluded Status
POST /v2/updateRespondentsExcludedStatus- Update the exclusion status of one or more respondents within a specific survey.
New Endpoints: Delete Surveys and Delete Respondents
POST /v2/deleteRespondents- Delete one or more respondents from a survey and clean up related data.POST /v2/deleteSurveys- Delete one or more surveys and all associated data.
API v2 Released: Consistent CHS Question IDs Supported
🔥 New Versioning Layer Introduced Across the ReDem API
We’re excited to introduce ReDem API v2 — a structured versioning layer that enables long-term enhancements while preserving backward compatibility with current integrations.All version 2 endpoints are now accessible via the/v2 path (e.g., /v2/addRespondent), ensuring a clean separation from legacy endpoints.🚀 What’s new in v2?
In version 2, each CHS interview entry must explicitly include the associatedquestionId.questionId a required field in CHS interviewData, you now have:- Consistent identifiers across all respondents
- Clear mapping between survey questions and CHS results
🔄 Backward Compatibility: How does v1 work?
In version 1, sincequestionId is not part of the schema:- The system auto-generates
questionIdslikeQ1,Q2, etc. uniquely for each respondent, making cross-respondent comparisons unreliable.
⛔ Deprecation Notice: API v1
Version 1 of the ReDem API will be deprecated starting 16th September 2025.We strongly encourage all teams and integrators to migrate to v2 endpoints before that date to avoid any disruption.API endpoint updates
The POST /addRespondent endpoint has been updated to rename parameters in the cleaning settings, changing from camelCase to UPPERCASE_UNDERSCORE formatting.The following is an example of the new cleaning settings object:API endpoint updates
The following API endpoint changes have been implemented to improve consistency and standardization: POST /respondent/add → POST /addRespondent -
The
interactionDatafield withindataPoints→qualityCheck: BAShas been modified to support additional interaction types. Now, it has been expanded to include bothKEYSTROKEandCOPY_AND_PASTEinteractions, enhancing tracking capabilities. - Enhanced the request body cleaning settings by allowing activate/deactivate options for each quality check and enhanced cleaning settings by introducing Behavioral Analytics Score (BAS) along with its categories.
- Renamed the Fake Answer category in Open-Ended Score (OES) to AI-Generated Answer.
- We have enhanced the response structure by adding a field to retrieve Behavioral Analytics Score (BAS) results.
GET /respondent/getRespondent → POST /getRespondent - Previously with
GETrequest we pass thesurveyNameandrespondentIdas a path parameters. Now we pass it in the request body.
GET /respondent/getAllRespondents → POST /getAllRespondents - Previously with
GETrequest we pass thesurveyNameas a path parameter. Now we pass it in the request body.
GET /survey/stop → POST /stopSurvey - Previously with
GETrequest we pass thesurveyNameas a path parameter. Now we pass it in the request body.
GET /respondent/estimation → POST /creditCalculation -
Introduced a new variable,
BASDataPoints, to specify the number of BAS data points required for credit calculation when evaluating a respondent. -
Rename the variable
CHSInterviewstoCHSAnswersin the request body. -
We have introduced a new response structure for the
POST /creditCalculationendpoint, improving clarity by renaming several fields for better self-explanatory representation.
Enhanced the quality checks by introducing Behavioral Analytics Score (BAS)
We have enhanced the quality checks by introducing Behavioral Analytics Score (BAS) to evaluate the respondent’s behavior and provide a score and categories based on the behavior.- Removed the Copy-Paste category from Open-Ended Score (OES) and incorporated it under Behavioral Analytics Score (BAS).
Streamlined the API response in error cases
When a request fails due to invalid input or other errors, the all API returns a 400 Bad Request status code. The response includes a descriptivemessage explaining the issue and an error object containing additional details to aid in diagnosing and resolving the problem.ReDem 3.0 API - Initial Release
This initial release of the ReDem API empowers you to seamlessly integrate ReDem into your workflows and applications. As the backbone of our platform, the API provides direct access to all ReDem features, from real-time data insights to smooth integration with existing systems.Since the ReDem Application is entirely powered by this API, anything you can do in the app, you can also achieve programmatically—without limitations, unlocking endless possibilities!🎉 Key Endpoints
-
POST /respondent/add- Add a respondent to a survey. -
GET /respondent/getRespondent- Get a respondent’s details. -
GET /respondent/getAllRespondents- Get all respondents for a survey. -
GET /survey/stop- Stop a survey. -
GET /respondent/estimation- Get a respondent’s estimation.

