Download a collection
Every collection here is preconfigured to call the mock environment with no credentials. Re-download after major content updates.API reference
Every endpoint of this portal and every pricing API use case, as ready-to-run requests, in one folder per API, seven in all. The mock environment returns realistic but fictitious data, so you can explore every request and response before you receive your access details.D-EDGE Docs: API reference
Postman collection, version 1.1
D-EDGE Docs: API reference
Insomnia collection, version 1.1
Before you run it
Before you run it
Four of the seven folders need more than a Send.Run the Booking Engine, Gift Shop, and CRM folders in order. Their requests chain: each one reuses the identifiers the previous one returned, so a request opened on its own has nothing to work with. On the CRM API, once the credentials are set, both tools request and refresh the OAuth 2.0 token themselves from
crmApi.tokenUrl, so there is no token request to run.Decide what the Channel Manager folder talks to. There the collection plays D-EDGE, so its requests target channelManagerApi.yourBaseUrl, the mock by default and your own server once you set it. Push bookings is the one call you make to D-EDGE rather than the other way round, and its credentials arrive later than the rest, during certification.In Postman, the variables prefixed with _ fill themselves as you run those three folders in order: leave them empty.Variables to fill
Variables to fill
You only need these to call the live API: against the mock the collection runs on the values it already carries. D-EDGE delivers your credentials after the partnership agreement, during the build step of the integration journey.
Versions
Versions
Version 1.1
The Best Price mock now answers like the updated API. Each entry of Rates, Rooms, and Hotels (Arrivals) carries the
behaviour it was computed for. Rates and Rooms entries also carry availability. The Hotels (Arrivals) request now describes its result as the best price per hotel over a date range.Version 1.0
Six CRM API requests join both files: compute merge confidence, read a task, unmerge a guest, create a segment, update a segment, and browse bookings. The merge and the confidence computation chain into the task read, which follows them until they end.
Version 0.5
The collection is renamed D-EDGE Docs: API reference, and carries its version number from now on:
info.version in Postman, the workspace description in Insomnia.Version 0.4
The Channel Manager API folder joins both files: thirteen requests reproducing the examples of the reference pages, the collection playing D-EDGE.
Version 0.3
Every Gift Shop endpoint joins both files as a ready-to-run request on the mock environment.
Version 0.2
Every Booking Engine endpoint joins both files, in funnel order: each request reuses the identifiers returned by the previous one.
Version 0.1
Both files call the mock environment by default, so the Best Price, Daily Rates, and Quotation requests run with no credentials.
Channel Manager API test scenarios
The test scenarios D-EDGE runs to certify a Channel Manager API integration, as ready-to-send requests in ten folders. There is one folder per interface you host, a refusal folder next to three of them, and one per price model. The collection plays D-EDGE, calls those four endpoints, and checks the response each scenario expects.D-EDGE Docs: Channel Manager API test scenarios
Postman collection, version 1.0
D-EDGE Docs: Channel Manager API test scenarios
Insomnia collection, version 1.0
Before you run it
Before you run it
Out of the box this collection can run entirely green and prove nothing: two settings decide whether a result means anything.Point it at your own server. Fresh from the import the four URL variables target the mock environment, which answers success to everything, including the three refusal folders that are meant to fail. Set them to your test environment before you read any result.Give it your room and rate codes. Run Get hotel and read your own response: it declares your room types and your rates, and every Planning updates message the collection sends addresses them by those codes. Copy the ones you want to certify with into the variables below. Your test hotel needs at least three room types and three rates in total, one room carrying at least two rates, because the scenarios reference that shape.The collection does not read those codes back from your response on purpose: a rule that took whichever room came first would run green against the wrong shape.
Variables to fill
Variables to fill
Everything below except
mockApiKey describes your own platform. The values shipped with the collection are the ones the mock uses.How to run it
How to run it
1
Run the folders in order
Run the ten folders top to bottom with the Collection Runner in Postman or the Runner in Insomnia, or send the requests one by one. Among the three price folders, run the one your Get hotel response declares and leave the two others. Leave out the scenarios your platform does not support. Each one that depends on a capability carries a marker on the test scenarios page, and your questionnaire is where you declared which ones you meet.
2
Read the results
Each request carries the four checks every response must pass, named after the scenario it plays:
PU-F3 answers 200 OK, PU-F3 answers within 5 s, PU-F3 returns <failure> of type 4. A red line points at the row below to read. Fix, run again, and hand over your endpoints when everything is green against your test environment.Versions
Versions
Version 1.0
First version: the phase one scenarios of the Test scenarios page, 63 requests in ten folders, four checks per request, dates in two months you choose.
How to import
Every collection on this page imports the same way and answers from the mock environment until you change its variables. Re-import the downloaded file at any time to return to the mock configuration.- Postman
- Insomnia
1
Import the file
In Postman, go to File > Import and add the JSON file.
2
Run a request
Open any request and click Send. The collection calls the mock environment by default, so you get a response with no further setup.
3
Fill the variables
Select the collection, go to the Variables tab, and fill what the Variables to fill accordion of that collection lists above. Click Save.