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

# Salesflare API

Introduction Getting Started The Salesflare API allows you to access and build your own applications or integrations that interact with Salesflare. The Salesflare API provides a RESTful interface with JSON-formatted responses to access most Salesflare resources. Authentication The Salesflare API uses bearer token based authentication, which means you need to use the key-value pair "Authorization :. The API exposes 67 endpoints.

## For AI agents

Programmatically create an account, list accounts. Covers 67 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Create an account
- List accounts
- Get current user's details
- Query and filter Salesflare API records by parameters
- Monitor Salesflare API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Salesflare API to perform identity auth operations programmatically. The API provides 67 endpoints covering core functionality including create an account, list accounts, create a contact.

Example prompt: Call POST /accounts to create an account

### Automated Accounts Management

Automate accounts operations by combining multiple Salesflare API endpoints. Agents can list accounts and then create a contact in a single workflow.

Example prompt: Call GET /accounts to list accounts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Salesflare 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/accounts` | Create an account |
| GET | `/accounts` | List accounts |
| POST | `/contacts` | Create a contact |
| GET | `/contacts` | List contacts |
| GET | `/currencies` | List supported currencies |
| GET | `/groups` | List groups |
| GET | `/me` | Get current user's details |
| POST | `/opportunities` | Create an opportunity |

## Key resources

- **Accounts** — Operations related to Accounts
- **Custom Fields** — Operations related to Custom Fields
- **Tags** — Operations related to Tags
- **Workflows** — Operations related to Workflows
- **Contacts** — Operations related to Contacts

## Why Jentic

- **Setup:** Wiring the Salesflare API by hand means reading its reference to find the right account, contact, and opportunity endpoints against api.salesflare.com and handling paging and retries yourself. Through Jentic you install once, import Salesflare from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Salesflare puts the record id in the URL path (`/accounts/{id}`, `/contacts/{id}`), 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 accounts or contacts are not included unless you add them.
- **Credential handling:** Your Salesflare 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 'create an account' or 'list contacts', and Jentic returns the matching Salesflare operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Salesflare API use?

The Salesflare API uses no authentication. 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 an account with the Salesflare API?

Yes. Use the POST /accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Salesflare 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 an account through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an account'. Jentic returns the matching Salesflare API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Salesflare API have?

The Salesflare API exposes 67 endpoints covering accounts, custom fields, tags operations.

### Can I limit what my agent is allowed to do with the Salesflare API?

Yes. Because you run Jentic One yourself, your own rules decide which Salesflare operations and credentials the agent may use. Salesflare puts the record id in the URL path, such as `/accounts/{id}` and `/contacts/{id}`, so you can pin the agent to specific accounts or contacts and let it read or update only those. You also choose the operations it may call, so writes like POST /accounts or POST /contacts stay off unless you add them.