Skip to main content
POST
Record customer consent

Body Parameters

Example Request

Response

Notes

  • Each consent record is immutable for audit purposes. To revoke consent, use the Revoke Consent endpoint.
  • Recording consent with granted: false creates an explicit denial record, which differs from revoking a previously granted consent.
  • Providing ip_address and user_agent is strongly recommended for GDPR and compliance audit trails.
Ensure you collect consent before sending marketing communications. Recurso will block outbound messages to customers without the appropriate consent on record.

Authorizations

Authorization
string
header
required

Tenant API key obtained from POST /auth/register or POST /v1/developer/keys.

Body

application/json
customer_id
string<uuid>
required
Available options:
recurring_billing,
email_marketing,
data_processing,
terms_of_service,
privacy_policy
granted
boolean
required
subscription_id
string<uuid>

Exact text shown to the customer. Defaults to the standard recurring-billing text.

Response

Consent recorded.

id
string<uuid>
tenant_id
string<uuid>
customer_id
string<uuid>
subscription_id
string<uuid> | null
Available options:
recurring_billing,
email_marketing,
data_processing,
terms_of_service,
privacy_policy
granted
boolean
granted_at
string<date-time>
revoked_at
string<date-time> | null
ip_address
string
user_agent
string

Exact text shown to the customer.

version
string

Version of the consent text.

created_at
string<date-time>
updated_at
string<date-time>