Aftership
Version 0.0.3
Checkout theΒ Aftership API docs for more information
Set up
To use the Aftership connector, you need to generate an API Key β Generate AfterShip API Key | AfterShip
This can be managed through the API settings page.
Features
Feature | Support | Notes |
---|---|---|
Backfill | β | Last 120 Days |
Incremental | β | Trackings, Trackings (legacy) |
Custom backfill | β | |
API reliability | π’ | Reliable API |
Reports detail
β¬οΈ Report | π Incremental key | π Primary key | π Link to API endpoint |
---|---|---|---|
Trackings (legacy) | UPDATED_AT | ID | Get trackings (legacy) |
Trackings | UPDATED_AT | ID | Get trackings |
Trackings (by created time) | N/A | ID | Get trackings |
Limitations
- Aftership only holds data for the last 120 days.
Trackings (legacy)
report relies on the Tracking APIβs legacy version which will be deprecated on October 9th, 2025. More info available here
API irregular behaviour
As of April 4th, 2025, the API exhibits inconsistent behavior where it does not reliably honor the
updated_at_max
andupdated_at_min query
parameters.In some cases, records are returned even if their
updated_at
timestamp is beyond theupdated_at_max
value specified in the request. This can lead to missed data during subsequent incremental loads.Recommendation:
Until the issue is resolved on the API side, consider running full backfills when generating reports.
You may also want to combine data from both the
Trackings
andTrackings (by created time)
reports, and deduplicate as necessary to ensure data completeness.
Updated 12 days ago