Please use the following Vipps HTTP headers for all requests to the Vipps APIs. These headers provide useful metadata about the merchant's system, which help Vipps improve our services, and also helps in investigating problems.
These headers are required for plugins and partners and sent by the official Vipps plugins. We strongly recommend that all customers with direct integration with the API to also do so.
Partners must always send the
Merchant-Serial-Number header, and we recommend
that everyone sends it, also when using the merchant's own API keys.
It can speed up any troubleshooting of API problems quite a bit.
For example, if the merchant's name is "Acme AS" and they offer three different systems: point of sale (POS) integration, web shop, and vending machines, the headers could be:
|Example value for POS
|Example for web shop
|Example for vending machine
|Example for WooCommerce plugin
|Example for Checkout plugin
|The name of the solution
|The version number of the solution
|The name of the plugin
|The version number of the plugin
|The MSN for the sales unit
- Please use self-explanatory, human-readable and reasonably short values that uniquely identify the system (and plugin).
- The max length of each header is 30 characters. See the API specification for details.
Vipps-System-Plugin-* headers do not make sense to you,
you can simply send the same as for
The important thing is that you send as much useful information as possible,
so it is as easy as possible to solve problems with your API requests if there are any.
Many API requests to Vipps APIs can be retried without any side effects
Idempotency-Key(in older APIs, this may be called,
in the header of the request.
For example, in case the request fails because of network error, it can
safely be retried with the same
Idempotency-Key key without causing a duplicate.
Idempotency-Key key must be generated by the merchant according to the API
Example HTTP request with all HTTP headers
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1Ni <truncated>