A valid request URL is required to generate request examples{
"id": "plan-item-0001",
"planId": "plan-restock-aigle-32",
"skuId": "sku-veste-aigle-m",
"storeId": "shop-metz-muse",
"quantity": 12,
"recommendedQuantity": 18,
"unitCostCents": 4200,
"status": "TO_REVIEW",
"source": "recommendation"
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123,
"fieldErrors": [
{
"field": "<string>",
"message": "<string>"
}
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Add a line to a draft plan
Adds one line to a plan that is still a DRAFT. Lines move ONLY while the plan is a draft: once it is validated, sent or agreed, the lines are what somebody committed to — a supplier answered a quantity, a shop expects goods — and adding one afterwards changes what was agreed without anybody being told. source is required (manual, workflow, recommendation, import): « qui a mis cette ligne là » is asked of every plan that goes wrong and cannot be answered afterwards. Every line starts TO_REVIEW.
A valid request URL is required to generate request examples{
"id": "plan-item-0001",
"planId": "plan-restock-aigle-32",
"skuId": "sku-veste-aigle-m",
"storeId": "shop-metz-muse",
"quantity": 12,
"recommendedQuantity": 18,
"unitCostCents": 4200,
"status": "TO_REVIEW",
"source": "recommendation"
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123,
"fieldErrors": [
{
"field": "<string>",
"message": "<string>"
}
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Authorizations
Authorization: Bearer <token>. Accepts EITHER a Keycloak access token (scopes-in-token) OR an opaque POS session token; both resolve to the same pos.* scope vocabulary the route guards enforce.
Path Parameters
The plan id, e.g. plan-restock-aigle-32.
1Body
110 < x <= 900719925474099110 <= x <= 90071992547409910 <= x <= 9007199254740991manual, workflow, recommendation, import Response
The line as persisted, in TO_REVIEW.
The line as persisted, in TO_REVIEW.
11110 < x <= 90071992547409910 <= x <= 90071992547409910 <= x <= 9007199254740991TO_REVIEW, READY_FOR_ORDER, FLAGGED manual, workflow, recommendation, import