1. Home
  2. Docs
  3. Data Subscriber API Documentation
  4. Endpoints Reference
  5. POST /consents

POST /consents

Send us the consumer’s consent. Note that this request does not have a JWT in the headers, and must be executed from your frontend application.

Note. Multiple calls with the same “usecase” for the same Person will result in only the most recent consent to be stored.

Headers

Name Value
Content-type application/json

Body

Name Value
signature string. Must be generated from GET /consents/signature.
usecase string. Valid are: “banking”, “auth”, “income”, “paymeback”.
text string. The language the consumer has accepted.

Response status

Code Value
200 OK
403 Not authorized (signature not valid).
400 Bad input (usecase or text).

How can we help?