Versions Compared

Old Version 12

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 you to get an access for API, help find answers about integration and investigate any problem.

Please contact us by JIRA where we have a project —  Agent API Support (AAS) Kaiten (it's much faster than email)

note

NEVER USE THE "SUPPORT" PROJECT (SUP)


Table of contents:

Table of Contents

How to get an access to

JIRA

Kaiten

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

  1. Go to Kaiten and register by your email
  2. Contact to one of our managers and fill in the application form, regarding to Quick Start section
  3. Check your invitation in email and proceed to received link
  4. Set password and log in JIRA
  5. Go to Projects and find Agent API Support (AAS)
  6. Done! You have the access (улыбка)(smile)

For any problem, contact our support team by email at api.support@s7.ru

Types of issues

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

#

Type

Description

Example

1Bug
Error that completely or partiality affects the service
We get the error "010-TIME" when used the OrderCreateRQ. Please check2StorySoftware system requirement (feature/change requests)We are not satisfied with the AirShoppingRQ method. Is it possible to add a query: parameter # 1, data # 2 and so on3Task
Technical request for implementation
Please issue a certificate for the QA environment4QuestionReference-information query about the functionality of the serviceWhen is the release of the new version of the S7 Agent API?

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
Bug report 

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
, use request timestamp and name+surname one of passengers (or another unique data from request) to identify your request.
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)