This is a high-level overview of a typical response from S7 Agent API.
Headers
The following table describes the HTTP headers that you received in a S7 MSE API response:
| # | Name | Key in headers | Description |
|---|---|---|---|
| 1 | Version of API | X-API-Version | Executed version of API
|
| 2 | Type of content | Content-Type | The content type of the response. Always "text/xml" |
| 3 | Conversation ID | X-API-Conversation | The identificatior of transaction.
|
The following example shows headers of a typical SearchFlights operation of 0.35 version API on Test environment:
| Code Block | ||
|---|---|---|
| ||
Content-Type: text/xml SOAPAction: "http://api.s7.ru/SearchFlights" X-API-Version: 0.35 Authorization: Basic oV5zbWlyCx92X3M3dfS6dGFpbDpxLTE2OXFs X-API-Conversation: ceec2d2d-8081-4d48-9df9-a712f6236220 |
Table of contents:
| Table of Contents |
|---|
Successful results
Successful responses typically includes the following structure (actual for 0.35 version):
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<result id="vI6FGb59SpQWElktM09l44tkt" session="eFvNjn2PKFDJVAs0RLbhhZITz" solutionCount="12" solutionSet="FoS0VzPw4UkLQExJm46znbA">
<mso>
<solution id="pFo605MVUMf0VZaw2xYIZZVO0" saleTotal="RUB24050">
<ext link="https://travelwith.s7.ru/mseDeeplink.action?LAN=RU&partner=16f3d011b0&TA=2&TC=1&TI=1&SUP=SITA&CP=F&CUR=RUB&TF=24050&FLC=1&FSC1=1&FN1=179&AC1=S7&DD1=2017-12-06&DT1=11:15:00&AD1=2017-12-06&AT1=19:15:00&DA1=DME&AA1=OVB&SC1=Q">
<SalePriceWithoutYQ amount="8600" currency="RUB"/>
<SalePriceWithoutYQAndYR amount="7100" currency="RUB"/>
<SalePriceWithoutYR amount="7100" currency="RUB"/>
</ext>
<pricing paxCount="2">
<ext>
<SalePriceWithoutYQ amount="8600" currency="RUB"/>
<SalePriceWithoutYQAndYR amount="7100" currency="RUB"/>
<SalePriceWithoutYR amount="7100" currency="RUB"/>
<pax adults="2"/>
</ext>
</pricing>
<pricing paxCount="1">
<ext>
<SalePriceWithoutYQ amount="6850" currency="RUB"/>
<SalePriceWithoutYQAndYR amount="5350" currency="RUB"/>
<SalePriceWithoutYR amount="5350" currency="RUB"/>
<pax children="1"/>
</ext>
</pricing>
<pricing paxCount="1">
<ext>
<SalePriceWithoutYQ amount="0" currency="RUB"/>
<SalePriceWithoutYQAndYR amount="0" currency="RUB"/>
<SalePriceWithoutYR amount="0" currency="RUB"/>
</ext>
</pricing>
<slice>
<segment arrival="2017-12-06T19:15+07:00" cabin="COACH" carrier="S7" departure="2017-12-06T11:15+03:00" destination="OVB" duration="240" flight="S7179" origin="DME">
<ext operationalDisclosure="OPERATED BY GLOBUS LLC"/>
<operationalDisclosure carrier="GH"/>
</segment>
</slice>
</solution>
<solution>
...
</solution>
</mso>
</result> |
For more information about received data in successful response, check RQ pages divided by operation in reference.
Unsuccessful results
Unsuccessful responses typically includes the following structure (actual for 0.35 version):
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version='1.0' encoding='UTF-8'?>
<result id="C08FNvhbikL0RLcXhWhWcE">
<error type="input">
<message>version: Unrecognized api version.</message>
</error>
</result> |
For an unsuccessful responses, API returns Errors with technical info in the message tag.
For Сheck Errors page for more information about possible errors, check Errors pages divided by operation in reference.
Common questions
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|