iubenda Consent Solution API
Agent-ready OpenAPI document · curated by JenticIdentity AuthAuthorizationapiKey17 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Record and retrieve user consent events, manage subject profiles, and attach legal notices to a consent database that satisfies GDPR audit requirements.
Use for: I need to record a user's cookie consent for GDPR compliance, Retrieve the latest consent state for a given subject ID, List all consent events recorded in the last 30 days, Find all subjects who consented to marketing emails
Not supported: Does not handle cookie banner rendering, privacy policy generation, or DSAR workflow UI - use for consent recording and retrieval only.
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.
Install Jentic One Beta
Connect the iubenda Consent Solution API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iubenda Consent Solution API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fiubenda.com%2Fiubenda" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fiubenda.com%2Fiubenda" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with iubenda Consent Solution 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
Attach versioned legal notice documents to consent events for proof of disclosure
Submit public consent events from frontend applications using a scoped public API key
Use Cases
Patterns agents use iubenda Consent Solution 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
GET
/legal_notices
List versioned legal notice documents
POST
/public/consent
Submit a consent event using a public API key
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the iubenda Consent Solution API by hand means managing its ApiKey header, splitting private and public key auth, and choosing the right host yourself. Through Jentic you install once, import iubenda from the API Directory, store the key once, and your agent calls it.
Permission scoping
iubenda takes the consent record in the request body when writing, so scope by operation: limit the agent to the operations it needs, such as recording a consent event or reading a subject's latest consent, and leave subject updates out unless you add them. You pick the allowed set, so it stays inside consent recording and retrieval.
Credential isolation
Your iubenda API key is stored once, encrypted, by your own Jentic One instance and injected at request time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'record a consent event' or 'check the latest consent', and Jentic returns the matching iubenda operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using iubenda Consent Solution 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the iubenda Consent Solution API?
Yes. Jentic One is self-hosted, so you decide which of the API's operations the agent may call and which credentials it uses, and you scope by operation because iubenda takes the consent record in the request body when writing. For example, you can allow only recording a consent event and reading a subject's latest consent, and leave subject updates out unless you explicitly add them. You pick the allowed set.
GET STARTED