Skip to main content

Integrating SparkPost

Capabilities

DataGrail's SparkPost Integration provides the following capabilities:

ProductCapability
Request Manager
Request TypesAccess, Deletion, Do Not Sell/Share
Identifier CategoriesEmail
Foundation ConnectionsTransactional Mailer

Before You Start

To successfully configure this integration, please ensure you have sufficient privileges:

  • DataGrail User Role: Super Admin, Connections Manager
  • SparkPost User Role: Admin

Create a SparkPost API Key

  1. Log in to SparkPost.
  2. In the left-hand menu, select Configurations and then API Keys.
  3. In the top-right, select Create API Key.
  4. In the new page that opens, configure the new API key with the following information:
API Key Configuration

API Key Name: DataGrail (You can use any value)

Subaccount: leave blank

Allowed IPs: leave blank

API Permissions: Select the following permissions depending on your integration needs:

Required for All Integrations

  • Account: Read
  • Suppression Lists: Read/Write

Access

  • Events Search: Read-only
  • Recipient Lists: Read/Write

Deletion

  • Data Privacy: Read/Write
  • Recipient Lists: Read/Write

Do Not Sell/Share

  • Data Privacy: Read/Write

Transactional Mailer

  • Transmissions: Read/Write
  1. Select Create API Key.
  2. Copy your API Key and store it in a temporary, secure location.

Configure SparkPost as a Transactional Mailer

This configuration step is required if you are going to use the SparkPost service as your DataGrail transaction mailer.

  1. Go to Configuration, then Domains and select Add a Domain.
  2. Select the Sending Domain option, define a Subaccount Assignment and select Save and Continue.
  3. Add the required DNS records to verify your domain.
  4. Select Verify Domain.
  5. Confirm that the API Key create in the previous step has the Transmissions: Read/Write permission. If not, update the API key.
  6. If you want to support Bounce Domains, follow the Bounce Domain Configuration below.
Bounce Domain Configuration
  • Navigate to Configuration, then Domains and select the Bounce Domains option.
  • Configure and select the bounce domain to fill the Return Path:
    • The domain of the Return Path address must be a CNAME-verified sending domain. The local part of the Return Path address will be overwritten by SparkPost.
    • For Enterprise accounts, the Return Path may be any valid email address and the local part in the Return Path will not be overwritten by SparkPost.

Connect to DataGrail

  1. Return to DataGrail.
  2. Enter the API Key obtained from the first step.
  3. Select the Account Location in the dropdown.
  4. If you are using SparkPost as a Transactional Mailer and have configured Bounce Domains, enter the Return Path used above.
  5. Select Configure Integration.

Next Steps

Now that you've successfully connected the integration, check out the following resources:

Troubleshooting

If you are unable to successfully connect the integration, review these common troubleshooting steps:

Ensure Required Permissions Are Granted on API Keys/Resources

DataGrail checks required permissions and scopes on API keys/resources used by each integration. If all necessary permissions are not granted, new connections will fail.

Review Required Account Types and User Roles

If users do not have the necessary permissions or the minimum required user role in the connecting system, the connection to DataGrail will fail. Additionally, connections will fail if your account type does not match the one required by the integration.

See Before You Start to review these requirements.

Technical Details

The SparkPost integration uses the V1 API:
Access TypeSynchronous
Deletion TypeAsynchronous (Whole Record)

API Documentation

Learn more about this API implementation and DataGrail functionality in our API Integration Documentation.

 

Need help?
If you have any questions, please reach out to your dedicated CSM 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.