> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apinizer.com/llms.txt
> Use this file to discover all available pages before exploring further.
# HTTP Request Header Names
> You can make request headers ready and selectable in API Gateways and Test Console by defining request headers globally. You can manage header names that can be used in HTTP requests and add custom header names.
Request header is an HTTP header (Http Header) that can be used in HTTP requests to provide information about the request context so that the server can adapt the response. For example, Accept- \* headers indicate the allowed and preferred formats of the response. Other headers can be used to provide authentication information (Authorization, to control caching, or to get information about user agent or referrer, etc.).
There are 33 Request Header Names by default in the Apinizer Platform:
* Accept
* Content-MD5
* Content-Type
* Cookie
* Date
* Expect
* Forwarded
* From
* Host
* If-Match
* If-Modified-Since
* Accept-Charset
* If-None-Match
* If-Range
* If-Unmodified-Since
* Max-Forwards
* Origin
* Pragma
* Proxy-Authorization
* Range
* Referer
* TE
* Accept-Datetime
* Upgrade
* User-Agent
* Via
* Warning
* Accept-Encoding
* Accept-Language
* Authorization
* Cache-Control
* Connection
* Content-Length
You cannot edit and delete those added by Apinizer by default.
In addition to the above, you can add your own **Request Headers**.
## Creating a New Request Header Name
Click the **+New** button from the **Management → System Settings → Predefined Values → Request Header Names** screen.
**An image containing Request Header Name creation settings is shown below:**
The fields used for Request Header Name creation configuration are shown in the table below.
| Field | Description |
| --------------------------- | --------------------------------------- |
| Header Name *(Header Name)* | Field where the header name is entered. |