Error

A valid request URL is required to generate request examples

{
  "id": "store-rivoli",
  "name": "Boutique Rivoli",
  "city": "Paris 1er",
  "region": "Île-de-France",
  "active": true
}

{
  "error": {
    "code": "VALIDATION_FAILED",
    "message": "<string>",
    "statusCode": 123,
    "fieldErrors": [
      {
        "field": "<string>",
        "message": "<string>"
      }
    ]
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

Network

Reactivate (reopen) a store

Reopens a closed store by flipping its active flag back to true, the exact inverse of POST /stores/{storeId}/deactivate. It restores exactly one thing: the store’s eligibility to receive NEW operations, so it reappears in pickers and may be routed sales and transfers again. It resurrects nothing that was closed while the site was shut — no fiscal period reopens, no register session resumes, no transfer is revived. It never touches a sealed record: the store id is inside the NF525 signed body and is the addressing key here, never rewritten, and no sales_tickets or fiscal_signatures row is read or written. Idempotent: reopening an already-active store is a no-op that returns it unchanged. 404s for an unknown store. Same PERMISSION TRAP as the deactivate route (solya-pos#950): the guard accepts pos.settings.manage but the use-case asserts the kernel config:manage permission.

POST

stores

{storeId}

reactivate

Error

A valid request URL is required to generate request examples

{
  "id": "store-rivoli",
  "name": "Boutique Rivoli",
  "city": "Paris 1er",
  "region": "Île-de-France",
  "active": true
}

{
  "error": {
    "code": "VALIDATION_FAILED",
    "message": "<string>",
    "statusCode": 123,
    "fieldErrors": [
      {
        "field": "<string>",
        "message": "<string>"
      }
    ]
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

{
  "error": {
    "message": "<string>",
    "statusCode": 123
  }
}

Authorizations

Authorization

string

header

required

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

storeId

string

required

Minimum string length: 1

Response

The reopened store directory record (active: true).

string

required

Minimum string length: 1

name

string

required

Minimum string length: 1

city

string

required

Minimum string length: 1

region

string

required

Minimum string length: 1

active

boolean

required

Ventes & encaissement

Catalogue & stock

Finance

Clients & fidélité

Marketing & promotions

Services

Assistant

Intégrations & données

Système

Reactivate (reopen) a store

Authorizations

Path Parameters

Response