If you didn't find your question it the list, please, provide it to our technical support by JIRA
| # | Group | Question | Answer | |||
|---|---|---|---|---|---|---|
| 1 | Application | How to specify endpoints of internal systems (e.g., portal for a call center, mobile application)? | If your system have no domain name, you should use IP address. In case it's not public, please, ask your account manager for further details | |||
| 2 | Application | It would be nice to know what data will be needed to fill out the application in advance | Check out blank application form added to Quick Start page | |||
| 3 | Application | What does testing under the supervision of S7 technologists include before proceeding to production? | Currently we working on it with our technologists. All scenarios will be described similar to the other scenarios | |||
| 4 | Application | It would be better to share with you credentials to our sites and test environments to bring to you our needs | Provide this information to your account manager or send credentials as a feature request to our technical support by JIRA | |||
| 5 | JIRA | Using one account for all integration specialists isn't suitable for us. Why you do not group accounts to make all issues that we have done were visible to all our specialists? | Our account policy has been changed which allows using multiple user accounts per agent instead only one for everyone. | |||
| 6 | JIRA | How to make requests for a new feature? | ||||
| 7 | Support | Is there any plan to launch operational 24/7 support for the production environment? | Yes, but these plans will be announced later | |||
| 8 | Notification | It's not clear if the environment is updated | We've just launched the blog to notify you about all environment updates. Stay tuned! | |||
| 9 | Notification | How we can be notified of environment downtime? | All possible downtimes will be published at the blog that we recently launched. Keep updated! | |||
| 10 | Notification | Where we can check system availability? | We've added this feature to our backlog and hope you'll soon be able to easily check the health status of environments | |||
| 11 | Documentation | We faced a lack of examples. Please, add: request for fare details, ticket void, multi-segment flights | Documentation will be up to date until | |||
| 12 | Documentation | When can we expect the next update of the API's documentation? How often will this happen? | We have no exact schedule for that, but plan to deliver small updates every week | |||
| 13 | Documentation | We do not observe documentation updates as a result of JIRA issues resolving | Not all questions are grabbed for insertion into documentation, only the most common or critical | |||
| 14 | Documentation | The API's documentation does not describe the following operations: voidTicket, demandTicket, changeBook | DemandTickets operation is already specified in API's documentation, check it out! | |||
| 15 | Documentation | Are all possible values for API's requests specified in the documentation? | Check out References page references with detailed explanation of I/O parameters (incl. possible values) and probable errors | |||
| 16 | Documentation | Published roadmap with launch dates will help us better plan our development. Especially if you plan to add new features and operations | Due to agile methodology we can't post exact launch dates of versions. Check priority lists of features in the Road Map For a better understanding all of them divided into operations and approximately into quarters | |||
| 17 | Deployment | How long will the old versions be available after the release of the new ones? | We have no strong deprecation policy, so it'd be available until everyone stops using old versions | .At the moment that we have to deactivate the old version until, we'll notify each user individually | .||
| 18 | Deployment | How much time do we have to move to the new versions? | There's no time limits. All older versions will be available as new ones at the same time | .|||
| 19 | Deployment | Is it possible I/O formats of version be changed over time? | No, all I/O enhancements will be introduced only by a new version of the API | .We can update old versions to apply hot fixes for urgent bugs, but they'll never change I/O too | .||
| 20 | Deployment | Can the version of the NDC schema be updated only for one of the operations? | If we decide to move to a new version of the NDC schema, then this will be done at a time for the all operations by releasing a new version | |||
| 21 | Deployment | When will the next version be released? How often will they go out? | We going to keep the pace approx. one release in three months but only for test environment | .
| .
| .|
| 22 | Non-functional | Has the API been stress tested? | Not yet | |||
| 23 | Non-functional | How was the value of high availiability calculated? It would be better to publish downtime statistics. | This value based on our internal statistics. From now you can check the blog for all possible downtimes | |||
| 24 | Non-functional | What are the min, max and mid response time for each operation? Also there's no info about timeouts | We posted selected statistics of response time for each operation to make it more transparent | |||
| 25 | Non-functional | Is there a load distribution depending on the agent? Do you limit the number of requests for each agent individually? | No, we do not limit the agents and we do not | prioritizeprioritise traffic | ||
| 26 | Fares | Ability of combining fares is still not clear represented in documentation. Why we able to book an itinerary with uncombinable fares via Gabriel and can not do the same via the API? | According to S7 technology it's prohibided to use uncombinable fare for a single ticket | |||
| 27 | Fares | Why subsidized fares are not available still? | According to requirements of The Ministry of Transport of the Russian Federation it's prohibided for online sales | |||
| 28 | Fares | When will be available shopping with interline flights? | Check priority lists of features in the Road Map Due to agile methodology we can't post exact launch dates, but features divided into approximately into quarters | |||
| 29 | Fares | What are the limitations of the 3D Agreement basic shopping scenario? What about discounts combinations? | All limitations for 3D Agreement basic shopping scenario already specified in documentation:
| |||
| 30 | Fares | What is the best way to book a journey to avoid round trip fares and to keep ability to use non-combinable fares for each slice separately? | According to S7 technology it's | prohibided prohibited for online sales. The only way to make it happen is to proceed separated flows fo those parts of journey | .||
| 31 | Fares | The API's documentation does not explain combining of fares | Fares are combined by fare family, e.g. only Flex (incl. FlexEconomy and FlexBusiness) or Basic (BasicEconomy and BasicBusiness) | |||
| 32 | General | Is there an updates of the current versions? If so, where can we find out about these updates? | Yes, but these hot fixes are only for urgent bugs and they're never change I/O. We also add info to Release notes of versions that have been fixed | |||
| 33 | General | What is the main scenario for API using? | Discover from simplest flows to the best practices at Scenarios page of API's documentation | |||
| 34 | General | Should we track look-to-book ratio? | We do not fix this value in the contract and only recommend that the value should not exceed 200-1 | |||
| 35 | General | Currently API returns the same error code in all fault cases. Could you divide it into different codes and provide instructins how to manage with it? | We already changed error responses from 0.35 version and going to reassign all API errors in the near future | |||
| 36 | searchFlights | We need a param in the request to limit the number of solutions in the response — there are too many of them | We added the feature request to the Road Map Check it out and stay tuned for our updates by release notes and the launched blog | |||
| 37 | searchFlights | Deprecation of LowFare search isn't a good idea. Could you update it and keep it alive? | It wasn't update for a long time because we going to deprecate this type of search. We returned it back to our Road Map | |||
| 38 | searchFlights | In same cases we need to search only for basic or flex fares. Could you add filter on your side? | We added the feature request to the Road Map | |||
| 39 | searchFlights | What is a difference between the types of search? | Search operations return many solutions for each day. Solutions include itinerary and pricing information.
Check searchFlights operation for more information | |||
| 40 | searchFlights | We expected stopovers in the searchFlights operation response, but diidn't find them. Is it deployed? | This feature was asked only for demandTicket and retriveTicket operations Please, for a better understanding, provide more details and additional examples to our technical support Check how to promote feature requests by JIRA | |||
| 41 | searchFlights | On route SLY-OVB we expected to get basic fare family, but searchFlights returned only flex. What happed? | Generally you recieve all of four fare families for all domestic flights. | |||
| 42 | searchFlightsFlex | Are days after and days before params mandatory for this operation? | No, if you do no set them you recieve result only for one day | |||
| 43 | searchFlightsFlex | What diferrence between searchFlights and searchFlightsFlex operations? |
| |||
| 44 | seatMap | The response of seatMap operation does not contain details such as: exit row, extra space, seats for infants in a lap, etc. | We preparing a huge update for this operation already. | |||
| 45 | book | If uncombinable fares are prohibited anyway, could you add additional validation to avoid that in book operation? | We added the feature request to the Road Map Check it out and stay tuned for our updates by release notes and the launched blog | |||
| 46 | book | Can we make reservations without passenger details or with a fake? We want to avoid situations when flight became sold out while passenger inputs his details for booking. | You can't skip passenger's name, surname and contact in creating reservation. Also according to S7 technology it's prohibided to modify name and surname after | |||
| 47 | book | What are the penalties for creating incorrect bookings? | All penalties for incorrect booking are described in your agency agreement. For more information, please, ask your account manager. | |||
| 48 | book | Does the API recheck status of segments and partner's PNR after booking created? Can we issue a ticket if there is no confirmation from a partner? | Currently the API checks only status of segments. We are working on additional checking for partner's PNRs already, this feature will be available soon. | |||
| 49 | book | Will it be possible to use military transportation documents? | Not in the near future due to impossibility of checking this type of payment for online sales | |||
| 50 | changeBook | Can name or surname of a passenger be changed after a booking is made? | According to S7 technology it's prohibided to modify name and surname in a booking | |||
| 51 | changeBook | Sometimes children or infants are forgotten to add to a booking. Is it possible to add them after a booking is made? | It's not possible to add a child (2-12 years) in a booking aftrer it's made due to S7 technology. | |||
| 52 | reprice | Why do we need to use reprice operation to get the same price as from searchFlights? | Only reprice operation returns the final price for itinerary solution and it may be changed at the moment by reason of:
In that case you have to use:
| |||
| 53 | reprice | For what reason can a requested fare be replaced in response of reprice operation? | There's a lot of cases in which this can happen (you may catch a fare code change), but the common are:
But the most common is only price changing. In that case you have to use:
| |||
| 54 | reprice | After booking is made, RBD can't be changed, is it right? | The only case for that is deprecation of RBD in the moment between searching for itinerary solutions and reprice operation. So the reservation system suggests the cheapest combinable RBD and fare for requested itinerary. But the most common is only price changing. In that case you have to:
| |||
| 55 | reprice | When a total price changes in response of reprice operation, how do we can know at what exactly segments the price was increased? | There's no way to find it out due to specificity of pricing in reservation system at the moment | |||
| 56 | reprice | Can we recieve the taxes divided into slices? | There's no way to split it due to specificity of pricing in reservation system at the moment | |||
| 57 | reprice | Reservation system provides the lifetime of prices in terminal mode. Can the API provide this info? | There's no lifetime of prices from reservation system. | |||
| 58 | servicePrice | When can we expect pets pricing? | We preparing a huge update for this operation already, which includes pets pricing. Stay tuned for our updates by release notes and the launched blog | |||
| 59 | servicePrice | Is it possible to receive the availability of special equipment pricing/allowance, such as a snowboard, a bicycle, etc? | Special equipment will be available in servicePrice pretty soon. Stay tuned for our updates by release notes and the launched blog | |||
| 60 | voidTicket | Where can I learn more about the rules of ticket voiding? | Check Electronic Ticketing Procedure of S7 Airlines (July 30, 2015) for any airline's rules details Documentation for cancelBooking and voidTicket operations overview will be available soon. | |||
| 61 | retrieveTicket | As a part of the execution of the 3D agreement scenario, when retrieve ticket, we expect to see the info whether the discount was applied or not, but there's no such | We added the feature request to the Road Map Check it out and stay tuned for our updates by release notes and the launched blog | |||
| 62 | retrieveTicket | We receive errors when reading a booking created in terminal mode | Recently all versions has been patched to show any data, included unexpected values. | |||
| 63 | demandTicket | Do you have any plans to launch EMD issuing for pet baggage? | We already have this feature in our Road Map Check it out and stay tuned for our updates by release notes and the launched blog | |||
| 64 | demandTicket | How can I issue tickets and EMD simultaneously by the API? | At the moment, there is such a possibility, but only for seats. | |||
| 65 | agentPayment | We found a mention about an facilitated booking operation "agentPayment", when will this operation be available to agents? | Currently we testing it with one of our partners only In case of a successful results with a single partner, we will announce this operation for all other partners Stay tuned for our updates by the launched blog | |||
| 66 | New feature | For us, search by slices (BrandedFares search type) is not convenient and we would like to receive prices for other availeble fares as similar as request for ancillaries pricing. | We already have new operation "flightPrice" in our Road Map | |||
| 67 | New feature | We would like to be able to work with queues (e.g., flight change notifications) by the API. Including managing a list of PNRs in the queue (adding to a list, reading a list, deleting from a list) | Please, for a better understanding, provide more details and additional examples to our technical support | |||
| 68 | New feature | Now we have to deal with parsing of fare description on our side. It would be great if the API did it | Please, provide to our technical support an exact list of params which you expect to recieve in response | |||
| 69 | New feature | Many of us use take fare family description directly from the site s7.ru and store as a static in itself. Is it possible to receive this information via the API? | Please, provide convincent form of a response of required operation to our technical support Check how to promote feature requests by JIRA |