Versions Compared

Old Version 38

changes.mady.by.user Pavel A. Smirnov (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Pavel A. Smirnov (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Steps

  1. Application for connection
    All information required for connection — in one application
  2. Access to the test environment
    Get access to the test environment and integrate under the supervision of S7 technicians
  3. Hello world!
    Set your software and make your first request!
  4. Running your tests
    Test the S7 Agent API to prevent future problems
  5. Signing of the contract of EDS
    Sign the contract electronically
  6. Access to production environment
    Get access to the production environment and complete integration
  7. Maintenance
    Use the all of capabilities of the S7 Agent API and stay tuned for a new features!
Roles

Choose your role

RoleDescriptionTarget period
Integratora developer, who creates a solution for agents and proceed integration with the S7 Agent API7 working days
Agent with own solutionan agent, who creates own solution for yourself and proceed integration with the S7 Agent API7 working days
Agent with Integrator's solutionan agent, who going to use solution to connect to S7 environment, provided by integrator 3 working days
Anchorenvironment environment


Environment

Excerpt Include
Submitting requests | S7 Agent API
Submitting requests | S7 Agent API
nopaneltrue

AnchorStep1Step1Step 1: Application for connection

Integrator

Agent with own solution

Agent with Integrator's solution

1. Contact to manager of your region and request for an application form (sample) at vm@s7.ru or https://api4agent.s7.ru/

2. Fill in the application form with a link to your portal and send it to S7 manager.

In the contact data of a technical specialist must be specified:

  • Technical specialist
  • Integrator representative
  • Agent representative
  • Technical specialist
  • Agent representative
  • Agent representative
  • Integrator representative

3. S7 checks your form and initiates registration in our systems, including JIRA for communication with our technical support

4. Receive JIRA account credentials from S7 by email to technical specialist or agent representative

5. Proceed by the link provided in email to set password and log in to JIRA

6. Go to Projects and find Agent API Support (AAS)

AnchorStep2Step2Step 2: Access to the test environment

Integrator

Agent with own solution

Agent with Integrator's solution

1. Check your environment for OpenSSL and install additional software (required to create a request for SSL certificate):

Panel
titleFor Windows/Solaris

Download the last binary version of OpenSSL at https://www.openssl.org/community/binaries.html and install software

Code Block
titleFor GNU/Linux
sudo apt install openssl
Panel
titleFor MacOS

No action is required — already included in OS

2. Use command line (as administrator) to create private key: Panel
Code Block
openssl genrsa -out ${clientkey}.pem 2048

You have to replace ${clientkey} into understandable name using your local naming policies

Image Removed

3. Create request for SSL certificate:

Panel
Code Block
openssl req -new -key ${clientkey}.pem -out ${clientcsr}.pem

Replace ${clientcsr} to the name used on previous step

You have to replace ${clientkey} and ${clientcsr} into understandable name using your local naming policies

Image Removed

4. Fill in the details of the request for SSL certificate:

Panel

Mandatory:

  • Country Name (2 letter code)
  • State or Province Name
  • Locality Name (eg, city)
  • Organization Name (eg, company)
  • Organizational Unit Name (eg, section)
  • Common Name (your name or server's hostname)

No need to specify:

  • A challenge password
  • An optional company name

5. Create a new task with the request of SSL certificate (request_csr) by JIRA

Panel

Image Removed

Attach to the task created request for SSL certificate (request_csr)
Check “Bin” (OpenSSL) folder for those files.

6. Receive credentials for test environment from our technical support:

Panel
  • a SSL certificate (*.crt file)
  • personal credentials for basic authentication (login and password)
  • test access parameters for requests (XML block Party)
  • test Client ID and Agent ID for testing shopping with 3D agreement

7. Import SSL certificate and create key store file:

Panel
Code Block
openssl pkcs12 -export -in ${clientcert}.pem -inkey ${clientkey}.pem -out ${client}.p12 -name "${name}"

Export Password – password for key store file which will be requested while importing into test software

Image Removed

Responsibility of Integrator

Agent do not issue a certificate for the test environment

AnchorStep3Step3Step 3: Hello world! 

Integrator

Agent with own solution

Agent with Integrator's solution

1. If you are using test software build in browser you have to import keys (or check your software's documentation):

Panel
titleFor Mozilla Firefox

Menu → Preferences → Advanced → ViewCertificates → Your Certificates → Import → Choose created key store file (*.p12) on previous step

Panel
titleFor Google Chrome

Settings → Advanced Settings → HTTPS/SSL → Import → Choose created key store file (*.p12) on previous step

2. For a better experience, we prefer to use SoapUI for testing:

Panel

Download the last binary version of SoapUI at https://www.soapui.org/downloads/soapui.html and install software

3. Open SoapUI and create a new SOAP project

Panel
  1. SoapUI → File → Preferences → New SOAP project
  2. Check available versions at test environment at the top of the page
  3. Copy relevant WSDL URL
  4. Past in form, fill a project name and press OK

4. Assign created key store file to the project

Panel
  1. Project → Show project view → WS-Security Configurations → Keystores;
  2. Click on "+" (Adds a new Keystore to this configuration)
  3. Set a path to p12-file and input the password

(warning) Do not use global settings (SoapUI → File → Preferences → SSL Setting) to save ability of using both environments without any additional setting changes

5. Create new request and set basic authentication

Panel
  1. Open tab "Auth" under request textarea
  2. Select "Authorization" = "Basic"
  3. Input Username and Password (your received them from our technical support on previous step)

You have to set it for all your requests

6. Set assigned keystore

Panel
  1. Go to tab "TestRequest Properties" under the projects tree
  2. Select imported p12-file in "SSL Keystore" parameter

You have to set it for all your requests

7. Set the endpoint of test environment at the top of request window

8. Fill in the request textarea by an example described below and send it!

Excerpt IncludeOW + 1xADT + Transit + CodeShare | v0.35 | searchFlights operationOW + 1xADT + Transit + CodeShare | v0.35 | searchFlights operationnopaneltrue

9. If you have no results, try to check your connection to exclude the case of incorrect credentials before you contact to our technical support by JIRA.

Panel
  1. Import key store file into the browser (see steps to set up browser above)
  2. Go to any URL from Environment section via browser

Responsibility of Integrator

All tests executes by a personal certificate of integrator

AnchorStep4Step4Step 4: Running your tests

Integrator

Agent with own solution

Agent with Integrator's solution

1. Choose one of available versions at test environment at the top of the page

2. Use header's parameters for selected version (If the parameter is not defined, the oldest version will be used by default):
Image Removed

3. Read the API's documentation

4. Try to execute the user story with the simplest flow and then other scenarios that you are interested in

Panel
  • We are using actual schedule for flights but you may feel free to create bookings and issue tickets (please, note that some minor discrepancies between test and production results are still exist)
  • No time limits for testing

5. Give us a feedback through your manager or our technical support by JIRA

6. Ready to production environment?

6.1. Check available scenarios and choose which you're going to use at production environment

6.2. Notify our technical support by JIRA for final testing under the supervision of our technologists

Panel
titleIssue template
  • Summary: Execution of test scenarios // API01-17-000000-0
    • You can find the application number in received email at the first step
  • Description:
    • Agent code: agent
    • Agent name: OOO «Агент»
    • Website: www.site.ru
    • Application: https://requests.s7.ru/api01/17-000000-0
    • Version: v0.45
    • Scenarios:
      • Basic scenario
        • User Story: OW + 1xADT + Transit + S7 flight
        • User Story: RT + 1xADT 1xCHD 1xINF + Transfer + Business Mix + S7 flight
        • User Story: RT + 1xADT + 1CHD + Transfer + Codeshare + BusinessCabin (S7 + CodeShare)
        • User Story: OW + 2xADT 1xCHD 1xINF + Transfer + SPA
      • 3D agreement scenario
        • User Story: OW + 1xADT + Direct + S7 flight

6.3. Proceed test scenarios and attach all created PNRs and ETK numbers as a comment at the issue

6.4. Assign the issue to the "tech_s7" and keep

(warning) Keep all conversation with our technical support and technologists only in comments at the issue
(warning) If you faced any problems, create a new issue in JIRA and link with the issue for final testing

6.5. Once all tests will be passed you can proceed to signing of the contract of EDS

Responsibility of Integrator

Because Agent is going to use an Integrator's solution, we immediately proceed to signing of the contract of EDS and skip final testing under the supervision of our technologists to grant access to production environment

AnchorStep5Step5Step 5: Signing of the contract of EDS

Integrator

Agent with own solution

Agent with Integrator's solution

Responsibility of Agent

Agent will notify you once all the documents have been completed and he will be granted access to the production environment 

1. Contact with your account manager to sign a contract

2. Create a new validator (without transactions history) for our GDS to have ability to execute all basic shopping scenarios

3. If you are interesting in discounts for corporate client you have to enter into 3D agreement between Agent, S7 and corporate client

Panel

As a result Agent ID and Client ID will be defined in 3D agreement. They are required to execute scenarios with 3D Agreement

4. Once all the documents have been completed, your account manager will notify you when you can proceed to the production environment

AnchorStep6Step6Step 6: Access to production environment

Integrator

Agent with own solution

Agent with Integrator's solution

Create a new certificate for production environment (similar as for test environment but the new one — check Step 2 for more details):

  1. Create private key
  2. Create a request for SSL certificate
  3. Fill in the details of the request for SSL certificate
  4. Create a new task with the request of SSL certificate (request_csr) by JIRA
  5. Receive credentials for production environment from our technical support:
    1. a SSL certificate (*.crt file)
    2. personal credentials for basic authentication (login and password)
    3. access parameters for requests (XML block Party)
    4. Client ID and Agent ID (only If you are entered into 3D agreement)
  6. Import SSL certificate and create key store file

Responsibility of Integrator

Notify Integrator once all the documents have been completed and you will be granted access to the production environment 

AnchorStep7Step7Step 7: Maintenance

Integrator

Agent with own solution

Agent with Integrator's solution

1. Choose one of available and tested versions at production environment at the top of the page

2. Use header's parameters for tested selected version (If the parameter is not defined, the default version will be executed):
Image Removed

3. Try to use read operations to check the correctness of your first bookings (read operation) and issued tickets (retrieveTicket operation)

Note

Avoid making mistakes in the production environment due to the penalties specified in the signed contract!
If you are still not sure, don't hesitate to reach our technical support by JIRA

4. Don't forget to check our updates!

Panel
  • Release Notes for new versions of S7 Agent API
  • FAQ for most common issues you can be faced with

Despite the fact that the integrator was developing solution, you are responsible for all mistakes at the production environment

Note

Check the correctness of your first bookings and issued tickets to avoid making mistakes due to the penalties specified in the signed contract!

5. (warning) If validator's stock has less than 10 blanks, you'll receive the error as a result of ticket issuing at the production environment
Ask your manager to increase the validator's stock

Code Block
languagexml
titleError
<ns2:Errors>
         <Error Type="Host Error Response" Code="101" Tag="FETA">TKT092 TICKET ALLOCATION STOPPED-CTC CARRIER</Error>
</ns2:Errors>

6. (warning) If Agent credentials has not been used for 60 days, you'll receive the error as a result of any non-search operation at the production environment
Contact to S7 API support with used Agent credentials to renew them

Code Block
languagexml
titleError
<ns3:Errors>
          <ns3:Error Type="101" ShortText="032 - SI" Code="101"/>
</ns3:Errors>
InfoIf you still have any questions, try to find an answer using our FAQ and documentation or ask for technical support by JIRA or email at api.support@s7.ru