Custify API
Official vendor OpenAPI document · agent-readyCRMCustomer Successbearer63 EndpointsREST
For Agents
Manage people and companies, record product events, track customer health scores and lifecycles, capture NPS and CSAT feedback, and handle tickets, tasks, and financial records across 63 endpoints. Authenticates with a bearer token.
Use for: Create or update a company record in Custify, Record a product usage event for a person, List the health scores for our customers, Assign an NPS score to a person after a survey
Not supported: Does not send marketing campaigns, host a knowledge base, or process payments. Use for customer success data, health scoring, feedback, and account management only.
The Custify API is the RESTful interface to the Custify customer success platform. Across 63 endpoints it manages people and company records, records product events, tracks health scores, lifecycles, and customer objectives, captures NPS and CSAT feedback and survey responses, and handles tickets, tasks, notes, financial deals, invoices, subscriptions, and time tracking.
Install Jentic One Beta
Connect the Custify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Custify 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%2Fcustify.com%2Fcustify" | 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%2Fcustify.com%2Fcustify" | 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 Custify API.
Create, update, list, and delete people and company records
Record product usage events against a person or company
Track customer health scores, lifecycles, and objectives
Assign NPS and CSAT scores and read survey responses
Manage support tickets, tasks, notes, and time tracking
Record financial deals, invoices, and subscriptions
Use Cases
Patterns agents use Custify API for, with concrete tasks.
★ Agent-Driven Customer Health Monitoring
An AI agent connected through Jentic can keep customer success data current without manual entry. It records product usage events, reads the resulting health scores and lifecycle stage, and creates a follow-up task when an account looks at risk, so a success team acts on signals rather than chasing spreadsheets.
Read the health scores for a set of companies and create a follow-up task for any account whose score has dropped below a threshold
Feedback Collection and Scoring
Success teams track sentiment through NPS and CSAT. The Custify API assigns NPS and CSAT scores to people and lists survey responses, so an agent can record a rating captured elsewhere and pull the responses into a report or a downstream workflow.
Assign an NPS score to a person after they answer a survey and then list the latest survey responses
Account and Contact Sync
Keeping Custify aligned with other systems means writing people and company records as they change. The Custify API creates or updates people and companies and links custom data to them, letting an agent push a new signup or an updated account from a CRM into Custify automatically.
Create or update a company and its people in Custify from a record that changed in the CRM
Key Endpoints
63 endpoints — the custify api is the restful interface to the custify customer success platform.
METHOD
PATH
DESCRIPTION
POST
/people
Create or update a person
POST
/company
Create or update a company
POST
/event
Insert product usage events
GET
/health_score
List customer health scores
POST
/nps_score/{entity}
Assign an NPS score to a person
POST
/people
Create or update a person
POST
/company
Create or update a company
POST
/event
Insert product usage events
GET
/health_score
List customer health scores
POST
/nps_score/{entity}
Assign an NPS score to a person
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Custify by hand means managing a bearer token, learning the JSON API request shapes across 63 endpoints, and finding your data-centre-specific API URL. Through Jentic you install once, import Custify from the API Directory, store the token once, and your agent calls the operations directly.
Permission scoping
Many operations address a person, company, ticket, or other record by its ID in the URL path, so a rule can bound your agent to specific records as well as to specific operations. You might allow reading health scores and creating tasks while blocking company and people deletion.
Credential isolation
Your Custify bearer token 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 'create or update a company in Custify', and Jentic returns the matching operation with its input schema so the agent calls it with the right fields.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Custify API through Jentic.
What authentication does the Custify API use?
The Custify API authenticates every request with a bearer token in the Authorization header, using the API key from your Custify developer settings, per its OpenAPI spec. Through Jentic the token is stored once by your own self-hosted instance and injected when the agent calls, so it never appears in the agent's prompt or logs.
Is there a Custify MCP server?
You don't need an MCP server to give your agent the Custify API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the people, company, health score, and ticket operations. Operations are discovered on demand, so nothing extra loads into the agent's context.
Can I limit what my agent is allowed to do with the Custify API?
Yes. Many operations address a person, company, ticket, or other record by its ID in the URL path, so a rule can bound the agent to specific records as well as to specific operations. You might allow reading health scores and creating tasks while blocking company and people deletion, with every call logged.
Can the Custify API record product usage events?
Yes. The event operation inserts product usage events against a person or company, and the batch operation submits many requests at once, so an agent can feed usage signals into Custify to keep health scores and lifecycles current.
What are the rate limits for the Custify API?
The OpenAPI spec does not specify rate limits. Check the Custify documentation at https://docs.custify.com for current limits and batch guidance before running high-volume imports.
How do I update a company through Jentic?
Search Jentic by intent, for example 'create or update a company in Custify', and Jentic returns the matching operation with its input schema. Your agent supplies the company fields and reads back the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED