Climbo API
Browse all Climbo APIsAgent-ready OpenAPI document · curated by JenticMarketingMarketing AutomationapiKey32 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage reviews, campaigns, templates, locations, and contacts on Climbo's review management platform, plus agency-level client and plan management. 32 endpoints with x-api-key auth.
Use for: Send a review-request campaign to a list of contacts, Reply to a customer review on behalf of a Climbo client, List all reviews collected this month for a location, Create a new template for review-request messages
Not supported: Does not handle payment processing, social media posting, or SEO ranking - use for Climbo review collection, campaign sending, and agency client management only.
Jentic publishes the only available OpenAPI specification for Climbo API, keeping it validated and agent-ready. Climbo 2.0 is a white-label review management platform for agencies and their clients. The API exposes 32 endpoints across two operating modes: Agency Mode (manage downstream client accounts, plans, billing, webhooks) and Clients Mode (run reviews, templates, campaigns, contacts, feedback, and locations for a single business). Authentication uses a static x-api-key header, and the full surface is well suited to building review collection workflows, automating campaign sends, and replying to reviews at scale.
Install Jentic One Beta
Connect the Climbo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Climbo 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclimbo.com%2Fclimbo" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclimbo.com%2Fclimbo" | 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.
Capabilities
What an agent can do with Climbo API.
Send review-request campaigns to contacts and track their delivery
Reply to incoming reviews and monitor feedback received from customers
Manage business locations and the templates used for review-request messages
Provision and manage agency client accounts, billing plans, and account status
Subscribe to webhooks for review and feedback events to drive downstream automations
Pull billing details for the agency's own business account
Track contacts and the campaigns they have been included in
Use Cases
Patterns agents use Climbo API for, with concrete tasks.
★ Automated Review Request Campaigns
Local businesses need consistent review collection without remembering to ask each customer. POST /campaigns/send triggers a review-request campaign to a contact list using a chosen template, and GET /reviews tracks incoming responses. Agencies running this on behalf of clients can schedule it from their own systems and let Climbo handle delivery and tracking.
GET /templates to pick a template, then POST /campaigns/send with the template_id and the contact list to trigger review-request delivery
Review Reply at Scale
Brands managing many locations need to reply quickly to incoming reviews. GET /reviews returns recent reviews across the connected locations, and POST /reviews/reply submits a response. Combined with a webhook subscription on review events, an agency can route incoming reviews to the right reviewer and post the reply through one API call.
Subscribe a webhook for new review events, then for each review POST /reviews/reply with the review_id and the reviewer's response text
Location and Template Setup for New Clients
When an agency onboards a new client, the client's locations and review-request templates need to be configured before campaigns can run. POST /locations registers each business location, GET /templates and POST /templates manage the message library, and the standard agency endpoints provision the client account itself. The full setup is a deterministic sequence of API calls.
POST /client to create the client, POST /locations for each business location, then POST /templates for each review-request template the client will use
Agent-Driven Review Operations
An AI agent embedded in an agency operations console uses Jentic to surface and reply to reviews across many client accounts. Jentic search returns Climbo's reviews and reply endpoints with their schemas, the agent loads them, executes with the right x-api-key, and reports back which reviews were handled and which still need human attention.
Use Jentic to search for list reviews and reply, load the schemas for GET /reviews and POST /reviews/reply, and process the queue for a given client
Key Endpoints
32 endpoints — jentic publishes the only available openapi specification for climbo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/reviews
List collected reviews
POST
/reviews/reply
Reply to a review
POST
/campaigns/send
Send a review-request campaign
GET
/templates
List review-request templates
POST
/locations
Create a business location
POST
/client
Create an agency client account
POST
/webhook/subscribe
Subscribe to platform event webhooks
GET
/business/billing
Retrieve agency billing details
GET
/reviews
List collected reviews
POST
/reviews/reply
Reply to a review
POST
/campaigns/send
Send a review-request campaign
GET
/templates
List review-request templates
POST
/locations
Create a business location
POST
/client
Create an agency client account
POST
/webhook/subscribe
Subscribe to platform event webhooks
GET
/business/billing
Retrieve agency billing details
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Climbo by hand means managing its x-api-key header, mapping the review, campaign, and client endpoints yourself, and handling your own retries against api.climbo.com. Through Jentic you install once, import Climbo from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Climbo's write targets like a review reply or a campaign send travel in the request body rather than the URL path, so scope the agent to the operations it needs, such as fetching reviews or sending a review-request campaign. You choose which operations are in that set, so client creation or webhook subscription are not included unless you add them.
Credential isolation
Your Climbo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a review request campaign' or 'reply to a review', and Jentic returns the matching Climbo operation with its input schema, including template_id and contact list structure, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Climbo API (agency-only)
Smaller agency-focused slice of the same platform; covers client/plan/webhook only
Choose the agency-only slug when the agent only needs client provisioning, not reviews or campaigns
FAQs
Specific to using Climbo API through Jentic.
Why is there no official OpenAPI spec for Climbo API?
Climbo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Climbo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Climbo API use?
Climbo uses an x-api-key header. Send your API key on every call to /reviews, /campaigns, /templates, /locations, and the agency endpoints. Through Jentic the key is held encrypted in your Jentic One instance and injected at execution time.
Can I send review-request campaigns through this API?
Yes. POST /campaigns/send triggers a review-request campaign using a chosen template against a contact list. Use GET /templates first to pick the template_id and GET /campaigns to track delivery and engagement after sending.
What are the rate limits for the Climbo API?
The OpenAPI spec does not publish numeric rate limits. Apply exponential backoff on 429 or 5xx responses. For high-volume sends, contact Climbo to confirm plan-specific limits before scheduling large campaigns.
How do I reply to a customer review through Jentic?
Run pip install jentic, search Jentic for reply to climbo review, load the schema for POST /reviews/reply, and execute with the review_id and your response text. Jentic injects the x-api-key from the vault. Get started with Jentic One, the self-hosted execution layer.
Does Climbo support both agency and client modes through this API?
Yes. Agency Mode endpoints (/client, /clients, /plan, /plans, /webhook) manage downstream accounts; Clients Mode endpoints (/reviews, /campaigns, /templates, /locations, /feedbacks, /contacts) operate within a single business. The same x-api-key is used; the platform routes based on the key's permissions.
Can I limit what my agent is allowed to do with the Climbo API?
Yes. Because you run Jentic One yourself, your own rules decide which Climbo operations and credentials the agent can use. You can scope it to just the operations it needs, such as GET /reviews to fetch reviews or POST /campaigns/send to send a review-request campaign, while leaving out higher-impact operations like POST /client for client creation or POST /webhook/subscribe. Since Climbo's write targets travel in the request body rather than the URL path, those operations stay out of the agent's reach unless you explicitly add them to the allowed set.
GET STARTED