Skip to main content
POST
/
apps
/
gov-fr
/
v1
/
entry
/
{silo_entry_id}
/
agreement
Upload the signed agreement
curl --request POST \
  --url https://api.invopop.com/apps/gov-fr/v1/entry/{silo_entry_id}/agreement \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "data": "aSDinaTvuI8gbWludGxpZnk="
}
'
{
  "error": "missing siren parameter"
}

Documentation Index

Fetch the complete documentation index at: https://docs.invopop.com/llms.txt

Use this file to discover all available pages before exploring further.

Stores the customer’s signed PDF on the silo entry together with the chosen signature method. Two methods are accepted: esignature (PAdES — validated cryptographically against the EU Trusted List) and identity (hand-signed — verification deferred to Invopop’s approval service, requires identity images uploaded via POST /identity first). This call only persists the document. Call POST /confirm afterwards to mark the submission complete and let the onboarding workflow proceed.

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
​
signature
enum<string>
required

How the customer signed the agreement.

  • esignature - Signed electronically (PAdES). The PDF signature is validated against the EU Trusted List.
  • identity - Signed by hand and accompanied by uploaded identity images. Verification is delegated to Invopop's approval service.
Available options:
esignature,
identity
​
data
string<byte>
required

Base64-encoded binary of the signed PDF agreement. Must be application/pdf.

Response

Signed agreement stored.