# AfterShip

This Integration requires Fides Cloud or Fides Enterprise. For more information, [talk to our solutions team. (opens in a new tab)](/content/speak-with-us?utm_source=docs-site/index.html)

[AfterShip (opens in a new tab)](https://www.aftership.com/) simplifies eCommerce shipping by integrating with multiple selling platforms and providing real-time tracking for all your shipments and orders in one centralized dashboard. We support two types of integrations for AfterShip: AfterShip Tracking, which allows for access requests of tracking objects, and AfterShip Commerce, which allows for access requests of orders and requires additional configuration.

## Prerequisites

### AfterShip Tracking

_Access Only_

In order to [integrate](/content/docs/integrations/index.html) with AfterShip Tracking, you'll need to collect the following information:

| Name          | Description                                                 |
|---------------|-------------------------------------------------------------|
| **Domain\*** | The AfterShip Tracking API (default: api.aftership.com)    |
| **API key\***| Your API key. Follow AfterShip Tracking's docs to [obtain your API key (opens in a new tab)](https://www.aftership.com/docs/tracking/quickstart/api-quick-start) |

Your AfterShip API key will need the following scopes: `trackings.read`

### AfterShip Commerce

_Access Only_

This integration requires an [Enterprise (opens in a new tab)](https://www.aftership.com/pricing) plan for AfterShip.

In order to [integrate](/content/docs/integrations/index.html) with AfterShip Commerce, you'll need to collect the following information:

An owned database must be configured to store AfterShip Commerce data for privacy request processing. To learn how to integrate with a database, please see our guide for [integrating with databases](/content/docs/integrations/databases/index.html).

| Name                      | Description                                                   |
|---------------------------|---------------------------------------------------------------|
| **Domain\***              | The AfterShip Commerce API (default: api.aftership.com)    |
| **API key\***            | Your API key. Follow AfterShip Commerce's docs to [obtain your API key (opens in a new tab)](https://www.aftership.com/docs/tracking/quickstart/api-quick-start) |
| **AfterShip order ID\***  | The location in your owned database where you store AfterShip order's source_id in relation to user emails, in the following format: `dataset.collection.field` |

Your AfterShip API key will need the following scopes: `orders.read`, and `stores.read`

The AfterShip Commerce integration includes access to personal information stored within Returns and Coverage objects, as these are associated with existing orders. However, it does not cover personal information from gift returns or warranties that were created independently of AfterShip orders.

You may confirm your connection is working using the **Test connection** button, if desired.

### Creating an Email Integration

Due to the nature of the many products AfterShip offers, you will need to create an email integration for erasure request processing to ensure complete data deletion.

Follow our guide for [creating a generic email integration](/content/docs/integrations/email-integrations/generic-erasure-emails/index.html), and use the following values:

| Field                      | Value                                                   |
|---------------------------|--------------------------------------------------------|
| **Recipient Email Address\*** | [privacy@aftership.com](mailto:privacy@aftership.com) |

## Integrating with AfterShip

To integrate an existing system with AfterShip:

1. Navigate to **Data map** → **View Systems** and choose the system that you want to connect.
2. Click on the **Integrations** tab.
3. Pick the vendor or system type that you want to integrate with from the **Connection type** drop-down menu.
4. Complete the required fields for the integration and click **Save**.

To learn more, please see our guide for [Managing Integrations](/content/docs/integrations/guides/manage-integrations/index.html).

## Technical detail

Fides utilizes _API endpoints_ to access the _API service_ for a SaaS application. An _API service_ is the programmatic interface through which Fides can query and update data within an application to access, rectify, or delete personal information. Each SaaS tool will have a unique set of endpoints to enable privacy functions.

### AfterShip Endpoints

In the table below, you can find which endpoints are used for each type of privacy function. Clicking on the endpoint will take you to the documentation for that endpoint.

| Privacy function                      | Endpoint                                             | Description                             |
|-------------------------------------|-----------------------------------------------------|-----------------------------------------|
| **Access Requests (Tracking)**      | [Trackings (opens in a new tab)](https://www.aftership.com/docs/tracking/jh865r66gc6hi-get-trackings) | Returns information about Trackings.    |
| **Access Requests (Commerce)**      | [Stores (opens in a new tab)](https://www.aftership.com/docs/commerce/yc24p1srfyqiv-get-stores) | Returns information about Stores.       |
| **Access Requests (Commerce)**      | [Orders (opens in a new tab)](https://www.aftership.com/docs/commerce/kr3dy6e5ma49n-get-orders) | Returns information about Orders.       |