eBay Invalid Access Token Error: Why It Happens and How to Fix It (UK Sellers, 2026)

It usually surfaces at the worst moment. Your repricer stops adjusting prices, your listing tool refuses to publish, or your profit dashboard shows figures that are three days stale, and buried in the error log is the phrase invalid access token. It sounds alarming, like something has been hacked or suspended. In reality it is plumbing: the authorisation between the tool and eBay has lapsed, and it needs renewing. This guide explains what the token actually is, the seven reasons it dies, the exact steps to fix each one, and the signals that tell you the problem is on your tool vendor’s side rather than yours. The technical facts are drawn from eBay’s own developer documentation, which is where every third-party tool’s eBay connection ultimately lives.

The message does not come from your tool. It comes from eBay’s API, addressed to your tool, and the tool passes it on to you. Behind the scenes, eBay’s modern REST APIs reject a dead token with an HTTP 401 response and an error commonly labelled 1001: Invalid access token in eBay’s developer documentation. Most sellers never see that raw form; the tool translates it into something friendlier, such as:

• “Your eBay sign-in has expired”
• “eBay connection lost, please reconnect”
• “Authorisation failed, re-authorise your eBay account”
• “Token expired or invalid”

All of these are the same underlying condition. Equally important is what the error is not telling you:

• Your eBay account is not suspended or restricted. You can sign in at ebay.co.uk and everything works normally.
• Your listings and orders are untouched. eBay carries on selling for you; only the pipe between eBay and the tool is blocked.
• It is not, by itself, a sign of hacking. Tokens expire on a schedule as a security feature. (If it coincides with security emails from eBay you did not trigger, treat that separately; see Fix 3.)
• The tool has not deleted your data. Anything already synced stays put; the tool just cannot fetch anything new.

When you connect a tool to eBay, you never hand it your eBay password. Instead, eBay uses an industry-standard system called OAuth. You sign in on eBay’s own page, eBay shows you the list of permissions the tool is asking for, and when you agree, eBay hands the tool a set of tokens: long strings of characters that work like a hotel key card. The card opens specific doors, for a limited time, and the hotel can cancel it at any moment without changing the locks for everyone else.

Per eBay’s developer documentation, there are two tokens in play:

• The access token is the short-lived key the tool attaches to every API request (fetching orders, updating a listing, pulling fees). At the time of writing, eBay’s documentation puts its lifetime at roughly two hours.
• The refresh token is the long-lived companion. When an access token expires, the tool quietly exchanges the refresh token for a fresh access token, with no involvement from you. eBay’s documentation currently puts the refresh token’s lifetime at around 18 months, after which you must sign in and consent again.

That renewal loop is why a healthy connection feels permanent even though the actual key changes many times a day. The invalid access token error appears when the loop breaks: the access token has died and the tool cannot mint a new one, either because the refresh token has also expired, or because eBay has cancelled the authorisation entirely. One caveat worth stating plainly: token lifetimes are set by eBay and can change, so treat the figures above as current rather than permanent, and check eBay’s developer documentation if the exact numbers matter to you. Some very old integrations also still use eBay’s legacy “Auth’n’Auth” token system from the Trading API era; those tokens expire too, and the fix (reconnect and re-authorise) is the same.

Roughly in order of how often UK sellers actually meet them:

1. The refresh token reached its end of life. The long-lived token simply timed out (currently around 18 months on eBay’s modern APIs). Because the interval is so long, it feels random when it hits. Nothing went wrong; it is scheduled security hygiene.
2. You changed your eBay password, or eBay forced a reset. Password changes and account security events can invalidate existing authorisations, which is exactly what you want if the password change was because of a compromise. Every connected tool then needs a fresh sign-in.
3. The app’s access was revoked in your eBay settings. You, a teammate, or a well-meaning “security clean-up” removed the tool from eBay’s third-party app access list. From eBay’s side the authorisation no longer exists.
4. The tool failed to renew in time. A vendor outage, a stuck job or a bug meant the tool missed its renewal window or corrupted its stored token. You did nothing; the fix is still a reconnect, but if it recurs it is a vendor problem.
5. The permissions changed. Tools request specific permission scopes. If the vendor ships features needing new scopes, your old consent may no longer cover what the tool now asks eBay to do, and you will be prompted to authorise again.
6. The vendor’s own credentials changed. Behind every tool is the vendor’s registered application on eBay’s developer platform. If those application keys are rotated, migrated or misconfigured, every user’s tokens can break at once. Entirely vendor-side.
7. eBay revoked the token itself. Rare, but eBay can cancel an authorisation from its side, for example around unusual activity. If reconnecting works and it does not recur, you will usually never learn the specific trigger.

