Versions Compared

Old Version 1

changes.mady.by.user Pavel A. Smirnov (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Ruslan Tkachuk

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To execute S7

Agent

MSE API operations, applications must send an HTTPS POST request to the S7

Agent

MSE API endpoint

.

Note

S7 Agent MSE API doesn't support compressed request and/or response in GZIP format, but response in GZIP format is available (check Headers for more info)

Environments

Follow steps to quickly get an access to API

Excerpt




Test

Production

#
1

Version

Endpoint

Endpoint

1
2

0.

21

52

WSDL

Default

WSDL

Default

2

0.35WSDLNot installed
Note

If you are ready to a new versions which are not installed on production environment — notify our technical support by JIRA



Table of contents:

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. MSE API doesn't have WSDL, but you can check samples and references for all requests and responses.

Anchor
headers
headers
Headers

The following table describes the HTTP headers that you typically set in a S7 Agent 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

(warning) If you didn't pass Version of API in request a default one will be executed

2
Basic authorization stringRequiredAuthorization3Operation nameRequiredSOAPActionDepends on operation that you want to execute4
Credentials that you received from our S7 technical support. Check out Quick Start for how to get it

Type of content

Required

Content-Type

Sets the content type of the request.

Always

"text/xml" or "application/xml"

3

Response compression

Optional

Accept-Encoding

Sets the compressed type of API response. Only "gzip" available

S7 MSE API required S7 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 request of 0.35 52 version API on Test environment:

Code Block
linenumberstrue
POST /agent-api/gaiamse HTTP/1.1
Host: qa-gaia.s7.ru
Content-Type: text/xml
SOAPAction: "http://api.s7.ru/SearchFlights"https://qa-api.s7airlines.com
X-API-Version: 0.35
Authorization: Basic oV5zbWlyCx92X3M3dfS6dGFpbDpxLTE2OXFs52 
Content-Type:application/xml

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.

#OperationSOAPAction value (actual for v0.35)1agentPayment"http://api.s7.ru/AgentPayment"2baggageCharges"http://api.s7.ru/BaggageCharges"3book"http://api.s7.ru/Book"4cancelBooking"http://api.s7

.

ru/CancelBooking"

5changeBook"http://api.s7.ru/ChangeBook"6demandTickets"http://api.s7.ru/DemandTickets"7findRules"http://api.s7.ru/FindRules"8read"http://api.s7.ru/Read"9reprice"http://api.s7.ru/Reprice"10retrieveTicket"http://api.s7.ru/RetrieveTicket"11searchFlights"http://api.s7.ru/SearchFlights"12seatMap"http://api.s7.ru/SeatMap"13servicePrice"http://api.s7.ru/ServicePrice"14voidTicket"http://api.s7.ru/VoidTicket"

Common questions

Excerpt Include
Common FAQ | S7 MSE API
FAQ Common | FAQnopaneltrue| S7 MSE API