Salesup Upnify API
✓ Official Vendor SpecCRMDeal Pipelinebearer12 EndpointsREST
For Agents
Programmatically create contact, list contacts. Covers 12 operations with bearer authentication.
Use for: I need to contact, I want to contacts, Search for contact, Find all contact
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Upnify (SalesUp) CRM API. The API exposes 12 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Upnify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Upnify 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%2Fsalesup.com%2Fsalesup" | 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%2Fsalesup.com%2Fsalesup" | 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 Upnify API.
Create contact
List contacts
Get contact
Update contact
Monitor Upnify API operational status and events
Use Cases
Patterns agents use Upnify API for, with concrete tasks.
★ CRM Operations
Use the Upnify API to perform crm operations programmatically. The API provides 12 endpoints covering core functionality including create contact, list contacts, get contact.
Call POST /contacts to create contact
Automated Contacts Management
Automate contacts operations by combining multiple Upnify API endpoints. Agents can list contacts and then get contact in a single workflow.
Call GET /contacts to list contacts, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Upnify API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create contact', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
12 endpoints — upnify (salesup) crm api.
METHOD
PATH
DESCRIPTION
POST
/contacts
Create contact
GET
/contacts
List contacts
GET
/contacts/{contactId}
Get contact
PUT
/contacts/{contactId}
Update contact
POST
/deals
Create deal
GET
/deals
List deals
GET
/deals/{dealId}
Get deal
PUT
/deals/{dealId}
Update deal
POST
/contacts
Create contact
GET
/contacts
List contacts
GET
/contacts/{contactId}
Get contact
PUT
/contacts/{contactId}
Update contact
POST
/deals
Create deal
GET
/deals
List deals
GET
/deals/{dealId}
Get deal
PUT
/deals/{dealId}
Update deal
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Upnify API by hand means learning its bearer auth, reading the reference to map its contact and deal endpoints against api.salesup.com, and handling retries yourself. Through Jentic you install once, import Upnify from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
Upnify puts the record id in the URL path (/contacts/{contactId}, /deals/{dealId}), so a rule can pin your agent to specific records: it can read or update the ones you allow and nothing else. You choose the operations it may call, so writes like creating contacts or deals are not included unless you add them.
Credential isolation
Your Upnify 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 a contact' or 'get a deal', and Jentic returns the matching Upnify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Upnify API through Jentic.
What authentication does the Upnify API use?
The Upnify API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create contact with the Upnify API?
Yes. Use the POST /contacts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Upnify API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create contact through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create contact'. Jentic returns the matching Upnify API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Upnify API have?
The Upnify API exposes 12 endpoints covering contacts, deals, pipelines operations.
Can I limit what my agent is allowed to do with the Upnify API?
Yes. Because you self-host Jentic One, your own rules decide which Upnify operations and credentials the agent may use. Upnify puts the record id in the URL path, so you can pin the agent to specific contacts or deals it may read or update and nothing else. You also choose the operations it may call, so writes such as creating contacts (POST /contacts) or deals (POST /deals) are not available to it unless you add them.
GET STARTED