Skip to main content
POST
Answers the incoming takeover request currently in progress for the silo entry’s address, the same one the takeover form shows. Use it instead of the form to answer from your own system. See Moving parties between Plateformes Agréées for the full flow.
  • Accept without effective_date to take over on the date the new PA requested. If that date is too soon, the answer is the earliest possible date.
  • Accept with effective_date to agree on another date. The date must be at least 3 business days and 4 calendar days away, whichever is later.
  • Reject to refuse the takeover. Any effective_date is ignored.
The answer wakes the workflow’s Wait for migration approval step immediately. An address can only be answered once: a second call returns 400.

Authorizations

​
Authorization
string
header
required

Authenticate using a valid Invopop enrollment token in the Bearer scheme.

Example: Authorization: Bearer <token>

Path Parameters

​
silo_entry_id
string
required

ID of the org.Party silo entry being onboarded.

Example:

"5b45453c-cdd0-11ed-afa1-0242ac120002"

Body

application/json
​
action
enum<string>
required

Answer to the takeover request.

  • accept - Let the new PA take over the address.
  • reject - Refuse the takeover.
Available options:
accept,
reject
Example:

"accept"

​
effective_date
string<date>

Effective date of the takeover (YYYY-MM-DD), only used with accept. Omit it to use the date the new PA requested. Must be at least 3 business days and 4 calendar days away, whichever is later.

Example:

"2026-11-16"

Response

Answer recorded. Returns the decision that will be sent to the new PA.

​
migration_id
string
required

ID (UUIDv7) of the migration the request belongs to.

Example:

"019a1b2c-3d4e-7f50-8a1b-2c3d4e5f6a7b"

​
request_number
string
required

Request number assigned by the new PA, in the form <SIREN>_<new PA matricule>_<YYYYMMDD>_<NN>_<counter>.

Example:

"123456789_0999_20261023_01_101500"

​
address
string
required

Billing address being taken over, as it appears in the PPF Annuaire: the SIREN, optionally followed by a suffix (for example 123456789_ACHATS). It carries no scheme prefix and is not a Peppol ID.

Example:

"123456789"

​
status
enum<string>
required

Decision sent to the new PA in the MOBILITY_RESPONSE.

  • ACCP - Accepted on the requested date.
  • ACWC - Accepted on another effective date.
  • RJCT - Rejected, with motif REFUS_CLIENT.
Available options:
ACCP,
ACWC,
RJCT
Example:

"ACCP"

​
effective_date
string<date>

Agreed effective date of the takeover. Omitted for RJCT.

Example:

"2026-11-12"