canonical: https://jentic.com/apis/salesup.com/salesup

# Salesup Upnify API

Upnify (SalesUp) CRM API. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically create contact, list contacts. Covers 12 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Create contact
- List contacts
- Get contact
- Update contact
- Monitor Upnify API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Contacts** — Operations for contacts
- **Deals** — Operations for deals
- **Pipelines** — Operations for pipelines
- **Tasks** — Operations for tasks
- **Users** — Operations for users

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 75 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/salesup.com/salesup/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### 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.