> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/management-api/making-api-requests.md).

# Making API Requests

All API calls are made to an API REST server, using GET, POST, PATCH, or DELETE requests, depending on the API.

The body of each request, if any, should be plaintext containing valid JSON.

Each request needs to have a proper [**Management API Authorization**](/management-api/management-api-authorization.md) header.

### API Version

All APIs should be used in their `/api/v1/` version.

{% hint style="info" %}
If not specified, endpoints have a maximum pagination limit of **1000 items per request**.
{% endhint %}

### Rate Limiting

All Management API requests are subject to per-company rate limits.

For details on limits per plan and how rate limiting works, see [Rate Limiting](https://docs.licensespring.com/license-api/rate-limiting).


---

# 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.licensespring.com/management-api/making-api-requests.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.