Electronic document flow

The docflow category covers Russian electronic document flow (ЭДО) and adjacent systems — sending and receiving documents through the standard connector flow.

Document-flow connectors

These connectors are reached through the standard connector flow. The catalog includes, among others:

  • Diadoc (diadoc) and SBIS (sbis) — EDO operators: send and receive documents.
  • Kontur.Extern (kontur_extern) — reporting and document exchange.
  • The 1C family (onec_accounting, onec_trade, onec_document_flow, …) — RPC-style document operations.
  • MoySklad (moysklad) — trade documents and inventory.
  • Chestny ZNAK (chestnyznak) — product marking codes and documents.
  • HRlink (hrlink) — HR electronic document flow (КЭДО).

Calling a document-flow connector

Every EDO connector uses the same three-step flow as any other connector — discover, read the passport, execute:

1

Connect an account

An EDO connector returns real data only after the owning organization connects an account for it. Credentials are encrypted at rest and resolved per call — see Connecting accounts.

2

Read the passport

Call describe_service for the connector to see its modules, concrete recipes (verb + path or RPC method), field hints and response examples. Don't guess the shape — the passport carries it.

describe_service(service="diadoc")
3

Execute the call

Send or receive a document with connector_execute. REST operators take an HTTP method and path; the 1C family is RPC — leave path empty and pass the method name in method.

Marking and inventory, not only EDO

The category is broader than EDO operators: chestnyznak covers product marking codes, moysklad covers trade documents and stock, and hrlink covers HR document flow (КЭДО). All follow the same connector flow.

FAQ

Which electronic document flow (EDO) systems are supported?

The docflow category covers Diadoc, SBIS and Kontur.Extern (EDO operators), the 1C family, MoySklad, Chestny ZNAK for product marking, and HRlink for HR document flow (КЭДО). Each is a connector addressed by its key.

How do I call an EDO connector?

Through the standard connector flow: list_services for the catalog, describe_service to read the passport (modules, recipes, field hints), then connector_execute to send or receive a document. EDO operators are reached like any other connector.

Do I need to connect an account first?

Yes. An EDO connector returns real data only after the owning organization connects an account for it. Credentials are encrypted at rest and resolved per call — see Connecting accounts.

Are 1C connectors REST or RPC?

The 1C family (onec_accounting, onec_trade, onec_document_flow, …) is RPC-style: with connector_execute you leave path empty and pass the RPC method name in method. The passport's recipes show the exact shape.

Frequently asked questions

Which electronic document flow (EDO) systems are supported?

The docflow category covers Diadoc, SBIS and Kontur.Extern (EDO operators), the 1C family, MoySklad, Chestny ZNAK for product marking, and HRlink for HR document flow (КЭДО). Each is a connector addressed by its key.

How do I call an EDO connector?

Through the standard connector flow: list_services for the catalog, describe_service to read the passport (modules, recipes, field hints), then connector_execute to send or receive a document. EDO operators are reached like any other connector.

Do I need to connect an account first?

Yes. An EDO connector returns real data only after the owning organization connects an account for it. Credentials are encrypted at rest and resolved per call — see Connecting accounts.

Are 1C connectors REST or RPC?

The 1C family (onec_accounting, onec_trade, onec_document_flow, …) is RPC-style: with connector_execute you leave path empty and pass the RPC method name in method. The passport's recipes show the exact shape.

Was this page helpful?