Journease (Rhenus data)
Version 0.0.2
Check out the API docs here for more information
Set up
To get set up with the Journease (Rhenus data) connector you will need
- Domain Name
- API Key
Please speak with your Journease representative if you need support with obtaining these values.
Features
Feature | Support | Notes |
---|---|---|
Backfill | 🟢 | Custom backfill |
Incremental | 🟢 | Supported on some reports, see below. |
API reliability | 🟠 | Occasional time-out issues from the API when fetching data |
Reports detail
Report name
When setting up both reports above you will need the relevant "ReportName" that the Report endpoint can accept (e.g.
MyCompanyNameTrackingWithPIDs
).For the Jobs extract, please ensure this is the report that returns the bookings where each entity in the response has the
WebBookingID
included.If unclear, please ask your Journease representatives for the name of the report, as they will have visibility on this.
Limitations
Timeouts from the API
On some extract runs you might encounter an API time-out error. Please re-run your report later.
Jobs
report durationOn longer backfill settings this extract can take several hours to complete.
Incremental logic
The logic for the incremental runs for the
Report (data-retrieval query)
report is based on theENTRY_DATE_TIME
field of trackings, meaning you will only fetch new bookings when new trackings are added.
The extracts anticipate the Report you are setting up for the
/Report
endpoint will acceptStartDate
andEndDate
parameters in its request body."Parameters": [ { "Name": "StartDate", "Value": "2024-05-19 23:59:59", "DataType": "string" }, { "Name": "EndDate", "Value": "2024-05-20 23:59:59", "DataType": "string" } ]
In case other setup is needed for you report, please reach out to your CS representative so an extension to the connector can be built.
Updated 6 months ago