Familiarise yourself with the documentation, which contains all details about the service's functionality, data model, recommended listing and checkout flows and limitations.
Access our API documentation. +
If this hasn't already happened, for instance as part of an earlier exchange, get in touch to request an account on our development environment. +
We recommend utilising the published WADL + XSD or Swagger specification documents to quickly generate an API client in your application's native or preferred programming language.
Establish the connectivity between your project and the Livn API by making calls on the development endpoint, giving you a sandbox environment to retrieve inventory data for a wide range of products and make test bookings and cancellations without incurring any cost.
When you have completed your implementation, please contact firstname.lastname@example.org to have your connection certified by our team, ensuring that the integration is performing optimally for your specific requirements without causing excessive load on the shared systems, and to identify points that might be improved.
More details on certification/compliance test +
We do not have any strict protocol to follow for this final compliance test, as every client's implementation tends to take a slightly different approach to accessing inventory for imports and/or caching, checkout, cancellations, reporting etc.
We found all our users to be consuming the API in a somewhat different way, so forcing everybody to follow a scripted sequence of API calls, will not help us understand how it is you plan to use the API in production, nor allow us to identify potential problems.
Instead we will ask you to please run your API client through your application's normal expected usage patterns in production, but still using your test account on the development server: product search, departures listings, checkout and cancellation calls, any kind of caching you intend to do, in short anything you intend to later use in production.
During this test run we will enable fine grained request and response logging for your account. When you believe to have covered every aspect of the connection, we would analyse and evaluate the logs and generated data, looking for thing such as e.g. duplicate/redundant API calls, or malformed data that doesn't get captured by our server side validation, in short anything out of the ordinary, that we believe can be optimised.
Once you and our team are confident that the connection is running optimally, you will receive a set of production credentials to the live API endpoint. Both the development and production environments operate on the same codebase and the transition to go live should require no more than a simple reconfiguration of the accessed API endpoint base URL.
If at any stage of this development process you have questions or hit a road block please feel free to get in touch with our dedicated technical API support.