Not implemented yet. Will be implemented using some kind of token system to prevent denial of service attacks.
Information about current state between client and server is not stored in the server. Client sends all necessary information in each request.
Most of the resources from transport providers doesn't have a unique identifier. So, we have to use the combination of the information to identify the resource. For example, an offer could be identified by the combination of information about departure & arrival locations, time, number of passengers etc.
IDs could be used to identify entities within request/response payloads to avoid duplication of the same entity in the payload.
Documentation will specify whether an ID is relative or not.
Hypothetical example:
const payload = {
passengers: [
{
id: 1,
name: "John Doe",
age: 30
},
{
id: 2,
name: "Jane Doe",
age: 25
}
],
offers: [
{
legs: [
{
resources: [
{
passengerId: 1,
type: 'meal'
},
{
passengerId: 1,
type: 'extra-luggage'
},
{
passengerId: 2,
type: 'meal'
}
]
}
]
}
]
}