Reach

This documentation for the Reach integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Reach, visit our connection instructions.

Version

This integration utilizes the Reach Checkout API.

Base URL

The base URL used for all Reach API endpoints:

https://checkout.rch.how/v2.22

---

Authentication & Authorization

The DataGrail Reach integration connects using Hash-based Message Authentication Code (HMAC) signature authentication which requires a Secret and Merchant ID.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Reach API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
POST	/query	Validate credentials

Limits

Limits in Reach are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Reach integration provides Synchronous Access capabilities for the following supported identifier category: Order ID.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search for personal data using the Order ID.
2. If a match is found, DataGrail will extract the following objects:

Match Found

• Consignee
• Consumer
• Payment

Endpoints Utilized

Method	Endpoint	Purpose	Docs
POST	/query	Search personal data by Order ID

---