Before you start

What you need in front of you

To get your connection details

Your normal Temu seller account login
Apps and services → Manage your apps in Seller Central — free for your own shop
A few days' patience — Temu's compliance & security assessment has to be approved first

Hosting with a fixed public IP address (see step 5 — non-negotiable)
The Fetcher's Connection page open in another tab — it shows your server's IP in a copy-ready box and has a test button

Do this before you buy. Applying for permission to connect software to Temu takes a few days and not every account is approved straight away. Getting your connection details first is the surest proof the tool can work for your account. See the product page or email us if you're unsure your account qualifies.

The six steps

Add a self-developed app
Fill in the details & pass the assessment
Copy your app key & secret
Authorise it — your access token
Register your server's IP
Paste in and test the connection

Add a self-developed app

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.

Fill in the app details & pass the assessment

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 approved IP address list, which Temu calls its IP white list. It must contain a fixed EU or UK server IP (see step 5).

Both stages must show "Approved". The app isn't usable until App information filling and Compliance and security assessment are both approved — this can take a few days, so start early.

Temu Partner Platform — app details and the compliance and security assessment survey — The Partner Platform app page, with Temu's compliance & security assessment survey.

Copy your app key & app secret

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.

Keep the app secret private. It's a password: anyone with it can act as your app. Don't email it or paste it into a chat — the Fetcher stores it in your own database or your own Google Secret Manager, never with us.

Temu Partner Platform — app key and app secret shown after approval — After both approvals, your app key and app secret appear here.

Authorise the app — your access token

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.

Tokens can expire. If the connection works today but stops months from now, re-issuing the access token is the usual fix — your app key and secret stay the same.

Register your server's IP — don't skip this

The approved IP address 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.

⚠ This must be a fixed IP. Temu rejects every call from an unregistered address, so hosting whose outbound IP changes — some budget shared hosting, serverless platforms, home broadband — will not work. There is nothing any tool can do about that; it is how Temu's connection works. A small virtual private server (VPS), from a few pounds a month, or any hosting with a dedicated IP address is fine. Not sure what you have? Ask your host: "Is my outbound IP fixed?"

Paste the three values in and test

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 read-only request for an order list and explains whether the problem is one of the three values, the approved IP address or a missing permission.

Temu Order Fetcher dashboard — a searchable, sortable table of Temu orders with buyer, items, amounts, status and tracking — A green “connected” result means you're done — your Temu orders land in a table you own, ready to search and export. (Demo data shown.)

If the test fails

Three usual suspects — and the fix for each

Wrong connection details

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.

Server address not approved

Add the exact IP address shown on the Connection page to Temu's approved list, then wait a few minutes for Temu to apply it and test again.

Missing permission

Enable the order-query and logistics permissions on the app. A permission error normally means a required permission is missing or still awaiting approval; use Temu's returned code when checking the app.

Still stuck? Email ln3@sitelead.co.uk with a screenshot of the test result and we'll get you connected — support is included, and the three-month guarantee covers Temu changing its API.

FAQ

Common questions about Temu connection details

How long does Temu take to approve API access?

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.

Does it cost anything to use Temu's API?

No — using the API for your own shop is free. You're only paying once for the Fetcher itself (£199), never per order or per call.

Why do I need a fixed IP address?

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.

Will sitelead ever see my keys?

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.

The connection stopped working months later — what changed?

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.

Getting your Temu connection details