Request an ENO browser confirmation for processing-consent changes

​

Requires users:write, a current organisation whole-record grant and existing current patient-accepted onboarding terms. Access stores the proposed changes without changing effective consent. The patient authenticates in ENO and explicitly approves or rejects the request. Unrequested choices and disclosure grants remain unchanged. Requests expire after 24 hours; newer patient choices, revoked authority and erasure prevent confirmation. Idempotency-Key is scoped to the application, organisation, Cell, patient and request payload; an identical replay returns the original request with its current status, while changed input conflicts. This is a confirmation request, not an asynchronous processing operation or an effective consent receipt.

Path Parameters

Headers

Body·

required
application/json
  • Properties: 3

Responses

  • application/json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
Request Example for post/v1/users/{userId}/consents
curl 'https://api.dev.eno.health/v1/users/{userId}/consents' \
  --request POST \
  --header 'Idempotency-Key: ' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "version": "",
  "processing": {
    "labReports": true,
    "aiInterview": true,
    "wearables": true
  }
}'
{
  "id": "string",
  "status": "pending",
  "confirmationUrl": "https://example.com",
  "expiresAt": "2026-11-16T18:04:15.836Z",
  "decidedAt": null
}
Partner API reference · Check your integration’s enabled capabilities before making requests.