Six scenarios cover essentially every case. Match your symptoms to a row before you start clicking:

Whatever killed the token, the remedy is almost always the same: issue a new one by re-authorising the tool. The wording differs between tools, but the shape of the process is universal:

1. Open the tool and find its eBay connection page, usually under Settings, Integrations, Channels or Marketplaces.
2. Look for a button labelled Reconnect, Re-authorise or Connect eBay account. If the connection shows a red or amber status, the button is normally right next to it.
3. You will be redirected to ebay.co.uk to sign in. Check the address bar shows you are genuinely on eBay: this sign-in page is the whole point of OAuth, and it is the only place your password should ever be typed.
4. Sign in with the right eBay account. If you run more than one eBay account, or your browser auto-fills a personal account, you can silently authorise the wrong one, and the tool will then sync a different shop’s data or fail confusingly. Sign out of eBay first if in doubt.
5. Review the permission list eBay shows you and choose Agree (or the equivalent consent button).
6. Back in the tool, trigger a manual sync and confirm a recent order or listing change appears. Do not assume; verify with a transaction you know happened while the connection was down.

In DashVue this lives under Settings, then eBay: the connection card shows the current health of the link to your eBay account, and a Reconnect control sits on the card itself. After reconnecting you can run a sync from the same card so DashVue catches up on any orders, fees, feedback or offers it missed while the connection was down. Most reputable tools have an equivalent surface; the important habit is knowing where yours is before you need it.

eBay keeps a register of every application you have authorised, and you can inspect and revoke them yourself. This is the place to look when a reconnect keeps failing, or when you suspect access was revoked without you realising:

1. Sign in at ebay.co.uk and open your Account settings.
2. Find the third-party app access section (on most accounts it sits with the sign-in and security settings). If you cannot see it, search “third-party app access” in eBay’s Help pages; eBay moves settings around from time to time, so the search is more reliable than any saved path.
3. You will see each connected application and when it was granted access. If your tool is missing from the list, its authorisation is gone; run Fix 1 to grant it again.
4. If the tool is listed but still failing, revoke its access here, then immediately reconnect from inside the tool. That forces a completely clean authorisation rather than an attempt to repair a half-broken one.
5. While you are here, remove anything you no longer use. Old listing tools, trials you abandoned, services that shut down: each one is a live key to your account that nobody is watching.

The most common “why now?” answer: somebody changed the eBay password last week. Password changes and security events (a forced reset, suspicious sign-in checks, account recovery) can invalidate the tokens your tools hold. That behaviour is a feature, not a bug: if your password leaked, you want every previously issued key to die with it.

The right order of operations after any security event:

1. Secure the account first. Finish the password change, review recent activity, and check your registered email and payout details are untouched before you reconnect anything.
2. Review the third-party app access list (Fix 2) and remove anything you do not recognise. If your account really was compromised, an attacker-added app is one of the things you are looking for.
3. Reconnect your tools one by one (Fix 1), starting with whatever handles live operations such as orders and postage, and finishing with reporting tools.
4. Note the date. If a tool starts erroring weeks later, you will know its token was reissued recently and the new failure is something else.

If you run a team, agree that whoever changes the eBay password also owns reconnecting the tools the same day. A surprising number of “mystery” token errors trace back to one teammate improving security and another discovering the fallout a fortnight later.

When a tool connects to eBay it asks for specific permission scopes: read your orders, manage your listings, view your finances, and so on. Your consent covers exactly the scopes shown on eBay’s authorisation screen that day. Two things can then go wrong:

