Ending support of JSON::API

• Identifier field id used to be a string and is now an integer.
• Standard JSON::API pagination is not supported anymore (see “Pagination” below), which means the response won’t include links attribute anymore.
• Attributes won’t be nested into a data property anymore.
• relationships attributes won’t be included anymore.

Pagination

When a response contains a paginated list, it will include a specific next header which value is the URL to follow to retrieve the next page.

Example:

Link = <http://api-eu.getaround.com/owner/v1/unavailabilities?end_date=2022-08-30T01%3A52%3A00.000Z&page=2&per_page=2&start_date=2022-08-01T01%3A52%3A00.000Z>; rel="next"

Pagination is handled with the two following URL parameters:

• page: page number, integer, starting at 1
• per_page: number of items provided per page, integer, 25 by default

Resource trip renaming

trip was renamed in rental to match our product naming. The following endpoints are affected:

• GET /owner/v1/invoices
• GET /owner/v1/trips/:trip_id/invoices
  • Changed to GET /owner/v1/rentals/:rental_id/invoices
• GET /owner/v1/trips
  • Changed to GET /owner/v1/rentals
• GET /owner/v1/trips/:id
  • Changed to GET /owner/v1/rentals/:id
• GET /owner/v1/checkins
  • Changed trip_id to rental_id