On day one, we made an important architectural decision. Our client-facing interface should be built on top of our own APIs. This decision means that every single feature and capability we offer in the LiveRail platform has to be available in our API before we can add it to our UI. This strategy means that our clients have the same incredible, deep-level access to LiveRail’s core platform as we do.
Our clients can use this powerful tool to build their own software, interfaces, reporting tools or even entire UI platform, on top of the LiveRail infrastructure stack. Whether the client wants to build its own exchange-bidder, a custom ad server, or simple reporting dashboard; LiveRail’s API platform toolset gives our clients an incredible range of possibilities.
Full, up-to-date LiveRail API documentation, including the RTB API methods, is available online at http://test.api.liverail.com/. You need a valid LiveRail username and password in order to access this online documentation. This web application allows you test various methods and parameters in real time, access quick help, and view API responses. A LiveRail API client can connect to the LiveRail API through standard HTTP protocol. A client must send its request using HTTP POST. The LiveRail API will always return an XML response.