• The tool grew. A vendor adds, say, postage label support, which needs a scope you never granted. Depending on how the vendor handles it, you may see hard token errors or just one feature failing while the rest works. Either way the cure is a fresh authorisation that includes the new scopes.
• You granted a trimmed-down connection deliberately. Some tools offer permission levels. DashVue, for example, lets you connect read-only (view and sync your data) or with Full Access (also publish listings and push changes back to eBay). A read-only connection is not broken when publishing fails; it is doing exactly what you asked. Reconnecting keeps whichever level you had, so if you need more, choose the higher level during the reconnect rather than repeating the old one.

Practical rule: during any reconnect, read the permission list once and approve it in full if you trust the tool with everything listed. If a permission makes you uncomfortable, do not half-grant and hope; ask the vendor what the scope is for. A reputable vendor can answer in one sentence.

Plenty of UK sellers run their own scripts or spreadsheets against eBay’s APIs. If that is you, the invalid access token error is yours to debug, and the checklist is short:

1. Check which token actually failed. An expired access token is routine: exchange your refresh token for a new one and retry. A failed refresh means the refresh token itself is dead, and only a fresh user consent flow fixes that.
2. Refresh proactively, not reactively. Renew the access token before its expiry timestamp instead of waiting for a 401 mid-batch; you will stop seeing intermittent failures in long-running jobs.
3. Confirm the environment. Sandbox and production are separate worlds on eBay’s developer platform; a sandbox token against a production endpoint fails exactly like an invalid token, because it is one.
4. Match scopes to endpoints. A token minted without the scope an endpoint requires will be rejected. The scopes you requested at consent time are the ceiling; you cannot quietly add more later without re-consent.
5. Store tokens like passwords. Whole token strings, encrypted at rest, never in a shared spreadsheet. A truncated or whitespace-mangled token is one of the classic self-inflicted versions of this error.

eBay’s OAuth token documentation covers the current lifetimes, grant flows and scope lists, and is the source of truth when anything here and your logs disagree.

Reconnecting is your job; keeping the connection alive between reconnects is the vendor’s. Escalate to the tool’s support when you see any of these:

• The error returns quickly after a successful reconnect, within hours or a few days. The tool is failing to renew or store its tokens; no amount of re-authorising on your side fixes that.
• The reconnect flow itself breaks: you click Reconnect and land on an eBay error page before you even sign in. That usually means the vendor’s application configuration on eBay’s developer platform is wrong.
• Other users report the same thing at the same time on the vendor’s status page, forum or social channels. Mass token failures are vendor-side by definition.
• It started immediately after a tool update or an announced eBay API change, and you changed nothing.

When you write to support, include: the exact error text (screenshot the raw message if you can), the date and time it first appeared, whether a reconnect succeeded and for how long, and whether you changed your eBay password or settings recently. Those four facts let a competent support team classify the failure in one reply instead of four.

The error itself is free to fix. The cost is the silence before you notice. A worked example, deliberately modest: suppose you do 40 orders a week at a £22 average sale, about £880 a week flowing through eBay. Your connection dies on a Thursday and you spot it ten days later. In that window:

• Roughly £1,250 of sales never reached your records. If you price, reorder stock or set money aside for tax from the tool’s figures, you spent ten days deciding on numbers that were wrong, and understated.
• Every automation stopped, silently. A repricer stops responding to competitors; a stock-sync tool stops ending listings when inventory runs out. If an out-of-stock item sells and you have to cancel the order, eBay’s help pages are clear that cancelling may give you a transaction defect, which can affect your seller performance level. One £35 cancelled order can cost more in standing than in cash.
• Fee visibility went dark. Fees kept accruing on eBay while your tracking stood still, so your margin picture drifted further from reality each day. (If you want the full picture of what eBay actually charges, see our UK eBay selling fees guide.)

The honest caveat: a good tool backfills. When DashVue reconnects, a full sync pulls in the orders, fees, feedback and offers it missed, so the record heals; the same is true of most serious tools. The permanent damage is rarely lost data. It is the decisions made, and the automations not firing, during the gap. Which is why the real fix for this error is not the reconnect button; it is finding out about the problem in hours instead of weeks.

