iubenda Consent Solution API

Name: iubenda Consent Solution API API
Brand: iubenda Consent Solution API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthorizationapiKey17 EndpointsREST

For Agents

Record and retrieve user consent events, manage subject profiles, and attach legal notices to a consent database that satisfies GDPR audit requirements.

Quickstart

Get started with iubenda Consent Solution API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"record user consent for gdpr"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with iubenda Consent Solution API API.

Record consent events with proof documents and legal notice references for GDPR audit trails

Retrieve the most recent consent state for any subject by ID before processing personal data

Manage subject profiles including identifiers, preferences, and contact information

List and filter consent records by subject, legal notice, or timestamp range

GET STARTED

Start building with iubenda Consent Solution API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for iubenda Consent Solution API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for iubenda Consent Solution API, keeping it validated and agent-ready. The iubenda Consent Solution API records and retrieves consent actions performed by website and app users, who are tracked as subjects within the platform. It exposes endpoints for storing user consents, managing subject profiles, attaching legal notices and proof documents, and retrieving the most recent consent state for any subject. Designed to satisfy GDPR and other privacy regulations, the API operates at 50 requests per second with a daily ceiling of 108,000 calls per private key.

Use Cases

Patterns agents use iubenda Consent Solution API API for, with concrete tasks.

★ GDPR Cookie Consent Logging

Record cookie banner consent events with the exact legal notice version shown to the user, the consent preferences chosen, and a timestamped proof document. Each event is stored against a subject identifier so audit teams can produce a defensible record of consent for any user on demand. Integration with a banner SDK takes hours; the consent database is the long-term audit store.

Submit a POST /consent event for subject_id 'user-1234' referencing legal_notice version 'v3' with preferences {marketing: true, analytics: false}

Subject Access Request Fulfilment

When a user submits a data subject access request, retrieve the full consent history for that subject including all recorded preferences, legal notice versions, and proof documents. The API returns subject metadata plus the latest consent payload so privacy teams can respond to access and erasure requests within the regulatory deadline.

Call GET /subjects/{id} followed by GET /subjects/{id}/consent/last for the requesting user and return a structured export

Legal Notice Versioning

Maintain a versioned library of privacy notices, terms of service, and cookie policies. Whenever a notice changes, register the new version through the API so subsequent consent events bind to the exact wording the user accepted. This produces a defensible chain of evidence linking each consent record to the disclosure that was active at the time.

POST a new legal notice document and link it to subsequent consent events by referencing its returned identifier

AI Agent Consent Enforcement

An AI agent acting on behalf of a marketing system checks a subject's latest consent state before sending an email or processing personal data. Through Jentic the agent searches for 'check user consent', loads the GET /subjects/{id}/consent/last operation schema, and gates downstream actions on the returned preferences without ever touching the raw iubenda API key.

Search Jentic for 'check user consent', load the schema, execute against subject_id 'user-1234', and refuse the marketing send if consent.marketing is false

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for iubenda consent solution api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/consent

Record a consent event for a subject

GET

/consent/{id}

Retrieve a specific consent record

GET

/subjects/{id}/consent/last

Get the latest consent state for a subject

POST

/subjects

Create a subject profile

PATCH

/subjects/{id}

Partially update a subject record

GET

/legal_notices

List versioned legal notice documents

POST

/public/consent

Submit a consent event using a public API key

POST

/consent

Record a consent event for a subject

GET

/consent/{id}

Retrieve a specific consent record

GET

/subjects/{id}/consent/last

Get the latest consent state for a subject

POST

/subjects

Create a subject profile

PATCH

/subjects/{id}

Partially update a subject record

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

iubenda private and public API keys are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — the raw ApiKey header value is injected at request time and never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'record consent event' or 'check latest consent') and Jentic returns matching iubenda operations with their input schemas, so the agent can call the right endpoint without browsing iubenda documentation.

Time to first call

Direct iubenda integration: 1-3 days for auth setup, schema modelling, and audit log handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Mailchimp API

Email marketing platform that should respect iubenda consent state before sending campaigns

Use Mailchimp when an agent needs to send a campaign only after confirming the recipient's marketing consent through iubenda

Complementary

SendGrid Account Provisioning API

Transactional email infrastructure used downstream of consent verification

Pair SendGrid with iubenda when an agent must check consent state before triggering a transactional email

Complementary

Segment API

Customer data pipeline that can suppress events based on iubenda consent state

Use Segment alongside iubenda to gate analytics tracking on the user's recorded preferences

FAQs

Specific to using iubenda Consent Solution API API through Jentic.

Why is there no official OpenAPI spec for iubenda Consent Solution API?

iubenda does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call iubenda Consent Solution API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the iubenda Consent Solution API use?

The API uses an API key passed in the ApiKey header. There are two scopes: a private key for server-side calls and a public key restricted to /public/consent submissions from browsers. Through Jentic both keys are stored in the credential vault and never exposed to agents.

What are the rate limits for the iubenda Consent Solution API?

iubenda enforces 50 requests per second per private API key with a daily ceiling of 108,000 calls. Public keys are throttled separately at the banner integration level. Plan batched subject lookups to stay within the daily limit.

Can I retrieve a user's full consent history with this API?

Yes. Call GET /subjects/{id} for the profile and GET /subjects/{id}/consent/last for the most recent state, then page through GET /consent filtered by subject_id for the full historical record. This is the typical pattern for subject access requests.

How do I record a consent event through Jentic?

Search Jentic for 'record user consent', load the POST /consent operation schema, and execute with subject_id, legal_notice_id, and the preferences payload. Jentic handles the ApiKey header injection and returns the created record id.

Does the iubenda API store proof of disclosure documents?

Yes. Each consent event can reference a legal notice version, and you can attach proof documents that record the exact wording shown to the user. This produces a defensible audit trail linking the consent to the disclosure that was active at the time.