> For the complete documentation index, see [llms.txt](https://cee-systems.gitbook.io/tcpapi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cee-systems.gitbook.io/tcpapi/estreaming-api/estreaming/capacity-planning.md).

# Capacity Planning

eStreaming API pricing is based on RPS (requests per seconds).

Our free tier is a subject of **daily transactions limit** and **1RPS** capacity limitation.

If you want to use eStreaming API without this limitations, you have to calculate the capacity you need, and then reserve it for you.

## Reserved capacity calculation

We recommend following approach for the capacity calculation.

1. End user of API studies log log files of his web site.
2. After log files analysis, assumptions and estimations are made on how many concurrent requests per second will be send to eStreaming API.
3. Calculated number of concurrent requests is called reserved capacity.

## Ordering and changing reserved capacity

After you order your reserved capacity your daily transactions limit will be removed and you'll able to run queries according to selected RPS capacity.

You can feel free to change your reserved capacity by one day advance notice.

## Handling request bursts on your site

It is highly possible you are going to experience short periodic bursts of requests activity on your site. We recommend you to implement consequent retry API calls in case you receive API response message, that you are over your capacity.

If you are running into bursts too frequently, we recommend you to increase you reserved capacity.

## Capacity error messages

Free tier users might get the following error message in case daily requests limit is exceeded

```javascript
 {
     status: 'error',
     dataAvailable: false,
     requestId: '72a85761-19fb-11e7-a60b-c71e54dd7836',
     executionTimeInMs: 184,
     originalRequest: {
         pointOfSale: 'IT',
         searchPhrase: '20170304CUFLCE',
         minSearchDate: '2017-02-20',
         maxSearchDate: '2017-02-26'
     },
     errorMessage: 'Daily capacity limit exceeded'
 }
```

When the number of concurrent requests per second (RPS) is exceeded the relevant error message is also displayed.

```javascript
{
    status: 'error',
    dataAvailable: false,
    requestId: '72a85761-19fb-11e7-a60b-c71e54dd7836',
    executionTimeInMs: 184,
    originalRequest: {
        pointOfSale: 'IT',
        searchPhrase: '20170304CUFLCE',
        minSearchDate: '2017-02-20',
        maxSearchDate: '2017-02-26'
    },
    errorMessage: 'RPS capacity limit exceeded'
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cee-systems.gitbook.io/tcpapi/estreaming-api/estreaming/capacity-planning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.