> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/api-reference/using-the-api/request-format-and-rate-limits.md).

# Request format and rate limits

Content negotiation, compression, character encoding, and request rate limits.

## HTTP request format

Resources are mapped to URLs, actions are mapped to verbs, and the remaining information is mapped to headers. Requests use content negotiation, compression negotiation, and content character encoding:

* **Content negotiation:** clients and servers agree on the format of the data. You can use content negotiation to view different representations of the same resource.
* **Compression negotiation:** the server supports compression encoding. Request compressed content with the `Accept-Encoding` header, for example `Accept-Encoding: gzip`.
* **Character encoding:** UTF-8 is the only supported character encoding.

| Request                                               | Description                                      |
| ----------------------------------------------------- | ------------------------------------------------ |
| `GET /api/v2/hosts/2` with `Accept: application/json` | Returns the JSON representation of the resource. |
| `GET /api/v2/hosts/2` with `Accept: application/xml`  | Returns the XML representation of the resource.  |

## Request rate limits

The API limits the maximum number of requests the RESTful service processes, to minimize the risk of client misuse affecting SDP performance.

| Parameter    | Limit                                   | Description                                                                    |
| ------------ | --------------------------------------- | ------------------------------------------------------------------------------ |
| `max-rate`   | 20 per second                           | Maximum requests per second for the RESTful service.                           |
| `burst-rate` | 100 requests (temporary burst capacity) | Generally higher than `max-rate`; allows higher throughput for a short period. |


---

# 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.silk.us/api-reference/using-the-api/request-format-and-rate-limits.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.
