---
title: "🇫🇷 Norme · Submit a new flow"
method: POST
path: "/flow-service/v1/flows"
tags: ["AFNOR XP Z12-013/FlowService"]
---

# 🇫🇷 Norme · Submit a new flow

`POST /flow-service/v1/flows`

Submit a flow. A flow is a single-invoice file, with :

  - an XML/PDF file with the data of the invoice


The flow is created with a `flowInfo` object, allowing to qualify the flow.


A flow can be :

  - an invoice (CII, UBL, Factur-X,...) 

  - a lifecycle (CDAR) 

  - or a e-reporting file

## Query parameters

- `Sha256` string, byte
- `TrackingId` string
- `Name` string, required
- `ProcessingRule` 'B2B' | 'B2BInt' | 'B2C' | 'B2G' | 'B2GInt' | 'OutOfScope' | 'B2GOutOfScope' | 'ArchiveOnly' | 'NotApplicable' | 'Undefined' — - B2B : e-invoicing - B2BInt : International B2B e-reporting - B2C : B2C e-reporting - B2G : e-invoicing for B2G sales - B2GInt - OutOfScope : Out of scope (not regulated flow) - B2GOutOfScope - ArchiveOnly : Archive only, no transmission - NotApplicable : Not Applicable - Undefined : Not yet defined when in Pending state or unable to define when in Error state
- `FlowSyntax` 'CII' | 'UBL' | 'FacturX' | 'CDAR' | 'FRR', required — Syntax of the original file belonging to a flow
- `FlowProfile` 'Basic' | 'CIUS' | 'ExtendedCTCFR' | 'Undefined'
- `AdditionalProperties` object
- `Data.CanRead` boolean
- `Data.CanWrite` boolean
- `Data.CanSeek` boolean
- `Data.CanTimeout` boolean
- `Data.Length` integer
- `Data.Position` integer
- `Data.ReadTimeout` integer
- `Data.WriteTimeout` integer
- `FileName` string
- `ContentType` string

## Headers

- `Request-Id` string, uuid
- `Organization-Id` string

## Response `200`

OK

- FullFlowInfo — Identified Flow info: flow info + id + timestamp
  - `flowId` string, required
  - `submittedAt` string, date-time, required — The flow submission date and time (the date and time when the flow was created on the system) This property should be used by the API consumer as a time reference to avoid clock synchronization issues
  - `sha256` string, byte, nullable — The sha256 is the fingerprint of the attached file: - if provided in the request: it should be checked once received - if not provided in the request: it may be computed and returned in the response

---

[API](https://skmtc.net/neotimo/apis/neotimo-api.md) · [All operations](https://skmtc.net/neotimo/apis/neotimo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/neotimo/neotimo-api/revisions/2ecf51b1543e/schema)
