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.

Can I limit what my agent is allowed to do with the Clutch API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which Clutch operations and credentials your agent may use. You can allow read-only calls like GET /v1/cards/{cardId}/balance and GET /v1/cards/{cardId}/transactions while withholding value-minting operations such as POST /v1/cards and POST /v1/transactions unless you explicitly add them. Since the card id sits in the URL path (/v1/cards/{cardId}/...), a rule can also pin the agent to a single card for balance and transaction reads.