Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

Phaedon Tally

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

Version

This integration utilizes the Phaedon Tally REST API v3.

Base URL

The base URL used for all Phaedon Tally API endpoints:
https://api.{tenant_id}.loyaltyservices.io/api/v3

Endpoints Utilized

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


Authentication & Authorization

The DataGrail Phaedon Tally integration connects using OAuth 2.0 Client Credentials authentication which requires the following: Client ID, Client Secret, and Tenant ID.

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

Authentication Details

DataGrail posts the Client ID and Client Secret directly to the Okta authorization server to obtain a short-lived bearer token (1-hour TTL), bypassing user interaction. The token is refreshed automatically as needed, and all API calls include it in the Authorization: Bearer header.


Limits

Limits in Phaedon Tally 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 Phaedon Tally integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

  1. Find members by querying the /members endpoint using the subject's email address as the search identifier.
  2. Return all available member profile data including addresses, emails, phones, payment card accounts, aliases, currencies, preferences, and authorized members.

Endpoints Utilized


Deletion

DataGrail's Phaedon Tally integration provides Synchronous Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

  1. Find the member record using the subject's email address.
  2. Send a scrub request to the /members/{member_id}?scrub=true endpoint to permanently erase the member's personal data.
  3. A 404 response indicates the member no longer exists and is treated as a successful deletion.

Endpoints Utilized


 

Need help?
If you have any questions, please reach out to your dedicated Account Manager or contact us at support@datagrail.io.

Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.