To execute S7 MSE API operations, applications must send an HTTPS POST request to the S7 MSE API endpoint
S7 MSE API doesn't support compressed request in GZIP format, but request for response in GZIP format is available (check Headers for more info) |
Environments
Follow steps to quickly get an access to API
| |||||||||||||||||||||||||
Table of contents:
Schemas
S7 MSE API doesn't have WSDL, but you can check samples and references for all requests and responses.
Headers
The following table describes the HTTP headers that you typically set in a S7 MSE API request:
Name | Mandatory | Key in headers | Description | |
|---|---|---|---|---|
| 1 | Version of API | Optional | X-API-Version | Depends on version of API that you want to execute
|
| 2 | Type of content | Required | Content-Type | Sets the content type of the request. Always "text/xml" |
| 3 | Response compression | Optional | Accept-Encoding | Sets the compressed type of API response. Only "gzip" available |
If you didn't pass Version of API in request a default one will be executedS7 MSE API required requests via HTTPS only.
The following example shows headers of a typical request of 0.35 version API on Test environment:
POST /mse HTTP/1.1 Host: qa-api.s7airlines.com Content-Type: text/xml X-API-Version: 0.35 |
Versions
You can use any released versions if your requests conform that syntax. Check references for detailed explanation of input&output parameters and possible errors for every version of API.
If you didn't pass Version of API in request a default one will be executed. You always able to check executed API version in response headers.
But we recommend that you always specify version in all you request to avoid unexpected responses form another versions of API.