canonical: https://jentic.com/apis/api.digidom.pro/digidom # Digidom Pro Digidom API Jentic publishes the only available OpenAPI specification for Digidom API, keeping it validated and agent-ready. Digidom is a French company-incorporation and ongoing-management service: the API exposes the customer-facing operations needed to read organizations, documents, invoices, orders, subscriptions, leads, users, letters, payments, products, tasks, and messages. Customers and partner integrations use it to mirror their Digidom workspace into other systems - pulling invoices into accounting tools, syncing organization records into CRMs, or surfacing scanned mail letters in operational dashboards. Authentication uses JWT bearer tokens. ## For AI agents Read Digidom organizations, documents, invoices, orders, subscriptions, leads, letters, and payments. Bearer-token (JWT) authenticated. ## Scope Does not handle company incorporation filings, signature workflows, or banking transactions - use for reading Digidom organizations, documents, invoices, and related records only. ## Capabilities - List and retrieve organizations the customer manages via /organizations - Read scanned and uploaded documents via /documents and `/documents/{id}` - List and retrieve invoices via /invoices, including detail by id - Inspect orders and subscriptions associated with a Digidom account - Pull lead, user, letter, payment, product, task, and message records for downstream sync ## Use cases ### Invoice Sync to Accounting Pull Digidom invoices into an accounting tool like Pennylane or Sage so French customers see their company-management invoices alongside everything else. GET /invoices returns the list with status and date filters, and GET `/invoices/{id}` fetches the full record. Schedule the sync nightly to keep books current without manual export. Example prompt: Fetch /invoices created in the last 24 hours, then GET `/invoices/{id}` for each to retrieve full details and post into the accounting ledger ### Mirror Organization Records into a CRM Digidom customers managing multiple companies often want their CRM to mirror the organization records that live in Digidom. GET /organizations enumerates them and GET `/organizations/{id}` returns the detailed record. Pair with a CRM upsert call so reps see the latest legal entity name, registration status, and metadata without leaving the CRM. Example prompt: List organizations via GET /organizations and upsert each into HubSpot Companies with the Digidom id stored as a custom property ### Scanned Letter and Document Archival Digidom scans physical mail and stores it as digital documents and letters. GET /letters and GET /documents enumerate what is available; the per-id endpoints return the full metadata. Compliance and operations teams use this to archive scanned mail into a document-management system rather than logging into Digidom every day. Example prompt: List /letters from the last 7 days, fetch each by id, and store the metadata and references in a SharePoint folder ### AI Agent Back-Office Assistant An AI agent uses Digidom via Jentic to surface organization status, recent invoices, and scanned letters on demand without holding the Digidom JWT. The agent searches Jentic by intent, loads the schema, and executes the read with parameters supplied at runtime. Useful for founders running multiple French entities who want a single chat interface across them. Example prompt: Search Jentic for 'list Digidom invoices', load the schema, and report the total amount outstanding across all unpaid invoices ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/organizations` | List organizations on the account | | GET | `/organizations/{id}` | Get an organization by id | | GET | `/invoices` | List invoices | | GET | `/invoices/{id}` | Get an invoice by id | | GET | `/documents` | List documents | | GET | `/letters` | List scanned letters | | GET | `/payments` | List payments | ## Key resources - **Organizations** — Legal entities managed under a Digidom account - **Documents** — Scanned and uploaded documents associated with organizations - **Invoices** — Digidom-issued invoices with detail by id - **Orders and Subscriptions** — Service orders and recurring subscriptions - **Leads, Users, Letters, Payments, Products, Tasks, Messages** — Operational records spanning sales, ops, mail handling, and account activity ## Why Jentic - **Setup:** Wiring the Digidom API by hand means handling its JWT bearer auth, targeting the v1 host, and mapping the organization, invoice, document, and letter routes yourself. Through Jentic you install once, import Digidom from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Digidom puts the resource id in the URL path (`/organizations/{id}`, `/invoices/{id}`), so a rule can pin your agent to one organization or invoice: it can read that record and nothing else. You choose the operations it may call, so broad list operations are only included if you add them. - **Credential handling:** Your Digidom JWT bearer token 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 'list Digidom invoices' or 'fetch a Digidom organization', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Qonto API** — Qonto provides French business banking that pairs with Digidom company management. - **Xero Accounting API** — Xero is a common destination for invoices and payments synced out of Digidom. - **HubSpot Account Info API** — HubSpot is a typical CRM destination for Digidom organization and lead records. ## FAQ ### Why is there no official OpenAPI spec for Digidom API? Digidom does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Digidom API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Digidom API use? Digidom uses JWT bearer-token authentication. The token is issued by Digidom and sent in the `Authorization: Bearer ` header. Jentic stores the JWT encrypted in the vault and refreshes it as needed so agents never embed raw tokens in code. ### Can I list invoices on the Digidom API? Yes - GET /invoices returns the list of invoices on the account with status and date filters; GET `/invoices/{id}` returns the full record for a specific invoice. Use the list endpoint for incremental sync into an accounting tool and the by-id endpoint to fetch the latest detail when generating reports. ### What are the rate limits for the Digidom API? Digidom does not publish fixed rate limits in the public spec. Treat the API as moderate-throughput and avoid tight loops over per-id endpoints when you can use the list endpoint instead. If you receive a 429 response, back off and retry with exponential delay. ### How do I mirror Digidom organizations into a CRM through Jentic? Run `pip install jentic`, search for 'list Digidom organizations', load the GET /organizations schema, and execute. For each organization, run a Jentic call against your CRM (for example HubSpot Companies) to upsert the record. Storing the Digidom id as a CRM custom property keeps subsequent updates idempotent. ### Does the Digidom API let me create new organizations or invoices? The endpoints surfaced in this spec are read-oriented - they enumerate and retrieve organizations, invoices, documents, and other records. Creating new entities or issuing invoices is typically done through the Digidom UI or partner-onboarding flows. Confirm with Digidom if you need write access for a specific resource. ### Can I limit what my agent is allowed to do with the Digidom API? Yes. Because you run Jentic One yourself, your own rules decide which Digidom operations and credentials the agent may use, and it can call nothing else. Since Digidom puts the resource id in the URL path, such as `/organizations/{id}` and `/invoices/{id}`, a rule can pin the agent to a single organization or invoice so it reads that record only. Broad list operations like GET /organizations or GET /invoices are available to the agent only if you choose to include them.