Write application answers

PUT 
/api/v1/applications/:applicationId/answers

Returns when the batch is stored. Writes answers onto the applicant on behalf of your profile. Every answer is recorded as verified — attesting to a value through this contract is, by definition, verifying it — and every data point must belong to the application's template; one unknown data point rejects the whole batch, and nothing is partially applied. Answers need someone to belong to: until an applicant has claimed the application, writing answers fails with 400. Writes are published to the owning profile's subscriptions as application.answers_changed, so a receiver hears its own writes echoed back. actingUserId attributes the answers in the audit trail; omitted, it falls back to the API key's identity.

Request

Responses

204

All answers in the batch were stored as verified.

400

The batch is empty, a value is malformed, a data point is outside the application's template, or the application has no applicant yet to attribute answers to.

403

404

The application does not exist or belongs to another profile.