HTTP Headers allow passing additional information with the request or the response. A request header consists of its case-insensitive name followed by a colon ':', then by its value.
For example, when there is something like this in the sample code in buyer specification:
Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l - this is a header.
How Request With a Lead is Formed
The request with a Lead sent from PX to the Buyer is a link that consists of 4 parts:
1. URL - Test Ping URL and/or Test Post URL in Authentication method block.
2. Connection type - Ping connection type (POST/GET) and/or Post connection type (POST/GET) fields in Configure API block.
- Ping content type and Post content type fields in Configure API block;
- All fields related to Authentication Method selected (Username, API Key, Header);
- All fields specified in HTTP Headers block.
4. Body - all fields mapped in Step 2 of API Builder.
As soon as you select Ping/Post Content Type or enter values in Authentication Method block, these headers are automatically added as parameters of the request, for example:
When HTTP Headers Block is Useful
HTTP Headers block is useful in 3 cases:
1. Buyer specification contains headers that do not match any of the options in Authentication Method block.
2. There are multiple headers, and HTTP Headers block allows you providing as many options as you need.
3. When you configure API connection for a Ping Post Buyer Campaign, headers specified in Authentication Method block are related to both Ping and Post requests. If you need to create HTTP headers only for Ping or only for Post request, you can enter them in HTTP Headers block.