Aftership
Aftership ETL connector for data replication
Features | Details |
Release Status | Released |
Source API Version | v2 |
Table Selection | Yes |
Column Selection | Yes |
Edit Integration | Yes |
Replication Type Selection | No |
Authentication Parameters | Aftership API Key |
Replication Type | Key based Replication |
Replication Key | DATE |
Suggested Replication Frequency | 24 hrs |
Tables/APIs Supported | |
Couriers | Trackings |
- 1.Signin to Daton
- 2.Select Aftership from Integrations page
- 3.Provide Integration Name Replication Frequency and History. Integration name would be used in creating tables for the integration and cannot be changed later
- 4.Provide your Aftership API Key.
- 5.After providing the API Key Daton will periodically extract data from Aftership.
- 6.Post successful authentication you will be prompted to choose from the list of available tables
- 7.Then select all required fields for each table
- 8.Submit the integration.
- 1.Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
- 2.Users would be able to edit/pause/re-activate/delete integration anytime
- 3.Users can view job status and process logs from the integration details page by clicking on the integration name from the active list
Couriers
Purpose: Return a list of all couriers.
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
slug | STRING |
name | STRING |
phone | STRING |
other_name | STRING |
web_url | STRING |
required_fields | STRING |
optional_fields | STRING |
default_language | STRING |
support_languages | STRING |
service_from_country_iso3 | STRING |
Trackings
Purpose:Get tracking results of multiple trackings.
Replication: Key-Based Replication
Replication Key: lastRunDate
Fields
Name | Target Datatype |
order_id | STRING |
tag | STRING |
title | STRING |
checkpoints | RECORD |
Last modified 1mo ago