| # | 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 in Scenarios page. |
| 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? | All JIRA request types specified in Support section, as for feature requests — check it out and let us know your needs! |
| 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 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 prioritize 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 for online sales. The only way to make it happen is to proceed separated flows fo those parts of journey. |
| 31 | 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 |
| 32 | General | What is the main scenario for API using? | Discover from simplest flows to the best practices at Scenarios page of API's documentation |
| 33 | 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 |
| 34 | 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 reorder |
| 35 | searchFlights (feature request) | 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 to our updates by release notes and the launched blog |
| 36 | searchFlights | LowFare нужен поиск Аналог метапоиска на NDC — очень нужен ШОППИНГ | It wasn't update for a long time because we going to deprecate this type of search. We returned back to our Road Map |
| 37 | searchFlights | Фильтром по семейству, например только флекс тарифы | Сделаем в ближайшее время |
| 38 | searchFlights | Нужно явно расписать схему про комбинированные, некомбинированные тарифы и разницу между поисками. | Дополним |
| 39 | searchFlights | Стоповеры нигде не нашли |  Valeriya Shishkova |
| 40 | searchFlights | Примеры пришлют на собственные рейсы, где нет бейсика (салехард?) На определённых рейсах нет BASIC причём на глубокую выдачу. Агент говорит, что не видел на маршруте SLY-OVB. | Ждем примеры для всех похожих случаев |
| 41 | searchFlightsFlex | Даты от и до во флексе необязательный | Да |
| 42 | searchFlightsFlex | Описать флексиблдэйт. Что за метод? Как пользоваться? В чём отличие? | В ближайшее время |
| 43 | seatMap | Не явные схемы кабин, не удобно выбирать места Причесать SeatAvailabilityRQ; Явным образом отображать карту мест (exit row, extra space) согласно борту, выполняющему рейс. | Скоро изменим |
| 44 | book | Добавить проверку на некомбинированный тариф перед бронированием | Будет потом |
| 45 | book | Время на завершение бронирования для ввода данных. Места будут уходят, пока пассажир вводит данные — это плохо. | Решение из зала — сначала фейковый пассажир, потом ченджбуком заменять |
| 46 | book | Какие будут начеты по фейковым броням? | Valeriya Shishkova |
| 47 | book | Проверки при CodeShare/SPA? Сможем ли выписать билет, в случае если не будет подтверждение от партнера (статус сегмента и локатор патнера)? | Сейчас нет, но будут: Перезачитка пнр, получение статусов и пр |
| 48 | book | Военно перевозочные документы | в обозримом будущем - НЕТ |
| 49 | changeBook | Изменение имя и фамилию пассажира? Это можно? Полностью все? | Нельзя. |
| 50 | changeBook | Люди забывают добавит детей: | Нельзя |
| 51 | reprice | Замена тарифа при репрайсе — по какой причине? | Valeriya Shishkova |
| 52 | reprice | После бронирования не должно быть изменения RBD, так? Нужно прояснить | Valeriya Shishkova |
| 53 | reprice | При изменении цены в репрайсе, увеличенная часть на какой участок? Хотят знать в ответе Цена сейчас послайсевая | Valeriya Shishkova |
| 54 | reprice | Вопрос про общие таксы. Нельзя увидеть таксы по слайсам. Агент хотел бы увидеть подробную разбивку такс по слайсам. | Valeriya Shishkova |
| 55 | reprice | ГДС предоставляет время жизни цен, может ли апи предоставлять эту дату? В жиру поточнее сформулируют задачу | Нет такой технической возможности пока |
| 56 | reprice | Why do we need to use reprice operation to get the same price as from searchFlights? | Only reprice operation return the final price for itinerary solution and it may be changed at the moment.
|
| 57 | servicePrice | Прайсинг животных? | Будет в ближайшее вресмя |
| 58 | servicePrice | Сноуборды и прочее? | Будет в ближайшее вресмя |
| 59 | voidTicket | Про правила войдирования | уже есть в факе |
| 60 | retrieveTicket | Нет статуса, применился 3D или нет 3D. Агент не увидел инфо о применении скидки | Будет в ближайшее вресмя |
| 61 | retrieveTicket | ретрив броней созданных вручную | Теперь все, что получили, то и отрисовали |
| 62 | demandTicket | Выписка животных? | Да, будет |
| 63 | demandTicket | Одновременно выписка билетов и EMD? | Да, будет |
| 64 | agentPayment | Фасилитейдет букинг для агентов | Будет доступно, но позже, дополнительно объявим |
| 65 | New feature | Варианты тарифов для конкретного перелета. Те сначала поиск идет бейсика, вторым шагом смотреть все 4 тарифа как опции для текущего выбранного перелета | flightPrice |
| 66 | New feature | Очереди важны (нотификации о рейсе и прочие) Получение списка локаторов в очереди Удаление из списка очереди локаторов | Больше инфы, не в этом году |
| 67 | New feature | Парсинг тарифов инфо | Больше инфы, не в этом году |
| 68 | New feature | Информация о семействе брендов. Многие берут непосредственно с сайта s7.ru и возможно ли через API получать эту инфу? | Ок, но нужны примеры |
Overview
Content Tools