Versions Compared

Old Version 9

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

Saved on

compared with

New Version Current

changes.mady.by.user Danil Trefilov

Saved on

Key

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

If you're having issues using S7 Agent API, we're here to help.

Our support

...

team will help find answers about

...

integration and investigate any problem.

Please contact us

...

Info
titleNOTICE

NEVER USE THE "SUPPORT" PROJECT (SUP)

Steps for connection:

  1. request access from api.support@s7.ru
  2. check your invitation in email
  3. set password, log in
  4. go to Projects and find Agent API Support (AAS)
  5. done! you have access (улыбка)

Below you can see examples of tasks that you can create:

...

#

...

type

...

description

...

example

...

error that completely or partlity affects the service

...

technical request for implementation

...

by Kaiten (it's much faster than email)


Table of contents:

Table of Contents

How to get an access to Kaiten

There is a few steps to get an access to Kaiten:

  1. Go to Kaiten and register by your email
  2. Done! You have the access (smile)

For any problem, contact our support team by portal at Kaiten

New request

Image Added


On the Kaiten portal you can create a task:
  1. To consult on the methods used in the S7 API Agent, on errors that you have when using the S7 API Agent methods and eliminating.
  2. Getting access to the testing environment, production environment  and scenarios described in the S7 API Agent
  3. To consult on technical issues

Bug report 

Note

Before asking our technical support:

  • Find in FAQ | S7 Agent API most common problems you may encounter
  • Explore errors list divided by operations in Reference section and check handling instructions

Please pass the Conversation ID (value of "X-API-Conversation" or "X-Conversation" header in response) to S7 API support.

In case you haven't this data, pass:

  • Operation name
  • Request timestamp
  • Additional info to decrease waiting time for S7 API support feedback about your request:
#Operation nameAdditional info
1book
  • for successful result: PNR (booking record locator, e.g. MUOSSZ)
  • for unsuccessful result: 
    • origin, destination and departure date for all slices
    • name, surname, passenger type for all of passengers
2cancelBookingPNR (booking record locator, e.g. MUOSSZ)
3changeBookPNR (booking record locator, e.g. MUOSSZ)
4demandTickets
  • for successful result: ETK (ticket number, e.g. 4212402059143) 
  • for unsuccessful result: PNR (booking record locator, e.g. MUOSSZ)
5readPNR (booking record locator, e.g. MUOSSZ)
6reprice
  • origin, destination and departure date for all slices
  • and passenger types
7retrieveTicketETK (ticket number, e.g. 4212402059143)
8searchFlights
  • origin, destination and departure date for all slices
  • and passenger types
9searchFlightsFlex
  • origin, destination and departure date for all slices
  • and passenger types
10servicePrice
  • origin, destination and departure date of a flight
  • and fare code (fareBasisCode value e.g. QBSRT)
  • and passenger types and count
11voidTicketETK (ticket number, e.g. 4212402059143)

...