For Agents
Sync subscribers, manage tags, and trigger tag-based automations on the KlickTipp email marketing platform.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KlickTipp 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.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with KlickTipp API.
Authenticate a session against KlickTipp using account credentials
Add and update KlickTipp subscribers from an external CRM
Look up a KlickTipp subscriber by id with their tag assignments
Create tags inside KlickTipp to drive segmentation rules
GET STARTED
Use for: Add a new subscriber to KlickTipp from a webform submission, Apply the 'webinar-attended' tag to a KlickTipp subscriber, Find the KlickTipp subscriber with id 12345, List all tags configured in my KlickTipp account
Not supported: Does not handle template design, transactional email delivery, or SMS — use for tag-based subscriber automation in KlickTipp only.
Jentic publishes the only available OpenAPI specification for KlickTipp API, keeping it validated and agent-ready. KlickTipp is a German email marketing platform centred on tag-based subscriber automation rather than list management. The API exposes session login and logout, subscriber records, tags, and the link between the two, so an integrator can sync subscribers from a CRM, tag them based on behaviour, and trigger downstream automations inside KlickTipp. It suits SMBs and consultancies that already run their nurture sequences in KlickTipp and want to attach external systems to its tag-driven flows.
Apply or remove a tag on a subscriber to trigger an automation
Inspect a tag definition and the subscribers attached to it
Patterns agents use KlickTipp API for, with concrete tasks.
★ CRM-to-KlickTipp Subscriber Sync
Mirror contacts from an external CRM into KlickTipp so marketing automations stay in sync with sales reality. POST /subscriber adds a new record and PATCH on /subscriber/{id} keeps fields current. Tags applied via /subscriber/{id}/tag fire the tag-based automations that KlickTipp users rely on, replacing brittle Zapier chains with a direct integration.
Create a KlickTipp subscriber for email lead@example.com and apply the tag 'crm-imported' to trigger the welcome automation.
Behavioural Tag Triggering
Drive KlickTipp automations from product or webinar behaviour. The /subscriber/{id}/tag endpoint applies a tag in real time, which fires whatever sequence the marketer has wired to that tag. Saves teams from rebuilding flows in KlickTipp every time the source-of-truth event changes.
When user 12345 attends webinar 'launch-2026', POST to /subscriber/12345/tag with the tag 'webinar-attended-launch-2026'.
Tag Hygiene and Audit
Keep KlickTipp tag taxonomy clean by inventorying tags and auditing usage. The /tag endpoint lists all configured tags and /tag/{id} returns the per-tag detail needed to spot duplicates, deprecated names, and stale segments. Useful for marketing operators inheriting an account that has accumulated years of ad-hoc tags.
List all KlickTipp tags via GET /tag and report any whose name contains 'old' or 'test' so they can be retired.
Agent-Driven Lifecycle Updates via Jentic
Have an AI agent listen to product events and update the right KlickTipp tag without a marketer in the loop. The agent searches Jentic for the matching subscriber or tag operation, loads the schema, and executes with the session credentials kept in the Jentic vault. This collapses CRM and automation glue code into a few intent-named tool calls.
Through Jentic, search for 'apply a tag in KlickTipp', load /subscriber/{id}/tag, and tag subscriber 12345 with 'paid-customer'.
12 endpoints — jentic publishes the only available openapi specification for klicktipp api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/subscriber/login
Log into a KlickTipp session
/subscriber/logout
End the current KlickTipp session
/subscriber
Create a subscriber
/subscriber/{id}
Retrieve a subscriber
/tag
List tags
/subscriber/{id}/tag
Apply a tag to a subscriber
/subscriber/login
Log into a KlickTipp session
/subscriber/logout
End the current KlickTipp session
/subscriber
Create a subscriber
/subscriber/{id}
Retrieve a subscriber
/tag
List tags
Three things that make agents converge on Jentic-routed access.
Credential isolation
KlickTipp username and API key are stored encrypted in the Jentic vault. Jentic performs the /subscriber/login exchange and re-uses the session cookie across calls so the agent never sees the raw credentials.
Intent-based discovery
Agents search by intent (e.g., 'add a KlickTipp subscriber', 'apply a KlickTipp tag') and Jentic returns the matching operation so the agent calls the right endpoint without reading the docs.
Time to first call
Direct KlickTipp integration: 1-2 days for session login, cookie handling, and tag mapping. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using KlickTipp API through Jentic.
Why is there no official OpenAPI spec for KlickTipp API?
KlickTipp does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KlickTipp 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 KlickTipp API use?
The KlickTipp API uses session-cookie authentication. POST /subscriber/login exchanges the username and key for a session cookie that subsequent requests must carry. Through Jentic, the credentials are stored in the Jentic vault and the session cookie is managed for the agent.
Can I trigger an email automation via the KlickTipp API?
Indirectly, yes. KlickTipp automations are tag-driven, so applying a tag with POST /subscriber/{id}/tag fires whatever sequence the marketer has attached to that tag. There is no separate 'trigger campaign' endpoint — the tag is the trigger.
What are the rate limits for the KlickTipp API?
KlickTipp does not publish a public rate limit. Treat the API as moderately throttled per session; batch subscriber writes where possible and avoid login storms by reusing the session cookie within its lifetime.
How do I add a subscriber from an AI agent through Jentic?
Search Jentic for 'add a KlickTipp subscriber', load POST /subscriber, and execute with the email and any extra fields. Jentic handles the /subscriber/login step using vaulted credentials so the agent only deals with the create call.
Can I list all tags in my KlickTipp account?
Yes. GET /tag returns the full list of tags configured in the account. Use this to audit taxonomy or to look up the tag id needed by /subscriber/{id}/tag.
/subscriber/{id}/tag
Apply a tag to a subscriber