Cruise Control API

Name: Cruise Control API API
Brand: Cruise Control API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer25 EndpointsREST

For Agents

Manage customer contacts, trigger review-request broadcasts, and configure event-driven messaging rules for the Cruise Control review collection platform.

Quickstart

Get started with Cruise Control 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:
"send a customer review request"

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

Capabilities

What an agent can do with Cruise Control API API.

Authenticate against Cruise Control with email and password to obtain a bearer token

Add and search customer contacts by email or phone number

Execute trigger broadcasts that send review requests over SMS or email

Inspect call and message logs by phone number or UUID

GET STARTED

Start building with Cruise Control API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Cruise Control API, keeping it validated and agent-ready. Cruise Control automates customer review collection by sending feedback requests via SMS or email after e-commerce or invoicing events. The API exposes 25 endpoints covering contact management, trigger broadcasts, message and call records, event-type catalogs, and rule presets that decide which customers receive review prompts. Authentication uses bearer tokens issued by the /auth/login endpoint.

Use Cases

Patterns agents use Cruise Control API API for, with concrete tasks.

★ Automated Post-Purchase Review Requests

Send review-request SMS or email automatically when an e-commerce order ships by firing trigger broadcasts against contacts created via the /contacts endpoint. Cruise Control routes the message and tracks delivery in the calls and messages logs.

Create a contact for customer jane@example.com with phone +14155550101, then call POST /trigger-execution with the order_completed trigger and verify a message appears in GET /messages.

Rule-Based Review Targeting

Use rule presets to filter which customers receive review prompts based on event payload values such as order total, region, or product category. Rules can be authored manually or generated from natural-language instructions via the AI rule generator.

Call POST /event-types/order_completed/rules/generate with the instruction 'only request reviews for orders over $50 from US customers' and dry-run it against a sample payload.

Event Catalog Mapping

Standardise incoming event payloads from multiple e-commerce or invoicing platforms by defining field aliases that map vendor-specific keys (e.g. customer_email, buyer_phone) to the Cruise Control catalog so rules and triggers work consistently across sources.

POST a field alias to /event-types/order_completed/catalog/aliases mapping 'buyer_email' to the canonical 'email' field, then GET the catalog to confirm.

Agent-Driven Review Operations

Allow an AI agent to manage the entire review-collection lifecycle through Jentic: add contacts, fire trigger broadcasts, inspect logs, and adjust rules without the developer hard-coding the Cruise Control endpoint paths or storing the bearer token in agent memory.

Search Jentic for 'send a customer review request', load the trigger-execution operation schema, and execute it with the customer's phone number and order ID.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/auth/login

Obtain a bearer access token

POST

/contacts

Add customer contacts

GET

/contacts/search

Search contacts by email or phone

POST

/trigger-execution

Execute a trigger broadcast

GET

/messages

List sent messages

POST

/event-types/{eventType}/rules

Create or update a rule preset

POST

/event-types/{eventType}/rules/generate

Generate a rule from natural language

POST

/auth/login

Obtain a bearer access token

POST

/contacts

Add customer contacts

GET

/contacts/search

Search contacts by email or phone

POST

/trigger-execution

Execute a trigger broadcast

GET

/messages

List sent messages

POST

Why though Jentic?

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

Credential isolation

Cruise Control bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution rights and never see the raw token returned by /auth/login.

Intent-based discovery

Agents search Jentic by intent (e.g. 'send a customer review request') and Jentic returns the matching trigger-execution operation along with its input schema, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct integration: 1-2 days to wire login, token refresh, trigger lookup, and error handling. Through Jentic: under an hour using search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Crunchbase API

Enrich customer contact records with company firmographics before targeting review requests.

Choose Crunchbase when the agent needs to qualify a contact's company size or funding before sending a review prompt; Cruise Control handles the messaging itself.

Complementary

Crustdata API

Pull company and people data to enrich Cruise Control contacts.

Use Crustdata to enrich contact metadata that informs Cruise Control rule presets; Cruise Control still owns the outreach channel.

Alternative

Crush The Memory API

Another niche customer-engagement API in the same vendor neighbourhood.

Consider when the use case is broader memory or engagement workflows rather than review collection specifically.

FAQs

Specific to using Cruise Control API API through Jentic.

Why is there no official OpenAPI spec for Cruise Control API?

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

The API uses HTTP bearer token authentication. Tokens are issued by POST /auth/login in exchange for email and password credentials and revoked via GET /auth/logout. Through Jentic, the bearer token is stored encrypted in the vault and never enters the agent's prompt context.

Can I trigger SMS review requests with the Cruise Control API?

Yes. POST /trigger-execution fires a configured trigger broadcast that delivers the review request via SMS or email depending on the contact's channel preference. Use GET /triggers first to list which triggers are available in your account.

How do I generate a targeting rule with AI through the Cruise Control API?

Call POST /event-types/{eventType}/rules/generate with a natural-language instruction (for example, 'only request reviews from US customers spending over $50'). The endpoint returns a structured rule that you can dry-run via /rules/dry-run before saving.

What are the rate limits for the Cruise Control API?

The OpenAPI specification does not document numeric rate limits. Inspect the response headers on live calls for any X-RateLimit values, and contact Cruise Control support for production quotas before bulk-sending review requests.

How do I send a review request through Jentic?

Install the SDK with pip install jentic, then search for 'send a customer review request', load the returned trigger-execution operation, and execute it with your contact identifier and trigger name. Jentic handles auth and schema lookup so the agent only supplies business inputs.