Uploading your own document
POST /developer/v1/files returns a presigned form, POST /developer/v1/files/{file_id}/_confirm
confirms the upload, and POST /developer/v1/documents accepts file_id
instead of template_id — your PDF then travels the route like any other
document. Same scope, documents:write.Only application/pdf up to 50 MB is accepted: the file goes to signing
exactly as you sent it.→ Uploading your own documentDocuments in the Developer API
The full document lifecycle: create from a template, routes, sending, approval, signing (ЭЦП/КЭД), and download, plus type, category, and template catalogs. New scopes —documents:read and documents:write.Added document webhooks: document.sent, document.completed,
document.rejected, and others.Reworked the docs structure: guides for
employees and
documents, with recipes.Data ingest from external systems
Added thePOST /developer/v1/ingest/{source_type} endpoint: a batch of records
from an external HR system with a create_missing flag.Records are matched by
external_id — re-sending does not create duplicates.List login methods
GET /developer/v1/login_methods returns the authentication methods enabled for the
tenant, with stable slugs: GOOGLE_SAML_SSO, EDS_CMS_QR, OTP_TELEGRAM.