Agent Booking APIs are moving
Rental Car Manager is embarking on a major infrastructure
upgrade, and part of this involves moving our systems off our legacy
servers.
All Booking Agencies will be required
to make some minor changes to use a new API URL in order for them to continue
making live rates requests and bookings via the API.
Note: This article is for Agent developers. If you are a developer for a rental car company's own website please see this article.
Jump to:
The changes are quite straightforward:
If you are using API V3.2:
Change
1: API URL is changing to https://apis.rentalcarmanager.com/agent/booking/v3.2/
Note the change in both the domain (no
longer using secure.rentalcarmanager.com) and the structure following it: /api/3.2/ in URL is changing to /agent/booking/v3.2/
Change
2: You must do one of (a) or (b) below, whichever is easier:
(a) Add a request header with name =
“Ocp-Apim-Subscription-Key” and value = (your api key).
E.g. client.Headers.Add("Ocp-Apim-Subscription-Key", varAPIKey); or
(b) add ?apikey=<key> to the end of the
URL. The value of this key is the same as your existing key(s). The key will
now be on the URL twice, as per sample below.
Before: https://<old_server_domain>/api/3.2/<key>
After: https://apis.rentalcarmanager.com/agent/booking/v3.2/<key>?apikey=<key>
E.g.: https://apis.rentalcarmanager.com/agent/booking/v3.2/ABCDEF?apikey=ABCDEF
All
other data inputs and outputs should remain unchanged.
If you are using API v3.1:
Change
1: API URL is changing to https://apis.rentalcarmanager.com/agent/booking/v3.1/
Note the change in both the domain (no
longer using secure.rentalcarmanager.com) and the structure following it: /api/3.1/ in URL is changing to /agent/booking/v3.1/
Change
2: You must do one of (a) or (b) below, whichever is easier:
(a) Add a request header with name =
“Ocp-Apim-Subscription-Key” and value = (your api key).
E.g. client.Headers.Add("Ocp-Apim-Subscription-Key", varAPIKey); or
(b) add apikey=<key> as an extra
querystring parameter to the end of the URL. The value of this key is the same
as your existing key(s). The key will now be on the URL twice, as per sample
below.
Before: https://<old_server_domain>/api/3.1/<key>/step2/1/1/08_08_2021/09_00/1/15_08_2021/0900/15/1/-
After: https://apis.rentalcarmanager.com/agent/booking/v3.1/<key>/step2/1/1/08_08_2021/09_00/1/15_08_2021/0900/15/1/-?apikey=<key>
Check:
If using a hashed Signature/Signed Request, check that your Signature (the
hashed value) is derived using the URL portion that begins “/agent/booking/v3.1/…etc…”,
rather than previously “/api/3.1/…etc”
All
other data inputs and outputs should remain unchanged.
If you are using API v2:
We will be contacting you with further instructions. Please contact us if you'd like to get a head start on the migration: support@rentalcarmanager.com
When is this required?
Please make this change as soon as possible. In
mid-November we will be moving the APIs off the server “secure.rentalcarmanager.com”.
At that time, we will use an internal redirection to forward API requests still
being received on the old server to the new endpoint. Please note that
there may be a performance hit due to this redirection. The redirection
will be in place until the end of this year, at which point the server will be
retired and the current API will cease. We are moving our other servers “https://secure2.rentalcarmanager.com/”,
“https://secure.rentalcarmanager.com.au/”,
and “https://secure20.rentalcarmanager.com.au/”
over the next 4 months so these changes can be made for any other RCM partners
at the same time.
Troubleshooting
Please get in touch with us ASAP if you have any questions
or issues. We are happy to help you through this process. Feel free
to email us directly at support@rentalcarmanager.com
Access Denied
If you receive an error Http Status 401 or "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." please try the following:
1. Make sure you've included apikey=XYZ on your querystring (where XYZ is your key).
2. Make sure the apikey value is not encoded in any way. For e.g. if you have a "=" in your key, you must use "=" and not "%3D". If this is not possible, please see Alternative Subscription Key method below.
3. In the case of v3.2, make sure you are performing a POST request with the JSON data in the body.
Categories 