---
title: Headers and parameters
description: Most InfluxDB API endpoints require parameters in the request–for example, specifying the database to use. Common parameters The following table shows common parameters used by many InfluxDB API endpoints. Many endpoints may require other parameters in the query string or in the request body that perform functions specific to those endpoints. Query parameter Value type Description db string The database name InfluxDB HTTP API endpoints use standard HTTP request and response headers. The followin
url: https://docs.influxdata.com/influxdb3/enterprise/api/headers-and-parameters/
estimated_tokens: 663
product: InfluxDB 3 Enterprise
version: enterprise
---

[Download InfluxDB 3 Enterprise API Spec](/openapi/influxdb3-enterprise-openapi.yml)

Most InfluxDB API endpoints require parameters in the request–for example, specifying the database to use.

### Common parameters

The following table shows common parameters used by many InfluxDB API endpoints. Many endpoints may require other parameters in the query string or in the request body that perform functions specific to those endpoints.

| Query parameter | Value type | Description |
| --- | --- | --- |
| db | string | The database name |

InfluxDB HTTP API endpoints use standard HTTP request and response headers. The following table shows common headers used by many InfluxDB API endpoints. Some endpoints may use other headers that perform functions more specific to those endpoints–for example, the write endpoints accept the `Content-Encoding` header to indicate that line protocol is compressed in the request body.

| Header | Value type | Description |
| --- | --- | --- |
| Accept | string | The content type that the client can understand. |
| Authorization | string | The authorization scheme and credential. |
| Content-Length | integer | The size of the entity-body, in bytes. |
| Content-Type | string | The format of the data in the request body. |