Skip to main content
This guide walks you through your first call to the Daily Rates API. You will set up OAuth 1.0 signing, send a request to the Per day endpoint, and inspect the response.
No credentials yet? Import the API collections and run any request against the mock environment straight away, with no credentials. Add your OAuth 1.0 credentials when you are ready to call the live API.

Prerequisites

Get the following from D-EDGE before starting:
  • OAuth 1.0 credentials: consumer key, consumer secret, token key, and token secret.
  • API base URL: the base URL for your environment.
  • Hotel ID and Group ID: the hotel you want to query.
All are delivered during the build step of your integration journey, after the partnership agreement.
1

Install an OAuth 1.0 library

Use a battle-tested library to handle the signing. Skip this step if you only use cURL.
2

Make your first call

Send a POST to the Per day endpoint with a minimal request body. The request needs four pieces: a date range, a guest configuration, a filter selecting which hotel and group to query, and a layout describing which fields you want back. The full schema is documented in the Reference.
3

Inspect the response

A successful response returns 200 OK with a JSON object grouped by rate plan, then by hotel, then by entities. Each entity carries the daily breakdown for one room and rate combination over your date range. Fields that vary by day are returned as a list of { value, start, end } segments, so a single price block covers the full window when nothing changes. start is the first day the value covers and end is exclusive (the first day it no longer covers), so consecutive segments share their boundary date.
See the response schema for the full structure.

Common issues

Next steps

Reference

Endpoint specification, parameters, and response schema.

Use cases

Build nightly rate refreshes and revenue manager dashboards.

Best practices

Patterns to build responsibly and run reliably at scale.