> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/store/add-new-numberseries.md).

# Add new numberseries

Add a new numberseries to a tenant. A tenant holds at most one SERVICE series, and every service number is taken from it, whatever store registers the service order, so it never issues the same number twice. Creating the SERVICE\_WORKSHOP extension, or a save that leaves it active, creates the series when the tenant has none. A second SERVICE series is refused with a 400.

Required permissions: NUMBER\_SERIE

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Store","description":"Store"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"requestBodies":{"NumberSeriesCreateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/NumberSeriesCreateSchema"}}}}},"schemas":{"NumberSeriesCreateSchema":{"title":"NumberSeriesCreateSchema","type":"object","properties":{"end":{"type":"integer"},"name":{"type":"string"},"start":{"type":"integer"},"type":{"$ref":"#/components/schemas/NumberSeriesTypeENUM"},"numberSeriesUid":{"$ref":"#/components/schemas/UID"}},"required":["end","name","start","type"]},"NumberSeriesTypeENUM":{"enum":["PURCHASE","VOUCHER","SERVICE","INTERNAL_PURCHASE","RMA_ORDER","CUSTOMER_LEDGER","CUSTOMER_NUMBER"],"title":"NumberSeriesTypeENUM","type":"string"},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"NumberSeriesResponseSchema":{"properties":{"currentValue":{"type":"integer"},"end":{"type":"integer"},"name":{"type":"string"},"numberSeriesUid":{"$ref":"#/components/schemas/UID"},"start":{"type":"integer"},"type":{"$ref":"#/components/schemas/NumberSeriesTypeENUM"}},"required":["numberSeriesUid","name","type","currentValue","end","start"],"title":"NumberSeriesResponseSchema","type":"object"}},"responses":{"NumberSeriesResponse":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/NumberSeriesResponseSchema"}}},"description":"Number series response"}}},"paths":{"/tenants/{tenantUid}/number-series":{"post":{"description":"Add a new numberseries to a tenant.\nA tenant holds at most one SERVICE series, and every service number is taken from it, whatever store registers the service order, so it never issues the same number twice. Creating the SERVICE_WORKSHOP extension, or a save that leaves it active, creates the series when the tenant has none. A second SERVICE series is refused with a 400.\n\nRequired permissions: NUMBER_SERIE\n","operationId":"post-tenants-number-series","requestBody":{"$ref":"#/components/requestBodies/NumberSeriesCreateRequest"},"responses":{"200":{"$ref":"#/components/responses/NumberSeriesResponse"}},"summary":"Add new numberseries","tags":["Store"]}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/developers/api-documentation/store/add-new-numberseries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.