HTTP Headers
The following HTTP headers are used in the Digipost API.
Header | Descripiton | Required |
---|---|---|
X-Digipost-UserId | Used to identify your organisation’s Digipost id. | Yes |
Date | Consists of timestamp for when the request was sent. This timestamp must be specified in the RFC 1123 format, for example «Wed, 29 Jun 2011 14:58:11 GMT». If the difference between the timestamp of the request and the time on the Digipost server exceeds 5 minutes, the request will be rejected. | Yes |
X-Content-SHA256 | Consists of a hash of the request’s content (excluding headers). | Yes |
X-Digipost-Signature | Created from the three headers specified above, and is basis for the security that exists in the Digipost api. Read more about this in the security section. | Yes |
UserAgent | Specifies which client and version is being used. This header is not required but is helpful when troubleshooting. Example values for this header are: «Company X Digipost client v.2.0» or «Digipost API Client v1.0.0». | No |