---
title: "Confirm the onboarding submission"
method: POST
path: "/apps/gov-fr/v1/entry/{silo_entry_id}/confirm"
---

# Confirm the onboarding submission

`POST /apps/gov-fr/v1/entry/{silo_entry_id}/confirm`

## Request

- Base URL: `https://api.invopop.com`
- URL: `https://api.invopop.com/apps/gov-fr/v1/entry/{silo_entry_id}/confirm`
- Auth: none required
- TypeScript: <https://skmtc.dev/invopop/apis/access-service-api/docs/apps/gov-fr/v1/entry/:silo_entry_id/confirm/post.ts> (a function with typed inputs; its response is checked against the schema)

Finalises the approval and pokes the queued
`agreement.wait.approval` task so the onboarding workflow
continues.

Identity verification (`POST /identity`) is required on both
paths. In addition:

- **In-app signing**: `POST /sign` must have been called.
- **Pre-signed PDF**: `POST /agreement` must have been called.

Returns the approval flow status. A `submitted` status means
the submission is under review; the workflow will advance once
a decision is made.

## Path parameters

- `silo_entry_id` string, required

## Response `200`

Submission confirmed. Returns the approval flow status.

- ConfirmResponse
  - `status` string, required: Current status of the approval flow after finalisation.

## Other responses

- `400`: The request is malformed or missing required parameters.
- `401`: Missing or invalid authentication token.
- `403`: The authenticated enrollment is not allowed to access this silo entry.
- `404`: The referenced silo entry or its party registration could not be found. The party must be registered before submitting the OTP.
- `422`: The request was well-formed but failed business validation — e.g. the uploaded file is not a valid PDF.
- `500`: An unexpected server-side error occurred.

---

[API](https://skmtc.dev/invopop/apis/access-service-api.md) - [All operations](https://skmtc.dev/invopop/apis/access-service-api/llms.txt) - [OpenAPI document](https://skmtc.dev/invopop/apis/access-service-api/revisions/fc954f96ea62?raw)