Track your Guichet unique formalities from your own code

What you can build on the Guichet unique

• List formalities with their status

  Build this

  Reads the formalities on the tableau de bord reached through Suivre l'avancement d'une formalité d'entreprise, with status, status date and amount.

  Takes

  Status (optional), type: création, modification or cessation (optional), SIREN (optional)

  Returns

  Liasse number, company name, SIREN, formality type, status, status date, your reference, file name, amount

• Get regularisation requests

  Build this

  Opens each formality in the Formalité en attente de régularisation block and reads each correction asked of you, the field concerned and the deadline.

  Takes

  Liasse number (optional)

  Returns

  Liasse number, company name, request type, observation, field concerned, deadline

• Get rejection reasons

  Build this

  Opens each formality in the Formalités rejetées block and reads the reasons given for the rejection.

  Takes

  Rejected since (optional)

  Returns

  Liasse number, company name, SIREN, formality type, rejection reasons, status date

• Follow annual accounts filings

  Build this

  Reads your dépôts des comptes annuels (annual accounts filings) on the Guichet unique dashboard for annual accounts, with where each one stands.

  Takes

  Status (optional), SIREN (optional)

  Returns

  Company name, SIREN, status, status date

Automate the Guichet unique with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• New regularisation requests, every weekday morning

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  Get the regularisation requests on the formalities in Formalité en attente de régularisation.

  Step 2

  Keep the requests that were not there on the last run.

  Step 3

  Email you each one with its observation, the field concerned and the deadline.

• Formality status changes, posted to your own system

  Build this

  Starts

  Every weekday at 9:00

  Step 1

  List your formalities with their status and status date.

  Step 2

  Keep the formalities whose status changed since the last run.

  Step 3

  Post liasse number, your reference, SIREN, status and status date to your webhook.

• Weekly report on annual accounts filings

  Build this

  Starts

  Every Monday at 7:30

  Step 1

  Get your annual accounts filings with their status.

  Step 2

  Keep the filings that are not yet validated.

  Step 3

  Group them by status and email you the list, with company name, SIREN and status date.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “List formalities with their status” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "procedures.inpi.fr/list_formalities",
    "input": {
      "status": "AMENDMENT_PENDING",
      "type": "modification"
    }
  }'

{
  "status": "completed",
  "data": {
    "formalities": [
      {
        "liasse_number": "J00000104521",
        "company_name": "ACME CONSEIL",
        "siren": "123456789",
        "type": "modification",
        "status": "AMENDMENT_PENDING",
        "status_date": "2026-11-10T09:12:00+01:00",
        "your_reference": "ACME-2026-114",
        "file_name": "Acme Conseil transfert de siège",
        "amount": 198,
        "currency": "EUR"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

The Guichet unique’s own options

INPI publishes an API for the Guichet unique that anyone with an account on its e-procedures portal can connect to. It files creation, modification and cessation formalities and annual accounts, lists your formalities with their status and amount, and handles signature, payment and answers to regularisation requests. INPI says its documentation will change as the application adds features.

Read on November 12, 2026: Accès aux API du Guichet unique, Contrat d'interface, June 2026 (PDF).

Signing in to the Guichet unique

The Guichet unique signs you in with an INPI Connect account, one email address and password for all your INPI customer areas, or with FranceConnect+. With Fous you sign in once through the Guichet unique's own sign-in with your own INPI Connect account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Status emails arrive the next morning

When a formality is rejected or goes to En attente de régularisation, the Guichet unique tells you by email the next morning.

The authorities set the pace, not the portal

The competent authorities examine each formality, and the Guichet unique cannot commit to their processing times. The Kbis is sent by the greffe, not from the dashboard.

How you sign in decides how you sign

Modifications, cessations and annual accounts need an advanced electronic signature on a qualified certificate when you sign in with INPI Connect. FranceConnect+ allows a free simple signature instead.

A rejected file starts again

A rejected formality is filed again from the start, fixing the reason given. INPI's API documentation lists an EXPIRED status and says a formality in it can still be regularised.

More in Government: UK and Western Europe

• Companies House WebFiling
• Planning Portal
• Chorus Pro
• FCA RegData
• net-entreprises.fr
• Urssaf compte employeur
• ePortal ESTV
• FinanzOnline
• impots.gouv.fr espace professionnel
• MOT Testing Service

Other industries: Sunshine 811, AppraisalPort, BSA E-Filing System, PASSPort, Ohio Business Gateway, bizfile Online.