canonical: https://jentic.com/apis/bergsystem.pl/bergsystem

# Bergsystem Pl Berg CRM API

The Berg CRM API manages customers, sales, and sales opportunities for the Berg System platform. It lists and creates customers and companies, moves sales opportunities through selling-process steps and checklists, and records payments, installments, and paychecks against sales. Supporting operations cover products, calendar events, employees and their goals, and GDPR records, all behind an OAuth 2.0 authorization.

## For AI agents

Manage a sales pipeline in Berg CRM: create customers and companies, open and progress sales opportunities through selling-process steps, record payments, and schedule calendar events.

## Scope

Does not handle email marketing, telephony, or e-commerce checkout. Use for managing customers, sales, and sales opportunities in Berg CRM only.

## Capabilities

- List and create customers and companies
- Create and update sales and sales opportunities
- Progress a sales opportunity through its selling-process steps and checklist
- Record payments, installments, and paychecks against sales
- Create products and product categories and producers
- Create and update calendar events and employee goals

## Use cases

### AI Agent CRM Updates

An AI agent keeps Berg CRM current without a developer building a sync integration. Through Jentic the agent creates customers, opens sales opportunities, and records payments against sales, while the OAuth credentials stay on the developer's own machine.

Example prompt: Create a customer, open a sales opportunity linked to that customer, and advance it to the next selling-process step

### Sales Pipeline Progression

Sales teams move each opportunity through defined stages. Berg CRM exposes selling processes with ordered steps and a checklist per opportunity, so an agent can read where an opportunity stands, check off a requirement, and advance it.

Example prompt: Read the steps of a selling process for an opportunity, mark a checklist question answered, and update the opportunity

### Payment Recording

Closed sales need payments logged against them. Berg CRM lets an agent record payments and installments on a sale and read what has been paid, so finance stays in sync with the pipeline.

Example prompt: Record a payment against a sale and list that sale's payments to confirm the balance

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/customers` | Get customers list |
| POST | `/customers` | Create a customer |
| GET | `/sales` | Get all sales |
| POST | `/sales` | Create a sale |
| GET | `/sales_opportunities` | Get all sales opportunities |
| POST | `/sales_opportunities` | Create a sales opportunity |
| GET | `/selling_processes` | Get selling processes list |
| GET | `/payments` | Get all payments |

## Key resources

- **Customers** — List, create, and update customers and their companies
- **Sales** — Create and update sales and read their products and commissions
- **Sales Opportunities** — Open, update, and progress opportunities through selling-process steps and checklists
- **Payments** — Record payments, installments, and paychecks against sales
- **Products** — Create products, categories, and producers
- **Events** — Create, update, and delete calendar events and event types

## 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:** 38 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 39 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 23 / 100
  - Agent Usability: 79 / 100
  - Security: 30 / 100
  - AI Discoverability: 40 / 100
- **View full report:** https://jentic.com/apis/bergsystem.pl/bergsystem/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 Berg CRM by hand means implementing its OAuth 2.0 token exchange, learning its selling-process step model, and matching payments to sales yourself. Through Jentic you install once, import Berg CRM from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Access runs through one OAuth client, so a rule bounds the agent to the operations it needs, such as reading customers and creating sales. You choose which operations it may call, so deleting events or files is not included unless you add them.
- **Credential handling:** Your Berg CRM OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a sales opportunity' or 'record a payment', and Jentic returns the matching Berg CRM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot Deals** — HubSpot Deals tracks opportunities through pipeline stages across a large CRM.
- **Pipedrive** — Pipedrive focuses on visual sales-pipeline tracking for deals and people.
- **Salesforce** — Salesforce manages customer records across an enterprise CRM data model.

## FAQ

### Is there a Berg CRM MCP server?

You don't need an MCP server to give your agent the Berg CRM API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so nothing extra loads into the agent's context.

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

Yes. Write a rule that allows only the customer-read and sale-create operations, so the agent can look up customers and log new sales but cannot delete events or files, and every call is logged.

### What authentication does the Berg CRM API use?

The Berg CRM API authenticates with OAuth 2.0, obtaining an access token from its token endpoint using the password or authorization-code flow declared in its OpenAPI spec. Through Jentic the credentials are stored encrypted by your own Jentic One instance and exchanged for a token at call time, so they never reach the agent's prompt or logs.

### Can I progress a sales opportunity through its pipeline with the Berg CRM API?

Yes. Read the selling process and its ordered steps for an opportunity, mark a checklist question answered, and update the opportunity, so the agent advances it through the pipeline the same way a sales rep would.

### How do I create a sales opportunity through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Berg CRM API from the Jentic API Directory and store your OAuth credentials. Your agent searches for 'create a sales opportunity' and Jentic returns the create operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### What are the rate limits for the Berg CRM API?

The Berg CRM OpenAPI spec does not define rate limits. Berg System documents operational detail in its knowledge base, so confirm the current limits there before high-volume syncing.