canonical: https://jentic.com/apis/abtasty.com/abtasty # AB Tasty Integration API Jentic publishes the only available OpenAPI specification for AB Tasty Integration API, keeping it validated and agent-ready. The AB Tasty Integration API exposes campaigns, variations, goals, and reports for AB Tasty's experimentation platform, covering A/B testing, feature flags, and personalization at integration-api.abtasty.com. Eleven endpoints support full CRUD on campaigns and variations, listing and creating goals, and pulling per-campaign and per-variation conversion reports. Authentication is a single API key passed in a header, making it straightforward to wire into deployment pipelines, marketing tools, or AI-driven experimentation workflows. ## For AI agents Programmatically create and manage A/B test campaigns, variations, goals, and conversion reports across the AB Tasty experimentation platform via 11 REST endpoints. ## Scope Does not handle visitor data collection, web analytics tracking, or session replay - use for managing AB Tasty experiment campaigns, goals, and reports only. ## Capabilities - Launch a new A/B test campaign with one or more variations from a deployment script - Create or update a conversion goal and attach it to a running campaign - Pull conversion-rate and uplift metrics for a campaign or specific variation - Pause or delete an underperforming campaign without logging into the dashboard - List active campaigns to feed dashboards or feature-flag-style rollouts ## Use cases ### CI-driven experiment launch When a developer merges a feature flag, the deployment pipeline calls POST /campaigns and POST /campaigns/{campaignId}/variations to create a matching A/B test in AB Tasty without anyone clicking through the dashboard. This couples experiment creation to code releases and removes a manual handoff between engineering and growth. Example prompt: POST /campaigns to create a campaign named 'checkout-cta-test', then POST /campaigns/{campaignId}/variations twice to create control and treatment variations ### Slack-bot experiment summary A nightly job calls GET /reports/campaigns/{campaignId} for each running campaign and posts a Slack summary with conversion rate, uplift, and statistical significance. Saves the growth team from logging into the AB Tasty dashboard every morning. Example prompt: For each campaignId in the watchlist, call GET /reports/campaigns/{campaignId} and post conversion_rate, uplift, and significance to #experiments ### Goal lifecycle management When a product squad ships a new feature, an internal tool calls POST /goals to create a tracking goal and then attaches it to the relevant campaign. Removes the duplicated step of creating goals manually in the AB Tasty UI. Example prompt: POST /goals with name='checkout_completed' and type='click', then GET /goals to verify the new goal is listed ### AI agent experimentation workflow An agent tasked with running growth experiments uses Jentic to discover the AB Tasty operations on demand, creates campaigns and variations, then loops on the conversion-report endpoint until significance is reached. Through Jentic the agent never sees the API key directly. Example prompt: Search Jentic for 'launch an ab test', load POST /campaigns, execute with treatment variations, then poll GET /reports/campaigns/{campaignId} every hour ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /campaigns | Create a new A/B test campaign | | GET | /campaigns | List campaigns | | POST | /campaigns/{campaignId}/variations | Create a variation under a campaign | | GET | /reports/campaigns/{campaignId} | Get campaign-level conversion report | | GET | /reports/variations/{variationId} | Get variation-level conversion report | | POST | /goals | Create a conversion goal | ## Key resources - **Campaigns** — Create, list, update, and delete A/B test campaigns via /campaigns and /campaigns/{campaignId} - **Variations** — List and create variations under a campaign via /campaigns/{campaignId}/variations - **Goals** — List and create conversion goals via /goals - **Reports** — Pull campaign and variation conversion reports via /reports/campaigns/{campaignId} and /reports/variations/{variationId} ## Why Jentic - **Setup:** Wiring the AB Tasty Integration API by hand means holding its X-API-Key header on every request and tracking campaign and variation ids across calls yourself. Through Jentic you install once, import the AB Tasty Integration API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** AB Tasty puts the campaign id in the URL path (/campaigns/{campaignId}/...), so a rule can pin your agent to one campaign: it can add variations and read that campaign's report and nothing else. You choose the operations it may call, so creating new campaigns or goals is not included unless you add it. - **Credential handling:** Your AB Tasty API key is stored once, encrypted, by your own Jentic One instance and injected as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'launch an ab test' or 'get a conversion report', and Jentic returns the matching AB Tasty operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Optimizely** — Experimentation and feature flagging with deeper enterprise tooling - **LaunchDarkly** — Feature flag platform optimised for engineering rollouts - **Split** — Feature flag and experimentation platform with metric-driven rollouts ## FAQ ### Why is there no official OpenAPI spec for AB Tasty Integration API? AB Tasty publishes Swagger HTML at integration-api.abtasty.com/swagger but does not distribute a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AB Tasty Integration 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 AB Tasty Integration API use? An API key passed via the ApiKeyAuth header on every request. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the agent never sees the raw value. ### Can I create A/B test campaigns programmatically with this API? Yes. POST /campaigns creates a campaign and POST /campaigns/{campaignId}/variations adds variations. You can also update with PUT /campaigns/{campaignId} or remove via DELETE /campaigns/{campaignId}. ### What are the rate limits for the AB Tasty Integration API? AB Tasty publishes per-account rate limits in their dashboard rather than the spec; defaults are typically 60 requests per minute per token. If you need higher throughput for backfill jobs, batch reads of /campaigns and /goals together to stay under the limit. ### How do I pull a conversion report through Jentic? Search Jentic for 'get ab test conversion report', load GET /reports/campaigns/{campaignId}, and execute with the campaign id. Install with pip install jentic and use await client.search, load, execute. ### Can I list goals attached to my AB Tasty account? Yes. GET /goals returns every conversion goal on the account, including the goal type and the campaigns it is attached to. Use it to audit the goal catalogue before creating duplicates. ### Can I limit what my agent is allowed to do with the AB Tasty Integration API? Yes. Because you run Jentic One yourself, your own rules decide which AB Tasty operations and credentials the agent may use. Since the campaign id sits in the URL path (/campaigns/{campaignId}/variations and /reports/campaigns/{campaignId}), you can pin the agent to a single campaign so it only adds variations and reads that campaign's conversion report. Broader operations like creating new campaigns with POST /campaigns or creating goals with POST /goals stay off limits unless you explicitly grant them.