canonical: https://jentic.com/apis/b24platform.ru/main

# B24platform Ru 1C–Bitrix24 Exchange API

The 1C-Bitrix24 Exchange API moves accounting data between a 1C installation and Bitrix24, exporting ASUP objects in full or as incremental changes and pushing payer counterparties across. It also registers and updates customer invoices in Bitrix24 directly from 1C billing documents, so the two systems stay reconciled without manual re-entry. The surface is small and sync-focused: object export, counterparty transfer, and invoice write.

## For AI agents

Export full or incremental ASUP objects from 1C, push payer counterparty records, and create or update Bitrix24 invoices from 1C billing data.

## Scope

Does not handle 1C licensing, Bitrix24 deal pipelines, or payment settlement. Use for exchanging ASUP objects, payer counterparties, and invoices between 1C and Bitrix24 only.

## Capabilities

- Export the full set of ASUP objects from 1C for loading into Bitrix24
- Pull only the ASUP objects that changed since the last run for an incremental sync
- Push payer counterparty records from 1C into Bitrix24
- Register and update customer invoices in Bitrix24 from 1C billing documents

## Use cases

### Agent-driven 1C to Bitrix24 sync

An AI agent keeps Bitrix24 aligned with a 1C back office by exporting ASUP objects and pushing counterparty and invoice updates on a schedule. Because the API separates a full export from an incremental changes feed, the agent can run a heavy full load occasionally and lightweight change pulls in between, registering new invoices in Bitrix24 as 1C emits them.

Example prompt: Call the ASUP updates operation, then for each changed payer document register or update the matching invoice in Bitrix24

### Initial full object load

A new Bitrix24 workspace needs the complete set of ASUP objects from 1C before day-to-day sync begins. The full-export operation returns the entire object set in one pass so the target can be seeded, after which the incremental feed takes over. This is the one-time backfill that makes later change-only pulls meaningful.

Example prompt: Call the full ASUP export operation once to seed Bitrix24, then switch to the incremental updates operation for ongoing sync

### Counterparty and invoice reconciliation

Finance teams need payer counterparties and their invoices to match between 1C and Bitrix24. The API pushes counterparty records and registers or updates invoices from 1C source documents, so a discrepancy found in Bitrix24 can be corrected from the authoritative 1C data rather than edited by hand in two places.

Example prompt: Push the counterparty record for a payer company, then register the matching invoice in Bitrix24 from the 1C billing document

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/exchange1c/asup/full` | Export the full set of ASUP objects |
| GET | `/exchange1c/asup/updates` | Export only changed ASUP objects |
| POST | `/exchange1c/company` | Push payer counterparty records |
| POST | `/exchange1c/bill` | Create and update invoices in Bitrix24 from 1C |

## Key resources

- **ASUP objects** — Full export and incremental change feeds of ASUP objects from 1C
- **Counterparties** — Payer company records transferred from 1C into Bitrix24
- **Invoices** — Customer invoices registered and updated in Bitrix24 from 1C billing documents

## 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:** 60 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 38 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 94 / 100
- **View full report:** https://jentic.com/apis/b24platform.ru/main/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 1C-Bitrix24 Exchange API by hand means managing its X-Auth key header and the split between full and incremental ASUP export flows yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The operations carry their targets in the request body, so a rule bounds which operations your agent may call, such as the ASUP export reads, rather than naming a single record. You choose the operations it may call, so the invoice write is not included unless you add it.
- **Credential handling:** Your X-Auth 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 'sync ASUP objects to Bitrix24', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Segment** — Segment moves customer and event data between systems as a managed pipeline rather than a 1C-to-Bitrix24 bridge.
- **Multiwoven** — Multiwoven is open-source reverse ETL that syncs records from a warehouse into business tools.
- **Zoho CRM** — Zoho CRM manages the customer and deal records that a 1C-Bitrix24 sync keeps financially current.

## FAQ

### What authentication does the 1C-Bitrix24 Exchange API use?

The 1C-Bitrix24 Exchange API authenticates with an API key sent in the X-Auth request header, as declared in its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs.

### Can I pull only the ASUP records that changed instead of a full export?

Yes. The API exposes a dedicated ASUP updates operation that returns only changed objects alongside the full-export operation, so your agent can run a light incremental sync between scheduled full loads.

### What are the rate limits for the 1C-Bitrix24 Exchange API?

The OpenAPI spec does not specify rate limits. Check the vendor documentation at b24platform.ru for current limits before scheduling frequent full ASUP exports.

### Is there a 1C-Bitrix24 Exchange API MCP server?

You do not need an MCP server to give your agent the 1C-Bitrix24 Exchange API. Jentic connects it directly from the API Directory: import it, store your X-Auth key once, and your agent calls the export, counterparty, and invoice operations on demand.

### Can I limit what my agent is allowed to do with the 1C-Bitrix24 Exchange API?

Yes. Write a rule that allows only the two ASUP export reads, so the agent can pull full and incremental object sets but cannot push counterparties or write invoices, and every call it makes is logged.

### How do I sync 1C data into Bitrix24 with this API through Jentic?

Search Jentic for an intent like 'export ASUP objects to Bitrix24' and it returns the matching operation with its input schema, then your agent calls it with the X-Auth key Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.