AliExpress API

How to get AliExpress Dropshipping API access

If you want to pull tracking, refunds, and order amounts out of AliExpress automatically, you need the AliExpress Dropshipping API — not the affiliate API, not the open platform's generic endpoints, the actual DS program. The good news is that approval is mechanical: do the steps in order and you get keys. The bad news is that every guide skips the small things that get people rejected or stuck for a week.

This is the no-nonsense version: what to apply for, how to get approved, and exactly what to do the moment your keys land.

What "Dropshipping API access" actually means

AliExpress runs its developer platform through the AliExpress Open Platform. Inside it, the Dropshipping (DS) API is the family of endpoints that let an authorised app read your own placed orders — the order detail, the logistics tracking, the refund state. That is the data your eBay operation lives or dies on.

You are after the endpoints in the aliexpress.ds.* namespace — order detail and tracking calls that return the fields you care about: the AE order ID, order_status, logistics_status, tracking number, and refund signals. Affiliate access will not give you these. Make sure you are applying to the dropshipping track specifically.

The approval steps, in order

1. Create a developer account. Register on the AliExpress Open Platform with a business email. Use the same account identity you actually buy under where possible — mismatches slow review.
2. Create an app. Register a new application and select the Dropshipping solution / API scope. This generates your app_key and app_secret — the two credentials everything else hangs off.
3. Fill in the callback URL. You must register a redirect/callback URL for OAuth. Even if you do not have a slick UI, you need a valid HTTPS endpoint that can receive the authorisation code. Getting this wrong is the single most common reason the OAuth handshake fails later.
4. Request the DS API permissions. Add the dropshipping API group to your app and submit for review. Describe your use case plainly: "syncing my own AliExpress order tracking and refunds into a spreadsheet for my eBay store." Reviewers approve clear, honest, self-use cases quickly.
5. Wait for approval, then bind your buyer account. Once the app is approved, you run the OAuth flow to authorise your actual purchasing account, which gives you an access_token and a refresh_token.

The number one cause of a stalled application is a callback URL that does not resolve over HTTPS. Fix that before you submit, not after.

The moment your keys arrive: do these four things

Approval is the start, not the finish. Before you trust this with real money, lock down the basics:

• Complete the OAuth handshake and store the refresh token. Access tokens expire; the refresh token is what keeps you logged in. Save it securely and build refresh into your flow from day one.
• Test in the sandbox first. Validate your app_key, secret, and OAuth round-trip against test data before you ever hit live orders. We walk through this in how to test your AliExpress sandbox credentials before going live.
• Pull one real order and read the raw fields. Look at order_status and logistics_status with your own eyes so you know what the API actually returns versus what the docs imply.
• Plan for rate limits. You will hit "Api access frequency exceeds the limit" during a busy batch. Build retry-with-backoff before it bites you mid-sync.

The catch nobody warns you about

Getting keys is the easy 20%. The hard 80% is everything that comes after, because the AE Dropshipping API is full of sharp edges that only show up at volume:

• carrier_name is frequently wrong, so you have to resolve the real courier from the tracking-ID prefix yourself.
• Order IDs come in 16-digit and 19-digit formats with subtly different responses, so a naive parser silently drops orders.
• One eBay sale can map to several AE orders, so a single tracking lookup is not enough.
• Refunds hide across issue_status, the gmt_refund_* timestamps, and child orders — not in one tidy boolean.

Each of those is solvable. Solving all of them, keeping the token refreshed, retrying around rate limits, and writing the result cleanly into a sheet is a real engineering project — one you would be rebuilding instead of selling.

Or skip the build entirely

This is exactly the gap Fetch Order Tracking closes. It talks to the AliExpress Dropshipping API for you, handles the OAuth refresh, the rate-limit backoff, the carrier mapping, the multi-order matching, and the multi-field refund detection — then writes tracking ID, carrier, status, estimated delivery date, AE order amount, refund state, a delivery-proof link, and the AE order date straight into the Google Sheet you already own. It pairs with eBay's Finances API too, so your earnings reflect true net after fees.

If you want the API access for the learning, get it — the steps above are everything you need. If you want the outcome without maintaining a token-refresh loop forever, start with Fetch Order Tracking instead and point it at your sheet. Either way, once your keys are live, the next thing to read is why tracking automation pays for itself in the first week.

Frequently asked questions

What is the difference between the AliExpress affiliate API and the Dropshipping API?

The affiliate API is built for promoting products and earning commissions, so it exposes product and link data, not your own purchase records. The Dropshipping (DS) API is the family of aliexpress.ds.* endpoints that let an authorised app read the orders you actually placed, including order detail, logistics tracking, and refund state. For an eBay operation you need the DS track specifically, because only it returns the order_status, logistics_status, tracking number, and refund signals your sheet depends on.

How long does AliExpress Dropshipping API approval take?

Approval is usually quick when your application is clean, because reviewers favour clear, honest, self-use cases. Describe your use case plainly, something like syncing my own AliExpress order tracking and refunds into a spreadsheet for my eBay store. The thing that drags it out is almost always a callback URL that does not resolve over HTTPS, so fix that before you submit rather than after.

Do I have to build everything myself once I have API access?

No. Getting keys is the easy 20 percent; the hard part is the carrier_name field being wrong, the 16-digit versus 19-digit order-ID formats, one eBay sale mapping to several AE orders, and refunds hiding across multiple fields. Fetch Order Tracking already handles the OAuth refresh, rate-limit backoff, carrier mapping, multi-order matching, and multi-field refund detection, then writes the result into your Google Sheet, so you can have the outcome without maintaining a token-refresh loop forever.

Related guides

• How to test your AliExpress sandbox credentials before going live
• A practical guide to AE rate-limit retry-with-backoff
• Handling the 16-digit vs 19-digit AliExpress Order ID gotcha

---