Install Jentic One Beta

Connect the 1C–Bitrix24 Exchange API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 1C–Bitrix24 Exchange API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fb24platform.ru%2Fmain" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fb24platform.ru%2Fmain" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with 1C–Bitrix24 Exchange API.

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

Use Cases

Patterns agents use 1C–Bitrix24 Exchange API for, with concrete tasks.

GET STARTED

Start building with 1C–Bitrix24 Exchange API

Explore with Jentic One

View OpenAPI Document

★ 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.

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.

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.

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

Key Endpoints

4 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using 1C–Bitrix24 Exchange API through Jentic.

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.

B24platform Ru 1C–Bitrix24 Exchange API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Community OpenAPI document · agent-readyAnalyticsData PipelinesapiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: Sync full ASUP objects from 1C into Bitrix24, Get only the ASUP records that changed since my last export, Push updated counterparty payer details from 1C into Bitrix24, Create an invoice in Bitrix24 from a 1C billing document

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

20%

Example Density

How richly the API is illustrated with examples.

91%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

74%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

80%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

94%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the 1C–Bitrix24 Exchange API to your agent

Capabilities

Use Cases

Start building with 1C–Bitrix24 Exchange API

Key Endpoints

Why Jentic?

Related APIs

FAQs

B24platform Ru 1C–Bitrix24 Exchange API

Jentic AI Readiness Score

1C–Bitrix24 Exchange API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness