Overview
The 3Dsellers API empowers eBay sellers and developers to seamlessly integrate their online stores with the 3Dsellers platform. This RESTful API enables you to automate tasks, manage listings programmatically, synchronize data across multiple platforms, and build custom integrations that streamline your eCommerce operations. Whether you're a technical seller looking to automate workflows or a developer building custom solutions, the 3Dsellers API provides the tools you need to extend and enhance your selling capabilities.
Note: To access and utilize the 3Dsellers API, you must have administrative privileges within your 3Dsellers account.
How to Enable the 3Dsellers API
Log in to your 3Dsellers account
Navigate to Settings from the main menu
Click on Integrations in the settings menu
Locate the 3Dsellers API section
Click Generate API Key to create a new API key
Copy the generated API key and store it securely - you will need it for authentication
API Authentication
Auth2 is not required if you generated your API token from the 3Dsellers app. In that case, simply send the header Authorization: Bearer <your_token> with each request.
The OAuth2 flow is for building an application that other sellers authorize. In that case:
Send the seller to
GET /auth/authorizeExchange the result for a token at
POST /auth/tokenSend the access token as
Authorization: Bearer YOUR_ACCESS_TOKENon every requestCheck a token is still valid with
GET /auth/me
Full flow details are in the API documentation.
What the API covers
The reference at api.3dsellers.com/docs is the complete, always-current list. This is the shape of it, so you know where to look:
Products and catalog
Read, create, update and patch products. Manage categories, custom attributes and SKU templates. Read and tag listings. Publish products to a marketplace. Map catalog categories to channel categories, and map product data onto channel item specifics.
Orders
Read orders for a seller account, push carrier and tracking numbers back out to the marketplace, and tag orders in bulk.
Helpdesk
List tickets and counts per status, read full message threads including buyer attachments, reply to buyers, and set ticket status or type.
Sellers and integrations
List connected marketplace accounts, check integration health, toggle catalog inventory sync, read eBay business policies, and manage eBay Store categories.
Bulk actions
Queue the same batch operations the app runs from a grid selection, and poll their progress. They run asynchronously.
Standing rules
Automations (a trigger plus actions across listings, catalog, orders and Helpdesk), offer rules for eBay Best Offers, and post-sale Auto Messages.
Data in and out
Queue exports and recurring export schedules, monitor CSV imports and their per-row errors, and save or reuse filter sets as segments.
Listing Designer
Create and edit the HTML designs wrapped around eBay listing descriptions, and set which template new listings receive.
Webhooks
POST /webhooks/subscribe and POST /webhooks/unsubscribe. Supported events:
order.createdimport-csv.status-updated
Health check
GET /health/live- the service is upGET /health/ready- the service is ready for requests
Rate Limits
The API enforces rate limits to keep performance fair across all accounts. Build your integration to cope with them:
Handle rate limit responses explicitly rather than letting them fail silently
Back off exponentially and retry
Prefer webhooks over polling, and batch endpoints over per-record calls
Contact support if your use case genuinely needs a higher limit
Troubleshooting
I'm getting an "Invalid API Token" error
Check you copied the whole token from the Integrations page
Generate a fresh token and update it in your integration
Confirm the header is exactly
Authorization: Bearer <your_token>
I'm getting an "Insufficient scope" error
The token is valid but is not authorized for that area. Re-generate or re-authorize it so it covers the endpoints you are calling.
Can I manage variations and inventory through the API?
Yes. Products support variations, and inventory can be read and written, including per-warehouse stock. See the product endpoints in the reference.
Why did my call return before anything changed?
Bulk actions, exports and some large mapping operations are asynchronous by design. The call returns an ID, and you poll that ID for progress. A response is not the same as a finished job.
Are there limitations?
Some endpoints require a specific plan feature, and some actions are restricted to particular channels. The reference notes these per endpoint.
Best Practices
Keep your token secure. Never commit it to version control. Use environment variables or a secrets store
Dry run anything destructive. Bulk actions, tracking pushes and bulk mapping writes accept
dryRun. Use it, especially on a filter-based selection, where a wrong filter can hit thousands of recordsRead per-row results. Batch endpoints report each row separately. A 200 does not mean every row succeeded
Use webhooks instead of polling where an event exists for what you need
Handle errors properly, including rate limits, auth failures and validation errors
Test on one record first. Especially for anything that reaches a buyer, such as tracking pushes, Helpdesk replies and offer rules