The API/MCP page in 3Dsellers shows every API and MCP token issued to your company, every request made with those tokens, and how much of your rate limit you have used. Use it to create a token, revoke one you no longer trust, and find out why an integration or AI agent is failing, without contacting support. Open it from your name at the bottom of the left menu > API/MCP, or go to app.3dsellers.com/api-mcp.
💡 New to the 3Dsellers API or MCP? Start with How to connect AI agents to 3Dsellers using MCP, then come back here to manage the connection.
In this article:
What does the 3Dsellers API/MCP page do?
The API/MCP page has three tabs:
Tokens - the buttons to connect Claude, get an API token or connect MCP, and the list of every token issued to your company, with its scope, status, request count, last use and expiry date.
Requests - a log of every REST API call and MCP tool call made with your tokens, with a 7-day summary, filters, and the full details of each call.
Rate limits - how many calls you have used in the current minute and the current day, per limit, and when each counter resets.
The API/MCP page does not change your products, listings or orders. It only shows what your tokens did, and lets you create or revoke tokens.
Where do I find the API/MCP page?
Log in to 3Dsellers.
Click your name at the bottom of the left menu.
Choose API/MCP.
You can also reach it from Settings > Profile > API / MCP in the settings menu, or open app.3dsellers.com/api-mcp directly. The page opens on the Tokens tab.
Tokens tab: create, review and revoke 3Dsellers API tokens
At the top of the Tokens tab are three buttons:
Add to Claude - connects 3Dsellers to Claude. See How to connect AI agents to 3Dsellers using MCP for the full steps.
Get API token - creates a bearer token for your own integration or script that calls the 3Dsellers REST API.
Connect MCP - shows how to connect an MCP client: Connect in Claude, Copy URL (the server URL is
https://api.3dsellers.com/mcp), and a For developers section with a token and a ready-made command.
The Tokens tab of the 3Dsellers API/MCP page with the Add to Claude, Get API token and Connect MCP buttons
Why does Get API token say I already have active tokens?
If your company already has active tokens for the same app, Get API token and the developer section of Connect MCP show a warning first: "You already have N active tokens for this app", with the list of those tokens. No new token is created until you click Generate new token anyway.
Creating a new token does not revoke the old ones: every token stays active until it expires or you revoke it. If you are replacing a token, revoke the old one in the Issued tokens list afterwards.
What does the Issued tokens list show?
Below the buttons, Issued tokens lists every token issued to your 3Dsellers company:
Column | What it shows |
App | The app or agent the token was issued to |
Token | The last 6 characters of the token, for example …8ffb6d. The same short code is used in the Requests filter, the request details and the revoke confirmation, so you can match them by eye. |
Scope | What the token is allowed to do, for example |
Status | Active or Revoked |
Requests | How many calls were logged with this token |
Last used | The time of the most recent logged call, or "-" if none |
Created / Expires | When the token was issued and when it stops working. The tokens shown in our examples expire about six months after they were created. |
Actions | Requests opens the Requests tab filtered to this token. Revoke appears on active tokens only. |
The Issued tokens list with token codes, scopes, status, request counts and the Requests and Revoke buttons
How do I revoke a 3Dsellers API or MCP token?
On the Tokens tab, find the token in Issued tokens (match the last 6 characters).
Click Revoke in its row.
Confirm. The confirmation names the app and the token's last characters.
The row changes to Revoked. The token stops working on its next request, and the app or AI agent that used it has to connect again. Revoking cannot be undone; create a new token if you need access again.
To cut off every integration at once, click Revoke all above the list. It asks you to confirm "Revoke all N active tokens?" first.
⚠️ Revoke all disconnects every app and AI agent using a 3Dsellers token at the same time, including Claude and any custom integration. Use it only if you think a token has leaked.
Requests tab: the log of every 3Dsellers API and MCP call
The Requests tab of the API/MCP page records each REST API call and MCP tool call made with your tokens. At the top is a summary of the last 7 days:
Requests (7d) and Errors - total calls and how many failed
REST and MCP - the split between direct API calls and AI agent tool calls
Requests per day - a chart with errors in red
Most called - the endpoints and tools used most, with their error counts
The 7-day summary of the Requests tab with request and error counts, the per-day chart and the most called endpoints
Below the summary is the log itself. Filter it with the search box (endpoint or tool name), Source (REST or MCP), Status, and a From / To date range. Click Refresh to load new calls. Each row shows:
Column | What it means |
Time | When the call was made |
Source | REST for an API call, MCP for an AI agent tool call |
Endpoint / tool | For REST, the method and path, such as |
Status | The HTTP status. 200 is a success. 200 error means an MCP tool ran but returned an error (MCP tools reply with 200 even when they fail). 4xx codes mean the call was refused, for example 403 when the token does not have the scope the call needs. |
Duration | How long 3Dsellers took to answer |
Window | The rate-limit counter the call was counted against, for example |
Remaining | How many calls were left in that counter right after this call |
Seller | The seller ID the call was made for, when the call named one |
Error | The error message, when the call failed |
The Requests log with a failed MCP call highlighted, showing 200 error and the message in the Error column
To see only one token's calls, click Requests on that token's row in the Tokens tab. The Requests tab opens with a "Token …xxxxxx" filter tag; close the tag to see every token again.
How do I see the details of one 3Dsellers API request?
Click a row in the Requests log to open its details: the status, the token's last 6 characters, what was sent, and, for REST calls, what 3Dsellers answered.
Values that look like secrets (fields named token, secret, password, API key, credentials or authorization) are shown as [redacted].
For MCP calls, the tool's arguments are kept but its result is not: MCP results are streamed to the AI agent and not stored.
Long request and response bodies are shortened.
Rate limits tab: how close am I to my 3Dsellers API limit?
The Rate limits tab shows each limit that applies to your account, how much of it you have used in the current minute and the current day, and when each counter resets. The badge at the top shows which plan's limits apply, for example Paid plan limits.
Per-minute counters reset every 60 seconds.
Per-day counters reset at 00:00 UTC.
REST and MCP calls share the same counters: an AI agent and your own integration draw from the same limit.
Click the arrow on a row to see which endpoints count against it.
On a paid plan, the limits shown in our example are:
Limit | Per minute | Per day | Counts |
All API and MCP calls (general) | 600 | 50,000 | Every REST endpoint and MCP tool, combined |
Order reads (order-read) | 120 | 5,000 | GET /v1/orders |
Order writes (order-write) | 60 | 2,500 | Order tags and tracking |
Product reads (product-read) | 120 | 5,000 | GET /v1/products, product details and listings |
Product writes (product-write) | 60 | 5,000 | Creating and updating products, categories, tags, templates and mapping rules |
Further rows below these cover other operations, such as creating actions and import schedules. Every call counts against the general limit and, if it has one, its own operation limit.
The Rate limits tab showing per-minute and per-day usage for each limit with reset times
Example: reading an error in the 3Dsellers request log
An AI agent was asked to run a CSV import schedule, and nothing happened. In the Requests tab:
Set Status to Error.
The row
mcp:run-import-scheduleshows 200 error.The Error column reads: "Import schedule 17096 is paused, and the platform only runs active schedules."
The fix is to activate the schedule, then run it again. A row for mcp:create-import-schedule with "Unique constraint failed on the fields: (seller_id, file_url)" means a schedule for that seller and file URL already exists, so the agent should update the existing schedule instead of creating a new one.
What the 3Dsellers request log does not show
Calls with a missing, wrong or revoked token. 3Dsellers cannot tell which company they belong to, so they are not logged. If an integration fails and you see no rows, check that its token is still Active.
The results of MCP tool calls (only their arguments are stored).
Signing in and connecting. Only calls to the API and to MCP tools are logged.
Troubleshooting
My integration or AI agent stopped working
On the Tokens tab, check the token's Status and Expires date. A revoked or expired token must be replaced: create a new one and update the integration, or reconnect the AI agent.
On the Requests tab, set Status to Error and read the Error column for that token.
On the Rate limits tab, check whether a counter is at its limit, and when it resets.
I see 403 "Insufficient scope" in the request log
A 403 with "Insufficient scope" means the token is not allowed to make that call, for example a product:read token trying to read orders. Check the token's Scope on the Tokens tab, and connect again with a token that has the scope the call needs.
A token shows 0 requests but my integration says it is calling 3Dsellers
The calls are probably not using that token. Calls with a missing or invalid token are not logged at all. Compare the last 6 characters of the token in your integration with the Token column.
FAQ
Does creating a new 3Dsellers API token revoke my old one?
No - creating a token with Get API token or Connect MCP does not revoke your existing tokens. They stay active until they expire or you revoke them on the Tokens tab.
What does "200 error" mean in the 3Dsellers request log?
"200 error" means an MCP tool was reached and ran, but it returned an error. MCP tools reply with HTTP 200 even when they fail, so 3Dsellers marks these rows as errors and shows the tool's message in the Error column.
How far back does the Requests tab go?
The summary and chart on the Requests tab cover the last 7 days. Use the From / To filter to look at a specific date range in the log.
Do REST API calls and MCP calls have separate rate limits?
No - REST API calls and MCP tool calls share the same 3Dsellers rate-limit counters. An AI agent and your own integration draw from the same per-minute and per-day limits.
When do the 3Dsellers API rate limits reset?
Per-minute limits reset every 60 seconds. Per-day limits reset at 00:00 UTC. The Rate limits tab shows the time left until each reset.
Can I see my API key in full on the API/MCP page?
No - the API/MCP page shows only the last 6 characters of each token. Copy the full token when you create it, and keep it private.
Is my data safe in the request log?
The 3Dsellers request log hides values that look like secrets (tokens, passwords, API keys, credentials) as [redacted], and only people in your 3Dsellers company can see it.