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

# Forcemanager Sage Sales Management Public API Documentation for Developers

The Sage Sales Management API tracks the sales pipeline of a field sales team, so an application can move opportunities through their stages while keeping accounts, contacts, and activities in sync. You list and update opportunities with their types and statuses, manage the accounts and contacts they belong to, and log the calls, events, and activities reps record in the field. Supporting resources cover orders, products and rates, campaigns, documents, and webhooks, and each entity exposes a schema endpoint so an integration can discover its fields before writing.

## For AI agents

Move sales opportunities through their stages, manage accounts, contacts, and activities, and record orders and calls in Sage Sales Management. Authenticates with a session key in the X-Session-Key header.

## Scope

Does not process payments, run marketing email sends, or handle support ticketing. Use for sales pipeline, account, and activity management only.

## Capabilities

- List and update sales opportunities with their types and statuses
- Manage the accounts an opportunity belongs to, including segments and statuses
- Keep contacts and their account relationships up to date
- Log field activities, calls, and events recorded by reps
- Create and track orders with their statuses and line products
- Discover an entity's fields through its schema endpoint before writing

## Use cases

### Agent-Driven Pipeline Updates

An AI agent connected through Jentic keeps the pipeline current by creating opportunities, moving them to the right status, and logging the activities behind each change, so a sales manager sees an accurate board without reps updating the CRM by hand. Because each entity exposes a schema endpoint, the agent reads the available fields before writing so its updates fit the account's configuration.

Example prompt: Create an opportunity for this account, set its status to the next pipeline stage, and log a call activity against it

### Account and Contact Sync

An integration keeps accounts and contacts aligned with another system by listing accounts, updating their segments and statuses, and attaching the right contacts, so sales data stays consistent across tools. Sage Sales Management models account segments and statuses as their own resources, so the integration can reclassify an account without touching its contacts.

Example prompt: List accounts in a segment, update each one's status, and link any missing contacts to them

### Field Activity Logging

A mobile workflow records what reps do in the field by creating call, event, and activity records against the right accounts and opportunities, so managers can measure visit frequency and follow-up. Activities carry types and points, so the workflow can tag each entry for reporting without a separate system.

Example prompt: Log a visit activity for a rep against an account and tag it with the correct activity type

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/opportunities` | List sales opportunities |
| POST | `/opportunities` | Create an opportunity |
| PUT | `/opportunities/{ID}` | Update an opportunity |
| GET | `/accounts` | List accounts |
| POST | `/accounts` | Create an account |
| GET | `/contacts` | List contacts |
| POST | `/activities` | Create a field activity |

## Key resources

- **Opportunities** — Sales opportunities with types and statuses that model the pipeline
- **Accounts** — Customer accounts with segments, statuses, and addresses
- **Contacts** — People linked to accounts, with their types and relationships
- **Activities** — Calls, events, and activities reps log in the field, with types and points

## 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:** 46 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 35 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 39 / 100
  - Agent Usability: 43 / 100
  - Security: 50 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/forcemanager.com/forcemanager/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 Sage Sales Management API by hand means logging in to obtain an X-Session-Key, learning each entity's schema before you write, and choosing between the production and sandbox hosts. Through Jentic you install once, import Sage Sales Management from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow reading and updating opportunities and activities while leaving destructive ones like deleting an account out. Rules bound which operations run, so the agent works the pipeline you grant and nothing else.
- **Credential handling:** Your Sage Sales Management session 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 'update a sales opportunity' or 'log a field activity', and Jentic returns the matching Sage Sales Management operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Pipedrive API** — Sales CRM focused on deal pipelines and activity tracking
- **Close CRM API** — Inside-sales CRM with built-in calling, email, and pipeline management
- **Salesloft API** — Sales engagement platform for cadences, calls, and buyer activity

## FAQ

### Is there a Sage Sales Management MCP server?

You don't need an MCP server to give your agent the Sage Sales Management API. Jentic connects it directly from the API Directory: import it, store your session key once, and your agent can update opportunities, accounts, and activities straight away, with no extra server to run and no tool definitions sitting in the agent's context.

### Can I limit what my agent is allowed to do with the Sage Sales Management API?

Yes. Write a rule that allows only the operations the agent needs, such as listing and updating opportunities and logging activities, and leave deletions out. Every call the agent makes is logged, so you can see exactly which accounts and deals it changed.

### What authentication does the Sage Sales Management API use?

The Sage Sales Management API authenticates with a session key sent in the X-Session-Key header per its OpenAPI spec, obtained from the login operation. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

### Can I manage the sales pipeline with the Sage Sales Management API?

Yes. Opportunities are a first-class resource with their own types and statuses, so an agent can create an opportunity, move it between stages, and read the opportunities schema to see the available fields. Accounts, contacts, and activities link to each opportunity so the whole deal context stays together.

### What are the rate limits for the Sage Sales Management API?

The OpenAPI spec does not state request rate limits for the Sage Sales Management API. For current limits and fair-use guidance, check the provider documentation at https://developer.forcemanager.com.

### How do I update an opportunity through Jentic?

Import the Sage Sales Management API from the Jentic API Directory, then have your agent issue a request such as 'move this opportunity to the next stage'. Jentic matches the intent to the update-opportunity operation and returns its input schema so the agent builds the correct request, with your stored session key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.