canonical: https://jentic.com/apis/kiflo.com/kiflo # Kiflo PRM API Jentic publishes the only available OpenAPI specification for Kiflo PRM API, keeping it validated and agent-ready. Kiflo is a partner relationship management platform whose API exposes partners, deals, leads, customers, payouts, certifications, and supporting metadata. The 88-endpoint surface covers contact and customer records, deal and lead lifecycle, channel conflicts, partner certifications, attachments, and email templates, all secured with an API key in the Authorization header. Use it to keep a partner program in sync with a CRM, billing system, or onboarding workflow. ## For AI agents Manage partners, deals, leads, customers, payouts, and certifications inside a Kiflo PRM workspace from an automation or agent. ## Scope Does not handle direct-sales pipelines, marketing automation, or invoicing - use for partner-sourced deals, leads, and certifications inside a PRM workspace only. ## Capabilities - Create deals and update them as they move through the partner pipeline - Register and update leads passed in from partners - Maintain customer records linked to partner-sourced revenue - Issue and revoke partner team-member certifications - Track channel conflicts when two partners claim the same opportunity - Attach files to records by uploading from disk or from a URL - List and patch contact properties used in custom fields ## Use cases ### Partner-sourced deal sync When a partner submits a new opportunity through a portal or form, an integration can call POST /deals to register it in Kiflo and PATCH `/contacts/{id}` to update the linked partner contact. The deal then flows through the channel team's pipeline with the partner attribution preserved end to end. Example prompt: POST a deal to /deals with partner_id, account name, and value, then PATCH the related contact with the latest details. ### Lead distribution workflow Inbound leads from a website or paid campaign can be routed to the right partner by reading the relevant lead, customer, and partner records through Kiflo and writing back the assigned partner. The API exposes both the lead and customer collections needed to build the full attribution view. Example prompt: List leads, choose the partner with the lowest current load using the partner list, and assign the lead to that partner. ### Partner certification tracking Enablement teams can grant or revoke partner team-member certifications by calling POST /partner-contact-certifications, then list the certifications a partner currently holds with GET /partner-contact-certifications. This keeps the partner portal accurate without a manual update step. Example prompt: POST a certification award for the partner contact who completed training, then verify it appears in the contact's certification list. ### Channel conflict resolution When two partners both claim an opportunity, an automation can record the dispute via POST /channel-conflicts so the channel team has a single record to triage. The endpoint captures both parties and the contested deal in one structured object. Example prompt: POST a channel conflict to /channel-conflicts referencing both partner IDs and the disputed deal. ### Agent integration via Jentic A revenue operations agent can use Jentic to discover the Kiflo deal and lead operations, load their schemas, and execute them with vaulted credentials. The agent runs end-to-end partner workflows without holding the raw API key. Example prompt: Search Jentic for 'create a deal in Kiflo', load POST /deals, and execute it with the partner-supplied opportunity details. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/deals` | Create a partner-sourced deal | | POST | `/contacts` | Create a contact | | PATCH | `/contacts/{id}` | Update a contact | | GET | `/customers` | List customers | | POST | `/customers` | Create a customer | | POST | `/partner-contact-certifications` | Award a certification | | POST | `/channel-conflicts` | Log a channel conflict | | POST | `/attachments/upload` | Upload an attachment from file | ## Key resources - **Deals** — Create and update partner-sourced sales opportunities - **Leads** — Capture and route inbound leads passed in by partners - **Customers** — Manage customer records linked to partner revenue - **Contacts** — Read, create, and patch contact records and custom properties - **Certifications** — Award and list partner team-member certifications - **Channel Conflicts** — Record disputes when partners overlap on an opportunity - **Attachments** — Upload files to partner records from disk or URL ## Why Jentic - **Setup:** Wiring Kiflo PRM by hand means learning its Authorization-header API key, handling the api.kiflo.com/v3 host, and mapping its many partner endpoints yourself. Through Jentic you install once, import Kiflo PRM from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Most Kiflo writes carry the deal, contact, or customer in the request body rather than pinning a resource in the URL path, so scope by operation: limit the agent to the operations it needs, such as creating deals or contacts, and leave certifications or channel-conflict writes out unless you add them. - **Credential handling:** Your Kiflo 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. - **Discovery method:** Agents search Jentic by intent such as 'register a partner-sourced deal' or 'add a partner contact', and Jentic returns the matching Kiflo operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Salesforce API** — Salesforce holds the master account and opportunity record while Kiflo manages the partner relationship - **HubSpot Account API** — HubSpot CRM tracks contacts and deals at the company-wide level alongside a Kiflo partner program - **Pipedrive API** — Pipedrive runs the internal sales pipeline that closes deals registered through Kiflo - **Close CRM API** — Close handles direct sales pipelines but does not include Kiflo's partner program features ## FAQ ### Why is there no official OpenAPI spec for Kiflo PRM API? Kiflo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kiflo PRM 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 Kiflo PRM API use? Kiflo authenticates with an API key sent in the Authorization header. Jentic keeps that key in its vault and injects it on each call, so the agent process never reads the raw value. ### Can I create partner-sourced deals with the Kiflo PRM API? Yes. POST to /deals with the partner ID, account name, and deal value. The same surface lets you list, patch, and search deals through the dedicated /deals endpoints. ### What are the rate limits for the Kiflo PRM API? The OpenAPI specification does not declare explicit rate limits. Treat list endpoints like /deals and /customers as paginated reads, request only the pages needed, and back off if a 429 response is returned. ### How do I award a partner certification with the Kiflo PRM API through Jentic? Run pip install jentic, search Jentic for 'give a certification to a partner team member', load the POST /partner-contact-certifications operation, and execute it with the partner contact ID and certification ID. Jentic supplies the Authorization header from the vault. ### Can I limit what my agent is allowed to do with the Kiflo PRM API? Yes. Because you run Jentic One yourself, your own rules decide which Kiflo operations and credentials the agent may use. Since most Kiflo writes carry the deal, contact, or customer in the request body rather than in the URL path, you scope by operation: grant only the operations the agent needs, such as creating deals or contacts, and leave certification awards and channel-conflict writes out unless you explicitly add them.