For Agents
Run loyalty program actions — enrol customers, post point transactions, redeem rewards, and trigger campaigns — through a single dispatch endpoint at /api.php.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loyalty Gator API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Loyalty Gator API API.
Dispatch loyalty program operations through a single POST /api.php endpoint
Authenticate every call with the api_access_key header for tenant isolation
Submit request_type form fields to route between customer, transaction, and reward operations
Pair with the clienttoolbox.com main spec for the full operation catalogue
GET STARTED
Use for: Send a loyalty program request through the Loyalty Gator dispatch endpoint, Authenticate a Loyalty Gator call with the api_access_key header, Find which request_type values are supported for customer operations, List the form parameters required for a Loyalty Gator request
Not supported: Does not handle payment processing, ticketing, or full CRM workflows — use for loyalty program dispatch operations only.
Jentic publishes the only available OpenAPI document for Loyalty Gator API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Loyalty Gator API, keeping it validated and agent-ready. Loyalty Gator is a customer loyalty program platform from Client Toolbox, exposing a single dispatch endpoint that accepts a request_type form field to drive operations on customers, transactions, rewards, and campaigns. Authentication uses an api_access_key header. This index entry covers the dispatch endpoint; the full request_type catalogue is documented in the clienttoolbox.com main API spec.
Build a thin agent shim that maps natural language onto request_type values
Patterns agents use Loyalty Gator API API for, with concrete tasks.
★ Single-Endpoint Loyalty Dispatch
Developers integrating loyalty into a checkout flow can call POST /api.php with the appropriate request_type form field — for example a customer lookup or a points award — and receive a JSON response. Because every operation runs through one endpoint, network and auth handling can be shared across all loyalty interactions. The trade-off is that the agent must select the right request_type for the action.
POST to /api.php with api_access_key header set and form fields request_type=customer_info plus customer_id=12345 to fetch a customer record.
Index Spec for Catalogue Browsing
Catalogue and discovery tools that need a stable handle for the Loyalty Gator product can use this index spec to surface a single tile, then deep-link to the full request_type catalogue in the clienttoolbox.com main spec. This keeps marketplace listings clean while preserving the rich operation set for agents that need it.
Show the Loyalty Gator tile on the catalogue, and on click route to the clienttoolbox.com/main entry for the full per-request_type operation list.
AI Agent Loyalty Action via Jentic
Agent builders can register Loyalty Gator through Jentic and call /api.php with a request_type chosen at run time. Jentic stores the api_access_key server-side, so the agent receives a scoped token rather than the raw key, and the agent can compose the form body from a natural-language instruction. For full per-action operations, agents typically use the clienttoolbox.com/main spec instead.
Search Jentic for 'execute a loyalty gator request', load the POST /api.php schema, and execute with request_type and the form fields supplied by the user.
1 endpoints — jentic publishes the only available openapi specification for loyalty gator api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/api.php
Execute a Loyalty Gator API request, with the operation selected by the request_type form field
/api.php
Execute a Loyalty Gator API request, with the operation selected by the request_type form field
Three things that make agents converge on Jentic-routed access.
Credential isolation
Loyalty Gator api_access_key headers are stored encrypted in the Jentic vault. Agents receive a scoped execution token — the raw key never enters the agent's prompt or memory.
Intent-based discovery
Agents search Jentic by intent (for example, 'execute a loyalty gator request') and Jentic returns the POST /api.php operation with its form-field schema, so the agent fills request_type and the operation parameters together.
Time to first call
Direct Loyalty Gator integration: half a day to model form-encoded calls and the request_type switch. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Loyalty Gator API
Same product, modelled with one path per request_type for fine-grained agent operations.
Use the main spec when the agent needs distinct operations per action (customer, transaction, reward); use this index spec for a stable single-endpoint handle.
LoyaltyLion API
Loyalty platform focused on Shopify and e-commerce stores.
Choose LoyaltyLion when the storefront is on Shopify and ecommerce-native flows matter; choose Loyalty Gator for broader retail and POS integrations.
Yotpo API
Reviews, loyalty, and SMS platform for e-commerce brands.
Choose Yotpo when reviews and SMS marketing are bundled with loyalty; choose Loyalty Gator for a focused loyalty-only platform.
Specific to using Loyalty Gator API API through Jentic.
Why is there no official OpenAPI spec for Loyalty Gator API?
Client Toolbox does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Loyalty Gator 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 Loyalty Gator API use?
Every request to /api.php must include the api_access_key header. Through Jentic, the key is stored in the vault and never enters the agent's context — the agent receives a scoped execution token instead.
How does the single /api.php endpoint route between operations?
Operations are selected by the request_type form field on POST /api.php (for example customer_info, transaction_add, reward_redeem). For the full catalogue of request_type values, use the clienttoolbox.com/main spec, which models each request_type as a distinct path.
Can I post a loyalty transaction with the Loyalty Gator API?
Yes. POST /api.php with request_type set to a transaction operation and the customer and points fields in the form body. The detailed transaction request_type catalogue lives in the clienttoolbox.com/main spec.
What are the rate limits for the Loyalty Gator API?
Client Toolbox does not publish explicit rate limits in the spec. SSL is mandatory and limits are enforced per account. Handle 429 responses with backoff and check current quotas with Client Toolbox support for your tier.
How do I call Loyalty Gator through Jentic?
Run pip install jentic, then search for 'execute a loyalty gator request', load the POST /api.php schema, and execute with request_type plus the form fields for that operation. Jentic builds the form body and adds the api_access_key header.