To execute S7 Agent API operations, applications must send an HTTPS POST request to the S7 Agent API endpoint.
Environments
Follow steps to quickly get an access to API
Actual
| ||||||||||||||||||||||||
Table of contents:
Schemas
S7 Agent API makes WSDLs for all of versions available for download.
When you are developing S7 Agent API applications that send requests and receive responses, you might find it helpful to validate the contents of your messages against the relevant schema.
Headers
The following table describes the HTTP headers that you typically set in a S7 Agent 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 | Basic authorization string | Required | Authorization | Credentials that you received from our S7 technical support. Check out Quick Start for how to get it |
| 3 | Operation name | Required | SOAPAction | Depends on operation that you want to execute |
| 4 | Type of content | Required | Content-Type | Sets the content type of the request. Always "text/xml" |
If you didn't pass Version of API in request a default one will be executedS7 agent API required encrypted HTTP requests via HTTPS only. Check out Quick Start for how to get SSL certificate.
The following example shows headers of a typical SearchFlights operation of 0.52 version API on Test environment:
POST /agent-api/gaia HTTP/1.1 Host: qa-gaia.s7.ru Content-Type: text/xml SOAPAction: "http://api.s7.ru/SearchFlightsJourney" X-API-Version: 0.52 Authorization: Basic ********************* |
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.
Operation names
Applications must send the "SOAPAction" key in headers of request to the S7 Agent API for determination of operation.
| # | Operation | SOAPAction value (actual for v0.52) |
|---|---|---|
| 1 | book | "http://api.s7.ru/Book" |
| 2 | cancelBooking | "http://api.s7.ru/CancelBooking" |
| 3 | changeBook | "http://api.s7.ru/ChangeBook" |
| 4 | demandTickets | "http://api.s7.ru/DemandTickets" |
| 5 | flightInfo | "http://api.s7.ru/FlightInfo" |
| 6 | orderCreate | "http://api.s7.ru/OrderCreate" |
| 7 | orderChange | "http://api.s7.ru/OrderChange" |
| 8 | read | "http://api.s7.ru/Read" |
| 9 | reprice | "http://api.s7.ru/Reprice" |
| 10 | retrieveTicket | "http://api.s7.ru/RetrieveTicket" |
| 11 | retrieve TST | "http://api.s7.ru/RetrieveTST" |
| 12 | searchFlightsFlex | "http://api.s7.ru/SearchFlightsFlex" |
| 13 | searchFlightsBySlice | "http://api.s7.ru/SearchFlightsBySlice" |
| 14 | searchFlightsJourney | "http://api.s7.ru/SearchFlightsJourney" |
| 15 | seatMap | "http://api.s7.ru/SeatMap" |
| 16 | servicePrice | "http://api.s7.ru/ServicePrice" |
| 17 | voidTicket | "http://api.s7.ru/VoidTicket" |