AB Tasty Integration API

Name: AB Tasty Integration API API
Brand: AB Tasty Integration API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct AnalyticsapiKey11 EndpointsREST

For Agents

Programmatically create and manage A/B test campaigns, variations, goals, and conversion reports across the AB Tasty experimentation platform via 11 REST endpoints.

Quickstart

Get started with AB Tasty Integration 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:
"launch an A/B test campaign"

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

Capabilities

What an agent can do with AB Tasty Integration API API.

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

GET STARTED

Start building with AB Tasty Integration API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AB Tasty Integration API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use AB Tasty Integration API API for, with concrete tasks.

★ 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.

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.

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.

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.

Search Jentic for 'launch an ab test', load POST /campaigns, execute with treatment variations, then poll GET /reports/campaigns/{campaignId} every hour

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for ab tasty integration api, keeping it validated and agent-ready.

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

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

Why though Jentic?

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

Credential isolation

The AB Tasty API key is stored encrypted in the Jentic vault and injected as the ApiKeyAuth header at execution time. Agents receive scoped access tokens — raw API keys never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'launch an ab test', 'get conversion report') and Jentic returns the matching AB Tasty operation with its input schema, so the agent can call /campaigns or /reports without browsing docs.

Time to first call

Direct integration: 1-2 days for auth, error handling, and pagination across campaigns/goals/reports. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Optimizely

Experimentation and feature flagging with deeper enterprise tooling

Choose Optimizely when you need feature flag rollouts, multivariate testing, and deeper analytics integrations than AB Tasty's surface offers.

Complementary

LaunchDarkly

Feature flag platform optimised for engineering rollouts

Use LaunchDarkly for code-level feature flags and rollouts and AB Tasty for marketing-side A/B tests; the two often complement rather than replace each other.

Alternative

Split

Feature flag and experimentation platform with metric-driven rollouts

Choose Split when experimentation must be tied to engineering-defined metrics and you want statistical analysis baked into the rollout flow.

FAQs

Specific to using AB Tasty Integration API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.