1. Use a tool that watches its own connection. The difference between a two-minute fix and a ten-day gap is whether the tool tells you. DashVue’s eBay connection card shows a live health status and a countdown warning before the sign-in expires (for example, “your eBay connection expires in 12 days”), with Reconnect one click away, so renewal happens before anything breaks rather than after. If your current tool has an equivalent alert, switch it on; if it has neither, that is worth knowing about your tool.
2. Reconnect immediately after any password change. Make it part of the same task, not a thing you discover later.
3. Put a renewal note in your calendar if your tool does not warn you. Refresh tokens last many months, which is precisely why nobody remembers them; a yearly “re-authorise eBay tools” reminder beats a random outage.
4. Keep the third-party app access list tidy. Fewer authorised apps means fewer keys to leak, fewer mystery failures, and a shorter list to audit after any security scare.
5. Give the connection one owner. In a team, the person whose eBay sign-in authorised the tool is the only one who can cleanly renew it. Write down whose account that is.
6. Verify after every reconnect. One recent order, checked against the tool, confirms the pipe is genuinely flowing again.

If connection health monitoring is the feature that would have saved you this week, that is exactly the sort of unglamorous plumbing DashVue was built around: every plan includes the full dashboard, from £8.99/month, with a 7-day free trial and no card needed. Details on the pricing page.

Almost never. Tokens expire on a schedule as a security feature, and a routine expiry produces exactly this error. Treat it differently only if it arrives alongside things you did not do: password-reset emails, sign-in alerts from unfamiliar locations, or changes to your account details. In that case secure the account first (password, activity review, third-party app access audit) and reconnect tools afterwards.

No. eBay customer support cannot repair a third-party tool’s token; the authorisation is created by you signing in through the tool, and only a fresh sign-in replaces it. The only eBay-side action that ever helps is reviewing the third-party app access list in your account settings. Everything else happens in the tool.

Re-authorising only issues fresh tokens; it does not reset the tool’s database. In DashVue, reconnecting keeps everything already synced (listings, orders, fees, feedback, offers) and simply lets syncing carry on from where it stopped. Reputable tools behave the same way, but if you are nervous, ask the vendor before revoking anything: revoke-and-reconnect is the one flow where a badly built tool might start a fresh workspace.

At the time of writing, eBay’s developer documentation puts the access token at roughly two hours (renewed automatically by the tool) and the refresh token at around 18 months, after which you must sign in and consent again. These values are set by eBay and can change, so check the current developer documentation rather than relying on any article, including this one, for the exact figures.

A healthy connection should survive between refresh-token renewals, which are many months apart. If reconnecting works but the error returns within hours or days, the tool is failing to renew or store its tokens correctly. That is a vendor-side bug: report it with the exact error text and timestamps rather than reconnecting in a loop.

Commonly, yes: password changes and security events can invalidate existing authorisations, so plan to reconnect each tool right after changing the password. It is worth doing anyway; if you changed the password because of a suspected compromise, you want every old key dead.

Yes. Each application gets its own authorisation and its own tokens, and they are independent: revoking or reconnecting one does not touch the others. That is also why the fix is always per-tool; there is no single master reconnect for everything.

Sign in at ebay.co.uk, open your account settings and look for the third-party app access section (it usually sits with the sign-in and security settings). eBay occasionally moves account pages around, so if you cannot find it, search “third-party app access” in eBay’s Help; the help article links straight to the live page.

• eBay Developers Program: OAuth access tokens and refresh tokens : token types, current lifetimes and the renewal flow behind every third-party connection.
• eBay Developers Program documentation hub : authorisation grant flows, permission scopes and API error handling.
• eBay Help (ebay.co.uk): the third-party app access page for viewing and revoking application authorisations, and eBay’s guidance that cancelling an order may result in a transaction defect affecting your seller performance level.

Token lifetimes, settings locations and error wording are controlled by eBay and change over time. Where this article states a figure, it reflects eBay’s documentation at the time of writing; always confirm current values against eBay’s own pages.