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.

Simon Data

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

Version

This integration utilizes the Simon Data Privacy API v1.

Base URL

The base URL used for all Simon Data API endpoints:
https://api.simondata.com/v1

Endpoints Utilized

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


Authentication & Authorization

The DataGrail Simon Data integration connects using token authentication which requires an Access Token.

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

Limits

Limits in Simon Data 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 Simon Data integration provides Asynchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

  1. Submit a request to export data for the contact using configured identifiers.
  2. Retrieve the status of a request to export data for one or more contacts.
  3. Download the requested personal data.

Endpoints Utilized


Deletion

DataGrail's Simon Data integration provides Asynchronous (Whole Record) Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

  1. Submit a deletion request for the contact using configured identifiers.
  2. Retrieve the status of a request to delete data for one or more contacts.

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.