Below you will find descriptions of common terms used in B2B API:

  1. Company - this is a basic B2B API structure representing the company to which the user belongs to.

  2. Company Account - each Company may consist of multiple Company Accounts which represent different departments within the Company. They may be associated with different Discount Categories, Ticket Groups

  3. User - users belong to Company Accounts. Having such user accounts is needed to be able to book tickets with B2B API

  4. Discount category - this represents a set of Discounts available for a given Company. If more than one is available then B2B API user will be able to select which Discount Category should be applied to a booking. In case of a booking made on behalf of other clients (see Travel Management Company) both Client and Discount Category will have to be selected at the initial step.

  5. Travel Management Company (TMC) - this is a company who manages bookings for other Companies' Accounts (ie. Clients). In case of TMC, its user may book tickets for himself (as a standard B2B user) and for his clients' users

  6. Questions - survey that might need to be answered by B2B API user before submitting a booking

  7. Client - Client is related to TMC which manages its bookings. Client can either be a full Company Account having its own Discount Categories & Tickets or a standard Client using the same settings from as the TMC itself.

  8. Tokens - there are two tokens used during the booking flow - authorisation token and order token. The first authenticates the B2B API user and the second represents the order that is being created during the booking process

  9. Payments - payments on the current version of the B2B API are handled through credit accounts containing "prepaid" amounts of money, so they are processed in the background without the need to use credit cards or other payment methods.