Skip to main content

How to manage sellers and vendors with the API

Use the DataDoe public API to list, inspect, rename, reconnect, and delete the sellers and vendors in your Organization. DataDoe MCP offers the same operations except deletion. Send every API request with your datadoe-api-key header. To add a seller or vendor, create an invitation with the Invitation links API.

List and inspect sellers and vendors

  • GET /api/v1/util/sellers-and-vendors lists sellers and vendors. Filter with query (name search) and marketplaceCountryCode, and page with page and pageSize.
  • GET /api/v1/util/sellers-and-vendors/{sellerOrVendorId} returns one seller or vendor in the same shape as a list item.

Each seller or vendor includes its id, name, accountType, marketplace, row count, and its Seller Central, Vendor Central, Amazon Ads, and Amazon Ads DSP connections. Each connection includes:

  • needsReauthorization: true when Amazon no longer accepts the stored authorization and data stops updating
  • lastAuthorizedAt: when Amazon last granted the authorization
  • initialLoadStage: how far the first data load has progressed

The sellerOrVendorId applies to one marketplace. Use it in exports, Actions, and the other API endpoints.

Rename a seller or vendor

Send a PATCH request to /api/v1/util/sellers-and-vendors/{sellerOrVendorId}:

json
1{
2    "name": "Partner ABC US"
3}

The API returns status 200 with the updated seller or vendor. Names are unique within your Organization, so a name that another seller or vendor uses returns status 409.

Reconnect a seller or vendor

When a connection shows needsReauthorization: true, create a reconnect invitation with POST /api/v1/util/sellers-and-vendors/{sellerOrVendorId}/reconnect and send it to the account owner. The seller or vendor keeps its ID and data. See Reconnect an existing seller or vendor.

Delete a seller or vendor

Send a DELETE request to /api/v1/util/sellers-and-vendors/{sellerOrVendorId}. The API returns status 204.

  • Deletion is immediate and cannot be undone.
  • DataDoe also deletes the seller or vendor’s connections. A connection that another seller or vendor still uses, such as a shared Amazon Ads connection, is kept.
  • Data collected for deleted connections is purged after 30 days.
  • The API returns status 409 while the seller or vendor has an Amazon Marketing Cloud (AMC) binding. Disconnect AMC first. See How do I disconnect AMC?.

To add the account again later, create a new invitation. The new seller or vendor gets a new ID.

MCP tools

DataDoe MCP offers the same operations except deletion. Delete sellers and vendors through the API or in DataDoe.

OperationMCP tool
List sellers and vendorssellers_and_vendors_list
Inspect one seller or vendorsellers_and_vendors_get
Renamesellers_and_vendors_rename
Create an invitation or a reconnect invitationsellers_and_vendors_invitation_create
List pending invitations or read one invitationsellers_and_vendors_invitations_get
Revoke an invitationsellers_and_vendors_invitation_revoke

sellers_and_vendors_invitation_create creates a reconnect invitation when it gets a sellerOrVendorId. sellers_and_vendors_invitations_get returns one invitation and its status when it gets an invitationId, and lists pending invitations otherwise. In MCP, redirectUrl is optional when creating invitations. Without it, the invitee sees the DataDoe confirmation page when the flow finishes.

Errors

  • 400: the ID is not a UUID, or the request body is invalid
  • 404: the seller or vendor does not exist in your Organization
  • 409: see the conflicts above