June 3, 2026: Evalandgo evolves — new version

Your automations and Webhooks continue to work. Our API evolves with two minor changes — full details in the FAQ.

Important changes (action required)

1. Reduced set of accepted content formats

The following formats are no longer supported, either in requests or responses:

• application/hal+json
• application/vnd.api+json
• application/xml / text/xml
• application/x-yaml
• text/csv
• text/html

Supported formats: application/json and application/ld+json.

2. POST /api/v3/contacts — contactFields format changed

The contactFields field no longer accepts IRI strings. It now expects objects with field and value properties:

// Before
"contactFields": ["/api/v3/contact-fields/42"]

// After
"contactFields": [
  { "field": "/api/v3/contact-fields/42", "value": "My value" }
]

This change does not affect POST /api/v3/respondents or POST /api/v3/respondents/get-or-create, which remain unchanged.

What’s new

Partial updates with the new PATCH method

Until now, modifying a resource required a PUT request, meaning you had to send the entire object in the request body. Any omitted field was reset to null.

The PATCH method is now available on the same endpoints and lets you send only the fields you want to update. The other fields stay unchanged.

// PUT — all required fields, any omitted are overwritten
PUT /api/v3/respondents/123
{ "firstName": "John", "lastName": "Doe", "email": "john@example.com", "finish": false }

// PATCH — only the fields sent are modified
PATCH /api/v3/respondents/123
{ "email": "new@example.com" }

Note: your existing PUT requests remain unchanged and continue to work exactly as before. PATCH is an option, not a requirement.

Endpoints that support PATCH:

• PATCH /api/v3/respondents/{id}
• PATCH /api/v3/webhooks/{id}
• PATCH /api/v3/responses/datetime/{id}
• PATCH /api/v3/responses/multiple/{id}
• PATCH /api/v3/responses/nps/{id}
• PATCH /api/v3/responses/number/{id}
• PATCH /api/v3/responses/rating/{id}
• PATCH /api/v3/responses/scale/{id}
• PATCH /api/v3/responses/slider/{id}
• PATCH /api/v3/responses/text/{id}
• PATCH /api/v3/responses/unique/{id}
• PATCH /api/v3/responses/form/{responseId}/inputs/{inputId}
• PATCH /api/v3/responses/emoticon/{id}

New endpoints

• GET /api/v3/questions/item-text/{id}: retrieves a static text element on a questionnaire page.
• PUT /api/v3/responses/emoticon/{id} and PATCH /api/v3/responses/emoticon/{id}: saves or updates a response to an emoticon question.

Structured error responses

Responses with status codes 400, 404, and 422 now return a JSON body with detailed error information. Validation errors (422) include a list of constraint violations (affected field, message, code) to make debugging easier.