Clutch API

Name: Clutch API API
Brand: Clutch API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer10 EndpointsREST

For Agents

Run a loyalty or gift card programme on Clutch — create customers, issue cards, check balances, and record point or value transactions.

Quickstart

Get started with Clutch 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:
"check loyalty card balance"

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

Capabilities

What an agent can do with Clutch API API.

Create and update customer profiles tied to a loyalty or gift card programme

Search customers by attributes such as email or phone number

Issue new loyalty or gift cards and look up existing cards by ID

Retrieve a card's current balance and full transaction history

Record transactions that earn, redeem, or adjust card value or points

GET STARTED

Start building with Clutch API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Clutch API, keeping it validated and agent-ready. The Clutch API is the integration surface for the Clutch customer marketing platform's loyalty and gift-card programmes. It exposes operations to create and update customers, issue and look up loyalty or gift cards, retrieve a card balance and transaction history, and record point or value transactions against a card. Authentication uses an HTTP Bearer token, and the API is sized at 10 endpoints covering the core customer-card-transaction model.

Use Cases

Patterns agents use Clutch API API for, with concrete tasks.

★ Loyalty Points Earning From Point of Sale

Retailers running loyalty on Clutch wire their point-of-sale or e-commerce checkout to POST /v1/transactions whenever a customer makes a purchase. The transaction body references the customer's card and the amount or points earned, and Clutch updates the balance returned by GET /v1/cards/{cardId}/balance immediately. /v1/customers/search resolves the customer by email before the transaction is posted, removing the need for cashiers to look up loyalty IDs manually.

After a $48 purchase, search for the customer by email via POST /v1/customers/search, then POST /v1/transactions with cardId and the points earned for that purchase amount

Gift Card Issuance and Redemption

Brands running gift card programmes use POST /v1/cards to issue new gift cards in bulk for promotional drops or B2B sales, and customers redeem them via POST /v1/transactions at checkout. GET /v1/cards/{cardId}/balance returns the remaining value, and GET /v1/cards/{cardId}/transactions surfaces the redemption history for support agents handling balance enquiries. The flow runs entirely against the API, removing manual gift card issuance from the marketing team's queue.

Issue 100 gift cards each with $25 value via POST /v1/cards in a loop, then send the resulting card IDs to the marketing team for distribution

Customer Service Lookup During Support Calls

Support agents fielding 'what's my balance' and 'where did my points go' calls use the Clutch API to answer in seconds. /v1/customers/search resolves the customer by email or phone, GET /v1/cards/{cardId} returns the card details, GET /v1/cards/{cardId}/balance returns the current balance, and GET /v1/cards/{cardId}/transactions lists the transaction history. The 10-endpoint surface covers everything a tier-one support agent needs to resolve the call without a separate admin tool.

Search for the customer by email via /v1/customers/search, retrieve their card via /v1/cards/{cardId}, and return the balance plus the last 5 transactions to the support agent

AI Agent Running Loyalty Operations via Jentic

AI agents handling customer marketing or support can call Clutch through Jentic to issue cards, record transactions, and answer balance enquiries. The agent expresses an intent like 'check a customer's loyalty balance', and Jentic loads the matching Clutch operation, supplies the Bearer token from the vault, and returns the structured response. The same flow scales from individual support resolutions to bulk gift card drops without the agent reading apidocs.clutch.com.

Through Jentic, search for 'check loyalty card balance', load the clutch.com /v1/cards/{cardId}/balance operation, and execute it with the customer's cardId

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for clutch api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/customers

Create a customer

POST

/v1/customers/search

Search customers

POST

/v1/cards

Issue a card

GET

/v1/cards/{cardId}/balance

Get a card's balance

GET

/v1/cards/{cardId}/transactions

List transactions on a card

POST

/v1/transactions

Create a transaction

GET

/v1/transactions/{transactionId}

Get a transaction

POST

/v1/customers

Create a customer

POST

/v1/customers/search

Search customers

POST

/v1/cards

Issue a card

GET

/v1/cards/{cardId}/balance

Get a card's balance

GET

/v1/cards/{cardId}/transactions

List transactions on a card

POST

Why though Jentic?

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

Credential isolation

The Clutch API Bearer token is stored encrypted in the Jentic vault (MAXsystem) and applied to the Authorization header only at execution time. The agent never sees the raw token, and it is not written into prompt history.

Intent-based discovery

Agents search by intent (e.g. 'check loyalty card balance', 'issue a gift card', 'record a transaction') and Jentic returns the matching Clutch operation with its input schema, so the agent can call /v1/cards or /v1/transactions without browsing apidocs.clutch.com.

Time to first call

Direct Clutch integration: a day to wire customer-search, card issuance, and transaction recording into a checkout or support flow. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

LoyaltyLion API

LoyaltyLion is a directly comparable e-commerce loyalty platform with customers, points, and rewards endpoints

Choose LoyaltyLion for Shopify-centric loyalty programmes; choose Clutch when the brand also runs gift cards on the same customer record

Alternative

Yotpo API

Yotpo bundles loyalty, reviews, and SMS marketing in a single API platform

Choose Yotpo when the team also wants reviews and SMS in the same product; choose Clutch for a focused loyalty-and-gift-card surface

Complementary

Stripe API

Stripe handles the underlying card payment that earns or redeems Clutch loyalty points at checkout

Use Stripe to charge the customer, then call Clutch /v1/transactions with the resulting amount to award points or redeem a gift card

FAQs

Specific to using Clutch API API through Jentic.

Why is there no official OpenAPI spec for Clutch API?

Clutch does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clutch 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 Clutch API use?

The Clutch API uses an HTTP bearer scheme: an API token is sent in the Authorization header on every request. Through Jentic the token is stored encrypted in the vault and applied at execution time, so the agent never sees the raw token.

Can I issue a gift card through the Clutch API?

Yes. POST /v1/cards creates a new card tied to a customer (or to be assigned later) with the requested initial balance. The response returns the cardId, which is then used to look up the balance via GET /v1/cards/{cardId}/balance and to record redemption transactions.

How do I record a points-earning transaction at checkout?

Look up the customer with POST /v1/customers/search, retrieve their cardId, then POST /v1/transactions with the cardId and the points or value earned. The card's balance is updated immediately and is reflected in subsequent GET /v1/cards/{cardId}/balance calls.

What are the rate limits for the Clutch API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. Clutch applies plan-level limits documented in apidocs.clutch.com, and high-volume integrations should batch transactions per cart rather than per line item. Through Jentic, retries are handled by the SDK.

How do I check a customer's card balance through Jentic?

Install the SDK with pip install jentic, search for 'check loyalty card balance', load the clutch.com /v1/cards/{cardId}/balance operation, and execute it with the cardId. Jentic supplies the Bearer token automatically and returns the current balance.

Can I retrieve the transaction history for a card?

Yes. GET /v1/cards/{cardId}/transactions returns the list of point or value transactions against the card, which is the standard way to populate a customer's account history page or a support agent's lookup screen.