View Source

How to get an access to JIRA

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

Contact to one of our managers and fill in the application form, regarding to Quick Start | S7 Agent API section
Check your invitation in email and proceed to received link
Set password and log in JIRA
Go to Projects and find Agent API Support (AAS)
Done! You have the access

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

Types of issues

The following example shows types of issues that you can submit to S7 API support:

#	Type	Description	Example
1	Bug	Error that completely or partiality affects the service	We get the error "010-TIME" when used the OrderCreateRQ. Please check
2	Story	Software 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 on
3	Task	Technical request for implementation	Please issue a certificate for the QA environment
4	Question	Reference-information query about the functionality of the service	When is the release of the new version of the S7 Agent API?

Bug report

Before asking our technical support:

Dig through FAQ | S7 Agent API for most common issues you can be faced with
Explore errors list divided by operations in Reference section and check handling instructions

Please pass the Conversation ID (value of "X-API-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 name	Additional info
1	agentPayment	for successful result: PNR (booking record locator, e.g. SJF6D) 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
3	book	for successful result: PNR (booking record locator, e.g. SJF6D) for unsuccessful result: origin, destination and departure date for all slices name, surname, passenger type for all of passengers
4	cancelBooking	PNR (booking record locator, e.g. SJF6D)
5	changeBook	PNR (booking record locator, e.g. SJF6D)
6	demandTickets	for successful result: ETK (ticket number, e.g. 4212411174798) for unsuccessful result: PNR (booking record locator, e.g. SJF6D)
7	findRules	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	read	PNR (booking record locator, e.g. SJF6D)
9	reprice	origin, destination and departure date for all slices, passenger types and count
10	retrieveTicket	ETK (ticket number, e.g. 4212411174798)
11	searchFlights	origin, destination and departure date for all slices, passenger types and count
12	seatMap	origin, destination, marketing flight number (e.g. S7041) and departure date for all slices
13	servicePrice	origin, destination and departure date of a flight and fare code (fareBasisCode value e.g. QBSRT) and passenger types and count
14	voidTicket	ETK (ticket number, e.g. 4212411174798)