Versions Compared

Old Version 19

changes.mady.by.user Nikita Kartashev

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 by Service DeskKaiten (it's much faster than email)


Table of contents:

Table of Contents

How to get an access to

JIRA

Kaiten

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

  1. Contact to one of our managers and fill in the application form, regarding to Quick Start | S7 Agent API
  2. Go to Service DeskGo to Kaiten and register by your email
  3. Done! You have the access (улыбка)(smile)

For any problem, contact our support team by portal at Service Desk

Types of issues

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 issuesImage Removed

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:
  • Conversation ID from response message: /Envelope /Body /OrderViewRS /@EchoToken
    • Or
    #Operation nameAdditional info
    1
    agentPayment
    book
    • for successful result: PNR (booking record locator, e.g.
    SJF6DX
    • MUOSSZ)
    • for unsuccessful result: 
      • origin, destination and departure date for all slices
      • name, surname, passenger type for all of passengers
    2
    baggageCharges
  • origin, destination and departure date of a flight
    • and fare code (fareBasisCode value e.g. QBSRT)
  • and passenger types and count
    • 3book
    • for successful result: PNR (booking record locator, e.g. SJF6DX)
    • for unsuccessful result: 
      • origin, destination and departure date for all slices
      • name, surname, passenger type for all of passengers
    4
    cancelBookingPNR (booking record locator, e.g.
    SJF6DX
    MUOSSZ)
    5
    3changeBookPNR (booking record locator, e.g.
    SJF6DX
    MUOSSZ)
    6
    4demandTickets
    • for successful result: ETK (ticket number, e.g.
    4212411174798
    • 4212402059143) 
    • for unsuccessful result: PNR (booking record locator, e.g.
    SJF6DX
    • MUOSSZ)
    7findRules
    • requested hash (flightInfoHash value e.g. eNoLDHQKDgoxNDewNDBy8XX1D3MKNje0MAQASgcF8g==)
    • or origin, destination and departure date of a flight, and fare code (fareBasisCode value e.g. QBSRT)
    8
    5readPNR (booking record locator, e.g.
    SJF6DX
    MUOSSZ)
    9
    6reprice
    • origin, destination and departure date for all slices
    • and passenger types
    10
    7retrieveTicketETK (ticket number, e.g.
    4212411174798
    4212402059143)
    11
    8searchFlights
    • origin, destination and departure date for all slices
    • and passenger types
    12
    9searchFlightsFlex
    • origin, destination and departure date for all slices
    • and passenger types
    13seatMaporigin, destination, marketing flight number (e.g. S7041) and departure date for all slices14
    10servicePrice
    • origin, destination and departure date of a flight
    • and fare code (fareBasisCode value e.g. QBSRT)
    • and passenger types and count
    15
    11voidTicketETK (ticket number, e.g.
    4212411174798
    4212402059143)