Skip to main content

Working with the 3Dsellers developer API

For developers: base URL, authentication (OAuth and bearer token), webhooks, and the full endpoint reference for building directly against the 3Dsellers API.

Written by Karolina Santiago

Who this is for

Most people should connect an AI agent through the MCP server (see How to connect AI agents to 3Dsellers using MCP). This guide is for developers who want to call the 3Dsellers API directly from their own code, or set up webhooks. The MCP server and the direct API run on the same platform and share the same authentication.

Base URL and versioning

All API requests go to:

https://api.3dsellers.com

Resource endpoints are versioned under /v1/, for example GET https://api.3dsellers.com/v1/products. Requests and responses are JSON over HTTPS.

Authentication

There are two ways to authenticate, both tied to your 3Dsellers company:

  • Bearer token - the quickest option for your own scripts and integrations. Copy it from Settings > Integrations > MCP 3Dsellers (the same token used to connect an AI agent) and send it as an Authorization: Bearer YOUR_TOKEN header on every request. Keep it private, and regenerate it from that dialog if it is ever exposed.

  • OAuth 2.0 (authorization code flow) - for apps that act on behalf of other sellers. Send the user through GET /auth/authorize, exchange the returned code at POST /auth/token, and use the resulting access token the same way. GET /auth/me confirms a token is valid.

Every request is scoped to the authenticated company. To target a specific marketplace account, pass its seller ID (from GET /v1/sellers).

Full endpoint reference

The complete, always-current list of endpoints, parameters, and response shapes lives in the interactive API documentation:

api.3dsellers.com/docs

Treat that page as the source of truth. It is generated from the live API, so it never goes out of date. At a glance, the API covers:

  • Products - list, create, and update products, plus categories, tags, and SKU templates

  • Listings - the per-channel view of your products, with tags

  • Mapping templates - field mappings between your products and each channel, including bulk apply

  • Orders - list orders by seller, with tags

  • Sellers and policies - connected marketplace accounts and their business policies

  • Segments - your saved filter sets

  • CSV imports - import jobs and their row-level errors

  • Bulk actions - queue large batch operations, including publishing products to a channel, and poll their progress

Webhooks

To receive real-time notifications instead of polling, subscribe your endpoint with POST /webhooks/subscribe and remove it with POST /webhooks/unsubscribe. See the API documentation for the available events and payloads. Webhooks are a direct-API feature and are not available through the MCP server.

Direct API vs the MCP server

Use the MCP server when you want an AI assistant (Claude, Cursor, and similar) to read and act on your data conversationally, with no code required. Use the direct API when you are writing your own software, need webhooks, or want fine-grained control over each request. Both use the same base URL and the same token.

Access and rate limits

API access and rate limits depend on your 3Dsellers subscription. If a request is rejected for access or rate reasons, check your plan or slow your request rate. For details, or to ask about higher limits, contact the 3Dsellers team.

Need help?

Questions about the API, or an endpoint you wish existed? Use the "Need more MCP tools?" button in Settings > Integrations > MCP 3Dsellers, or reach out through your usual support channel.

Related Articles
Did this answer your question?