> For the complete documentation index, see [llms.txt](https://dev.skladon.com/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.skladon.com/main/v2/integration/api/api-usage-tips-and-limits.md).

# API usage tips and limits

**You should use our API wisely and use only reasonable amount of API requests**

It is recommended to use [Webhooks](/main/v2/integration/webhooks.md) to reduce repeatable API calls.

If there is case that webhooks are not match for your scenario and you need to fetch multiple records there are also filter endpoints for orders, products, receivings, returns etc.  These endpoint alows  you to retrieve multiple records, filter and sort them and also specifiy necessary  columns.

For example [endpoint for products filter](https://dev.skladon.com/main/integration/api/products#products-filter).

More details in API documentation itself.

{% content-ref url="/pages/uhAilXU5MqDfVyESpNr5" %}
[API](/main/v2/integration/api.md)
{% endcontent-ref %}

### API rating

*Api rate limiting is planned for 2025 and will be described here.*


---

# 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://dev.skladon.com/main/v2/integration/api/api-usage-tips-and-limits.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.