Consent revocation and expiry: what the validator does
The consent validator checks a submitted consent object against its validation rules. It is not a consent registry or lifecycle service: keep consent state and access enforcement in your application and its relevant LFI integration.
Validate a consent object
Send a JSON object with a nested consent object. The example expiration date is illustrative; submit a future date that satisfies your consent requirements.
curl -X POST "https://khaleejiapi.dev/api/v1/openfinance/consent/validate" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "content-type: application/json" \ -d '{ "consent": { "userId": "user-123", "providerId": "lfi-001", "purpose": "account_data_sharing", "permissions": ["ReadAccountsBasic", "ReadBalances"], "expirationDate": "2027-10-01", "recurring": false, "recurringPeriodMonths": null, "sensitiveData": false, "consentMethod": "explicit_opt_in", "withdrawalMethod": "app_toggle", "dataStorageLocation": "AE", "thirdPartySharing": false } }'The endpoint evaluates the object and returns data.compliant, a summary, and an issues array. Each issue identifies a field, severity, article, requirement, and message. Errors produce compliant: false and a NON_COMPLIANT verdict. Warnings alone may produce compliant: true with COMPLIANT_WITH_WARNINGS; no issues produces FULLY_COMPLIANT.
{ "data": { "compliant": true, "summary": { "total_issues": 0, "errors": 0, "warnings": 0, "verdict": "FULLY_COMPLIANT" }, "issues": [] }, "meta": { "timestamp": "2026-11-06T00:00:00Z" }}HTTP errors
400 INVALID_BODY: the body is missing or is not valid JSON.400 MISSING_PARAMETER: the body has no object-valuedconsentproperty.403 FORBIDDEN: the API key is missing theopenfinance:consentscope.
EXPIRED or REVOKED state, map those states to HTTP 403 or 410, or purge tokens or sessions stored by your application. A validation result is not persisted consent state.What the Rulebook says about withdrawal and retention
The CBUAE Open Finance Regulation (Circular No. 03/2025), Article 22(2)(5), says a user must be able to withdraw consent at any time. Article 22(3) requires the provider to explain how to exercise that right and make withdrawal at least as simple, quick, and easy as giving consent. It also says withdrawal does not affect the lawfulness of processing before withdrawal and does not prevent retention needed for Article 13 or applicable laws.
Article 22(10) requires destruction of identifying personal User Data after its purpose is complete, subject to Article 13 record-retention requirements and mandatory retention under applicable laws, including AML laws. Article 13(3) requires records to be retained for at least five years from creation, unless applicable laws or the Central Bank require otherwise. This is not a zero-retention rule.