Antavo Loyalty Engine API

Name: Antavo Loyalty Engine API API
Brand: Antavo Loyalty Engine API
Availability: InStock

★ Only Publicly Available SpecMarketingMarketing AutomationapiKey, bearer18 EndpointsREST

For Agents

Drive loyalty programs by posting earn/spend events, claiming rewards, and reading customer point balances and transaction history through Antavo's events and customers endpoints.

Quickstart

Get started with Antavo Loyalty Engine 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:
"award loyalty points for a purchase"

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

Capabilities

What an agent can do with Antavo Loyalty Engine API API.

Post point-earning events (purchases, signups, referrals) to a customer's loyalty profile

Spend points or claim catalogue rewards on behalf of a loyalty member

Bulk-ingest historical events to seed or backfill loyalty data via the events/bulk endpoint

Merge two loyalty customer profiles when a duplicate is detected

GET STARTED

Start building with Antavo Loyalty Engine API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Antavo Loyalty Engine API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Antavo Loyalty Engine API, keeping it validated and agent-ready. Antavo is a loyalty-program engine that exposes 18 REST endpoints covering customer profiles, point-earning and point-spending activities, reward claiming, custom-event ingestion, and entity records that drive program rules. The API is structured around the events and customers resources so agents can post earn/spend activities, retrieve a customer's transaction history, and trigger reward claims directly from a CRM or e-commerce flow. Authentication supports both an api_key query parameter and HTTP bearer tokens.

Use Cases

Patterns agents use Antavo Loyalty Engine API API for, with concrete tasks.

★ E-Commerce Earn-on-Purchase Hook

Wire a checkout webhook to call POST /events with the order amount, customer ID, and an 'earn' event type so points are awarded the moment a purchase completes. Antavo applies the program's tier rules and multipliers server-side, so the storefront does not need to encode loyalty math. Bulk historical seeding is supported via POST /events/bulk for migrations from another platform.

Call POST /events with type 'earn', the customer ID, and the order subtotal, then verify the response confirms the point award

Reward Redemption Flow

Let a customer redeem a reward in-app by calling POST /customers/{customerId}/activities/rewards/{rewardId}/claim with the desired reward ID. Antavo verifies the customer has enough points, applies the spend, and returns the claim status. Pair with POST /customers/{customerId}/activities/spend for ad-hoc point deductions outside the catalogue.

Call POST /customers/{customerId}/activities/rewards/{rewardId}/claim and surface the returned claim status to the user

Customer Profile and History Lookup

Display a member's point balance, tier, and recent activity by calling GET /customers/{customerId} and GET /customers/{customerId}/transactions. The agent uses these to render the loyalty section of an account page or to answer support questions like 'why did I only get 5 points on this order?' without screen-scraping the Antavo dashboard.

Call GET /customers/{customerId} for the member's profile, then GET /customers/{customerId}/transactions to list their last 10 point movements

AI Agent Loyalty Operations via Jentic

An AI agent embedded in a CRM or chat support flow can drive Antavo loyalty actions through Jentic without managing the api_key or bearer token directly. Jentic's intent search routes to POST /events or the customer activities endpoints with their input schema, and the credential is loaded from the vault at execution time so it never enters the agent's prompt context.

Search Jentic for 'award loyalty points for a purchase', load POST /events, and execute with the customer ID and purchase amount supplied by the support workflow

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for antavo loyalty engine api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/events

Post a single earn or spend event

POST

/events/bulk

Bulk-ingest historical events

GET

/customers

List customers in the loyalty program

GET

/customers/{customerId}

Retrieve a customer profile and balance

POST

/customers/{customerId}/merge

Merge two duplicate customer profiles

POST

/customers/{customerId}/activities/earn

Award points for a custom earn activity

POST

/customers/{customerId}/activities/spend

Deduct points for a custom spend activity

POST

/customers/{customerId}/activities/rewards/{rewardId}/claim

Claim a catalogue reward for a customer

POST

/events

Post a single earn or spend event

POST

/events/bulk

Bulk-ingest historical events

GET

/customers

List customers in the loyalty program

GET

/customers/{customerId}

Retrieve a customer profile and balance

POST

/customers/{customerId}/merge

Merge two duplicate customer profiles

Why though Jentic?

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

Credential isolation

Antavo api_key query parameters and bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access only — credentials are injected at execution time so the raw key never enters the agent's prompt or tool context, which matters because the key authorises point-issuance.

Intent-based discovery

Agents search by intent (e.g., 'award loyalty points for a purchase') and Jentic returns POST /events with its earn-event schema, so the agent does not need to study Antavo's event-type taxonomy from the docs.

Time to first call

Direct Antavo integration: 1-2 days for auth, event-type mapping, and reward-claim flow. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

LoyaltyLion API

LoyaltyLion offers an e-commerce loyalty engine with similar earn/spend primitives.

Choose LoyaltyLion when the agent works in a Shopify-first stack and needs out-of-the-box widget integrations.

Alternative

Yotpo Developer API

Yotpo includes loyalty and referrals alongside reviews and SMS in a single platform.

Choose Yotpo when the agent needs reviews, SMS marketing, and loyalty under one vendor rather than a loyalty-only engine.

Complementary

HubSpot CRM API

HubSpot stores the customer records that feed Antavo earn/spend events.

Choose HubSpot when the agent needs to look up the source customer record before posting events to Antavo.

FAQs

Specific to using Antavo Loyalty Engine API API through Jentic.

Why is there no official OpenAPI spec for Antavo Loyalty Engine API?

Antavo publishes its docs at developers.antavo.com but does not ship a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Antavo 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 Antavo Loyalty Engine API use?

Antavo accepts either an api_key query parameter or an HTTP bearer token. Through Jentic both credential types are stored in the encrypted vault and injected at execution time, so the raw key or token never enters the agent's prompt context.

Can I bulk-load historical events into Antavo?

Yes. POST /events/bulk accepts an array of historical earn or spend events for backfill or migration from another loyalty platform. Single-event traffic uses POST /events instead.

What are the rate limits for the Antavo Loyalty Engine API?

The OpenAPI spec does not declare explicit rate limits. Antavo enforces per-tenant throughput on the live service — confirm the limit for your plan and use POST /events/bulk for backfills rather than rapid-fire single-event calls.

How do I award loyalty points after a purchase with Antavo through Jentic?

Run pip install jentic, then search Jentic for 'award loyalty points for a purchase'. Jentic returns POST /events with its earn-event schema. Execute with the customer ID and order subtotal, and Antavo applies the program's tier and multiplier rules server-side.

Does Antavo support customer profile merging?

Yes. POST /customers/{customerId}/merge merges two loyalty profiles when a duplicate is detected, consolidating point balance, tier, and transaction history under a single record.