canonical: https://jentic.com/apis/betool.fr/betool

# Betool Fr CRM Golden Gate API

The CRM Golden Gate API is the REST entrypoint of the Betool CRM, where an agent lists and reads the companies in an organization, creates a company, and partially updates one by id. It also reads process datatables, returning both their rows and their column structure, and retrieves a single process record by its register token. Create and update calls run asynchronously and return an operation id whose progress the agent polls until the write settles.

## For AI agents

Work with Betool CRM data: list, read, create, and update company records, and read process datatables and records. Writes are asynchronous and return a pollable operation id.

## Scope

Does not handle marketing campaigns, deal pipelines, or support ticketing. Use for CRM company and process-record management only.

## Capabilities

- List the companies in an organization's Betool CRM
- Create a company record in the CRM
- Partially update selected fields on a company by id
- Read a process datatable's rows together with its column structure
- Retrieve a single process record by its register token
- Poll the progress of an asynchronous create or update operation

## Use cases

### Agent-maintained company records

An AI agent keeps CRM company records current. Through Jentic the agent lists companies, reads one by id, and submits a partial update; because writes are asynchronous, the update returns an operation id that the agent polls through the operations endpoint until the change settles. This lets an assistant correct a company's details without a human opening the CRM.

Example prompt: List companies, find the one named 'Acme', and submit a partial update setting its website, then poll the returned operation id until it completes

### Process datatable reporting

A team runs reporting off a Betool process datatable. The API returns both the datatable's rows and its column structure, and a schema-only call describes the columns without fetching rows, so an agent can map fields before pulling data. This supports building a report or sync without hard-coding the datatable layout.

Example prompt: Fetch a process datatable's schema to learn its columns, then retrieve its rows for the current reporting period

### Record lookup by register token

A support assistant resolves a single process record on demand. Given a register token, the API returns that one process record, so an agent handling an inbound request can pull the exact record it refers to without scanning the whole datatable. The lookup is read-only and scoped to one record.

Example prompt: Retrieve the process record for a given register token and return its fields to the support assistant

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/companies` | List the companies of the organization |
| POST | `/companies` | Create a company |
| GET | `/companies/{id}` | Retrieve one company |
| POST | `/companies/{id}` | Partially update a company |
| GET | `/process/{id}/datatable` | Retrieve datatable data and structure for a process |
| GET | `/process/{id}/records/{registerToken}` | Retrieve a single process record |
| GET | `/operations/{operationId}` | Read the progress of an async create/update operation |

## Key resources

- **Companies** — List, read, create, and partially update company records
- **Process datatables** — Read datatable rows and column structure, or the structure alone
- **Records** — Retrieve a single process record by its register token
- **Operations** — Poll the progress of asynchronous create and update operations

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 61 / 100
  - Developer Experience & Jentic Compatibility: 73 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 78 / 100
- **View full report:** https://jentic.com/apis/betool.fr/betool/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 CRM Golden Gate API by hand means handling its bearer-token auth, learning the async write pattern where create and update return an operation id you poll, and parsing process datatable structures yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The CRM Golden Gate API puts the company id in the URL path (`/companies/{id}`), so a rule can pin your agent to the company operations it needs: it can list and read companies and update one by id without reaching the process datatable endpoints. You choose the operations it may call, so create and update are not included unless you add them.
- **Credential handling:** Your Betool organization token is held 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 'list CRM companies' or 'update a company record', and Jentic returns the matching CRM Golden Gate operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot CRM Contacts** — A larger CRM with contact, company, and deal objects
- **Salesforce** — Enterprise CRM for accounts, contacts, and opportunities
- **Attio** — A flexible, data-model-driven CRM

## FAQ

### What authentication does the CRM Golden Gate API use?

The CRM Golden Gate API authenticates with a bearer token per its OpenAPI spec: an organization API token passed in the Authorization header as a bearer credential. Through Jentic the token is injected at call time by your own Jentic One instance, so it never enters the agent's prompt or logs.

### Can I update a company record with the CRM Golden Gate API?

Yes. The company update operation partially updates a company by its id, so you send only the fields that change. Because writes run asynchronously, the call returns an operation id whose progress you read back through the operations endpoint until the update settles.

### What are the rate limits for the CRM Golden Gate API?

The OpenAPI spec does not specify rate limits. Check the provider's documentation at https://betool.fr for current limits before running high-volume syncs.

### Is there a CRM Golden Gate MCP server?

You don't need an MCP server to give your agent the CRM Golden Gate API. Jentic connects it directly from the API Directory: import it, store your organization token once, and your agent calls it, so you skip installing and syncing a separate server.

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

Yes. Write a rule that allows only the company list and read operations, so the agent can look up companies but cannot create or update one, and add the update operation only when you want it to write. Every call the agent makes is logged.

### How do I update a company with the CRM Golden Gate API through Jentic?

Search Jentic for 'update a CRM company' and it returns the company update operation with its input schema; because writes are asynchronous, the call hands back an operation id you read through the operations endpoint. To run it on your own infrastructure, install Jentic One from its GitHub repo.