Aftership
Version
This integration utilizes the Aftership Aftership Tracking API 2025-07.
Base URL
The base URL used for all Aftership API endpoints:https://api.aftership.com/tracking/2025-07
Endpoints Utilized
DataGrail uses the following endpoints to authorize and test the connection:
Authentication & Authorization
The DataGrail Aftership integration connects using API Key authentication which requires an API Key.
Limits
Limits in Aftership 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 Aftership integration provides Synchronous Access capabilities for the following supported identifier categories: Email and Phone Number.Data Interactions
For Access requests, DataGrail will take the following actions:
- Search trackings using configured identifiers.
Endpoints Utilized
Deletion
DataGrail's Aftership integration provides Synchronous Deletion capabilities for the following supported identifier categories: Email and Phone Number.Data Interactions
For Deletion requests, DataGrail will take the following actions:
- Update tracking to anonymize data subject PII.
Endpoints Utilized
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.