Submit MiCA Consent
Submit MiCA Consent is an authenticated API call that records the time an EEA user who completed KYC before MiCA gave the one-time MiCA consent.
Call it when the Get Additional Requirements API returns a form with type: CONSENT. Before calling it, show the user the consent screen described in MiCA Changes for EEA Users, with their data and the two consents: data processing, and Transak’s Terms of Use and Privacy Policy.
consentedAt is the time the user agreed, not the time of the request. It must be in ISO 8601 format with a time zone offset (for example 2026-11-26T10:15:00Z), cannot be in the future, and cannot be earlier than Transak’s MiCA go-live date.
After a SUBMITTED response, call the Get KYC Requirement API again to continue the KYC flow. A FAILED status (still HTTP 200) means the consent was not recorded, so retry the request. Validation and authentication problems return a 4xx error.
KYC Reliance using API: send the consent in the consent object of the Identity Details API instead.
Authentication: use either Partner Auth (Auth Reliance), which sends x-access-token and x-user-identifier, or Transak Auth, which sends the user’s authorization token. Do not send both. See the headers below.
Headers
End user’s originating IP. More details here
Partner Auth (Auth Reliance). Your Partner Access Token. Send it with x-user-identifier, and do not send authorization. See Auth Reliance Flows and how to create a Partner Access Token.
Partner Auth (Auth Reliance). The email address of the user you authenticated. Send it with x-access-token.
Request
The time the user agreed, in ISO 8601 format with seconds and a time zone offset: Z or ±HH:mm, for example 2026-11-26T10:15:00Z, 2026-11-26T10:15:00.000Z or 2026-11-26T11:15:00+01:00. Milliseconds are optional.
Response
200 - Success