Climbo API

Name: Climbo API API
Brand: Climbo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey32 EndpointsREST

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.

Quickstart

Get started with Climbo 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 review request campaign on climbo"

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

Capabilities

What an agent can do with Climbo API 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

GET STARTED

Start building with Climbo API API

Explore with Jentic

View OpenAPI Document

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

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.

Use Cases

Patterns agents use Climbo API 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

Why though Jentic?

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

Credential isolation

The Climbo x-api-key is stored encrypted in the Jentic MAXsystem vault and injected at execution time. The agent never sees the raw key, only a scoped execution context.

Intent-based discovery

Agents search by intent (for example send review request campaign) and Jentic returns POST /campaigns/send with its request schema, including template_id and contact list structure, so the agent calls it correctly first time.

Time to first call

Direct integration: 1-2 days to wire x-api-key auth and walk through 32 endpoints across two modes. Through Jentic: under an hour from search to first review reply or campaign send.

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

Complementary

ClinchPad

Sales pipeline tracking that pairs with review management for agencies

Use ClinchPad to track sales deals and Climbo to provision and run review collection on the won deal

Alternative

Clip

Different domain (payments); included as catalog neighbor only

Not a real alternative for review management; agents should not select this for review or campaign work

FAQs

Specific to using Climbo API 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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up.

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.