Контур.Экстерн
Connect Kontur.Extern to the AI agent: organisations, report drafts, docflows, certificates
Connect Kontur.Extern to the AI agent: organisations, report drafts, docflows, certificates. The agent tracks response deadlines and the status of filed reporting.
DocumentationПо 11 организациям принято 34 отчёта, 2 отклонены, 3 ждут квитанцию.
- Оба отказа — расхождение ИНН подписанта с сертификатом
- По «Гранд-Логистике» требование ФНС: срок ответа истекает через 2 дня
Показать черновики, которые так и не ушли?
Integration scenarios
Response deadlines for regulators
The agent collects docflows across every organisation in the account and shows where the deadline to answer the tax office or a fund runs out first.
Status of filed reporting
For each submitted report the agent shows whether it was accepted, rejected or is still waiting for a receipt, and gathers the rejection reasons into one list.
Signing certificates about to expire
The agent finds organisations whose signer certificate expires within the next month — before it blocks submissions.
Drafts that were never sent
The agent aggregates report drafts by organisation and form and shows which ones are still unsent as the filing date arrives.
How to connect
Request API access for Extern
Use the «Отправить заявку» (Submit request) form at kontur.ru/extern/api. A manager emails the client_id and a key-issuing link. Production needs a contract with Kontur; a test environment with its own account and certificate comes first.
Issue the api-key from the emailed link
The link opens integrations.kontur.ru — press «Выпустить ключ» (Issue key). The value is a GUID: 8-4-4-4-12 hex characters separated by hyphens. For production you also create a self-integration on the same page.
Get an Access Token at identity.kontur.ru
The token comes from Kontur's OpenID provider, not from Extern: scope «openid extern.api», client_id from the email, and client_secret is your api-key. Sign in with the Kontur account that already has access to the organizations you need.
Check the token lifetime and signing certificate
The Access Token lives 3600 seconds (one hour) — copy it right away and keep the refresh_token from the same response. Sending and signing reports also requires a valid electronic signature certificate on the account.
What the agent does in the first 10 minutes
- Will gather document flows across all your organizations and show which reply deadline to a regulator expires first
- Will find organizations whose signing certificate expires within a month — before it blocks a report submission
- Will send a morning digest: which drafts await submission, what was accepted, and what was rejected and needs fixing
FAQ
How do I connect Kontur.Extern?
With two keys: an access token with the extern.api scope issued by the Kontur OpenID provider, and a GUID-style api-key from the integrations account. Both are opened by a manager after a request on the Extern website — you cannot issue the keys yourself.
What does the agent see in Extern?
Organisations in the account, report drafts and the documents attached to them, docflows with the regulators and their response receipts, plus the list of certificates — within the permissions of the account.
Can the agent submit a report?
Submission runs as a chain of asynchronous tasks and requires a qualified electronic signature, which Extern does not create by itself. The agent checks and assembles the data, and leaves signing and submission to a person with the certificate.
Is there a test environment?
Yes, the connection supports a separate sandbox address on testkontur.ru with its own account and a test certificate. The production environment is opened under a contract with Kontur.