Digidom Pro Digidom API

Name: Digidom API
Brand: Digidom API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbearer15 EndpointsREST

For Agents

Read Digidom organizations, documents, invoices, orders, subscriptions, leads, letters, and payments. Bearer-token (JWT) authenticated.

Install Jentic One Beta

Connect the Digidom API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Digidom 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Digidom API.

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

GET STARTED

Start building with Digidom API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Digidom API for, with concrete tasks.

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

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.

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.

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.

Search Jentic for 'list Digidom invoices', load the schema, and report the total amount outstanding across all unpaid invoices

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for digidom api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Digidom JWT bearer tokens live in the encrypted Jentic vault. Agents read invoices, documents, and letters through Jentic without ever holding the JWT, and rotation is handled centrally without touching agent code.

Intent-based discovery

Agents search Jentic by intent — for example 'list Digidom invoices' or 'fetch a Digidom organization' — and Jentic returns the matching operation with its parameter schema.

Time to first call

Direct Digidom integration: 1-2 days for JWT handling, pagination, and per-resource sync. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using Digidom API through Jentic.

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 at https://app.jentic.com/sign-up.

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 <jwt>` 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.