The Temu Order Fetcher connects to your shop using three values from Temu's own open platform — an app key, an app secret and an access token — plus one thing most people miss: your server's IP has to be registered with Temu. Here's every step, in order.
Before you start
Log in to Temu Seller Central with your normal seller account, open Apps and services → Manage your apps, and click Add a self-developed app. Only one self-developed app is allowed per account, and using the API for your own shop is free.
Adding the app opens Temu's Partner Platform. Fill in the app information — including the order and logistics / shipping permissions the Fetcher needs — then complete the two questionnaires Temu requires: a Compliance and a Security assessment. You'll be asked where your company is based, which cloud provider you use, and for an IP white list — which must be a fixed EU or UK server IP (see step 5).
Once both stages are approved, your app name,
app key and app secret appear on the
app's management page — copy the key and secret. Note the app's
Request URL too (EU sellers:
openapi-b-eu.temu.com); the Fetcher uses it for the Europe
region.
Authorise the app for your own shop. Temu then issues an access token — copy it. This is the third of the three values the Fetcher needs, alongside the app key and app secret.
The IP white list you filled in during the assessment must be your server's outbound public IP, and it has to be an EU or UK address. The Fetcher's Connection page detects and shows you this exact IP in a copy-ready box.
Open the Fetcher's Connection page, paste the app key, app secret and access token, choose your region (Europe for UK/EU sellers), save, and click Test connection. The test makes one tiny order-list call and tells you in plain English whether the problem — if any — is the credentials, the IP allowlist, or a missing scope.
If the test fails
Re-copy the app key, secret and token letter-by-letter — a stray space at the start or end is the most common cause. Re-issue the access token if in doubt.
Add the exact IP the Connection page shows to Temu's allowlist, then wait a few minutes for Temu to apply it and test again.
Enable the order-query and logistics permissions on the app. A permission error always means a scope isn't switched on.
FAQ
Usually a few days. It isn't always instant, and not every account is approved on the first try — which is exactly why we suggest getting your keys before you buy the Fetcher.
No — using the API for your own shop is free. You're only paying once for the Fetcher itself (£199 + VAT), never per order or per call.
Temu only accepts API calls from server IPs you've registered in advance. If your hosting sends traffic from changing IPs, Temu rejects the calls. A basic VPS or any dedicated-IP hosting solves it. See step 5.
No. Your keys come from your own seller account and are stored in your own database or your own Google Secret Manager project. They never pass through us.
Almost always an expired access token. Re-issue it on Temu's Partner Platform (step 4) and paste the new one into the Connection page — your app key and secret don't change.
Your Temu orders pulled onto your own server — searchable, exportable, with tracking pushed back to Temu. £199 + VAT, once.
See the Temu Order Fetcher