API Transparency

How Pdztools Uses the eBay API

A clear explanation of every eBay API endpoint we call, why we call it, and how your data is handled.

Back to Home

Pdztools integrates with the eBay REST API and eBay Trading API on behalf of sellers who grant OAuth 2.0 access to their eBay accounts. The integration covers four core workflows below. No eBay data is sold, shared, or used outside the seller's own workspace.

1 Order Sync — Pull eBay Orders into Dashboard READ

Sellers connect their eBay account via OAuth. Once connected, Pdztools calls the Fulfillment API to import new and recent orders into the seller's private dashboard, eliminating manual CSV downloads.

GET https://api.ebay.com/sell/fulfillment/v1/order GET https://api.ebay.com/sell/fulfillment/v1/order?filter=creationdate:[{date}T00:00:00.000Z..]
  • Fetches buyer shipping address, line items, SKU, quantity, sale price, and order status
  • Filters orders awaiting shipment (orderfulfillmentstatus:{NOT_STARTED|IN_PROGRESS}) for the fulfillment queue
  • Sellers can also query by date range to sync historical orders
  • Orders are stored inside the seller's isolated workspace — never visible to other accounts
[Screenshot: Orders dashboard — eBay orders synced]
2 Tracking Update — Push Tracking Numbers Back to eBay WRITE

After a fulfillment partner ships an item and returns a tracking number, Pdztools automatically posts it back to the corresponding eBay order via the Trading API's CompleteSale call.

POST https://api.ebay.com/ws/api.dll [CompleteSale]
  • Marks the order as shipped and attaches the carrier tracking number (e.g., USPS, UPS, FedEx)
  • Keeps buyers informed with real carrier tracking — no manual action by the seller
  • Helps sellers maintain eBay's on-time shipping metrics and Top Rated Seller status
  • Only the shipping carrier and tracking number are written — no other order fields are modified
[Screenshot: Order detail — tracking pushed to eBay]
3 Messaging — Read & Reply to Buyer Messages READ + WRITE

Read: Pdztools fetches buyer messages and Q&A threads (Ask Seller a Question) from the seller's inbox using the Trading API.

POST https://api.ebay.com/ws/api.dll [GetMemberMessages — fetch Q&A threads] POST https://api.ebay.com/ws/api.dll [GetMyMessages — fetch inbox messages]

Write: Sellers can reply to buyer Q&A directly from the Pdztools dashboard. Replies are posted back to eBay, optionally including image attachments.

POST https://api.ebay.com/ws/api.dll [AddMemberMessageRTQ — reply to Q&A]
  • Centralizes buyer communication alongside order management — no need to switch between tabs
  • Supports image attachments in replies (uploaded to eBay's hosting via UploadSiteHostedPictures)
  • Only the seller's own messages and Q&A threads are accessed — no access to other sellers' data
[Screenshot: eBay Messages panel inside Pdztools]
4 Listing & Inventory Management READ + WRITE

Read: Pdztools reads listing details (title, variants, images, SKU) to power fulfillment routing and SKU matching when an order arrives.

POST https://api.ebay.com/ws/api.dll [GetItem — read listing details by Item ID]

Write: Sellers can update listing quantity and inventory directly from Pdztools without visiting eBay Seller Hub.

POST https://api.ebay.com/ws/api.dll [ReviseItem — update quantity for a specific SKU variant] POST https://api.ebay.com/ws/api.dll [ReviseFixedPriceItem — update price or other listing fields] POST https://api.ebay.com/ws/api.dll [ReviseInventoryStatus — bulk update inventory quantity]
  • Supports multi-variation listings — update individual SKU quantities without affecting other variants
  • Images can be uploaded to eBay's Picture Services before listing creation or revision
  • Pdztools does not delete listings or modify title/description without explicit seller action
[Screenshot: Listing management panel — inventory update]

OAuth 2.0 Scopes Requested

Pdztools requests the following eBay OAuth scopes during account connection. Each scope is used to power a specific workflow described above.

commerce.identity.readonly Read eBay account identity (username, account type, email) — required to link and verify the seller's account in Pdztools
sell.fulfillment.readonly Read eBay orders — required for order sync and fulfillment queue management
sell.fulfillment Manage eBay orders — required to push tracking numbers (CompleteSale) and update order fulfillment status
sell.inventory.readonly Read listing and inventory data — required for SKU mapping and fulfillment routing
sell.inventory Manage listings and inventory — required to revise item quantity, price, and upload pictures
sell.account.readonly Read account settings — used to validate seller account status and marketplace registration
sell.analytics.readonly Read seller analytics — used to display sales summary (today's sales, orders of the year) on the accounts dashboard
sell.finances Read financial transactions — used to fetch transaction-level data for individual orders (fees, payout amounts)

eBay Connection Flow

How a seller authenticates and connects their eBay account to Pdztools via OAuth 2.0.

1
Seller clicks "Connect eBay Account"

Inside Pdztools, the seller navigates to the eBay Accounts page and clicks the Connect button. Pdztools redirects the seller to eBay's authorization URL with the requested OAuth scopes.

[Screenshot: eBay Accounts page — Connect button]
2
eBay displays the permission grant screen

The seller is redirected to eBay's website where they see exactly which permissions Pdztools is requesting. The seller must explicitly click Agree to proceed — no access is granted without this confirmation.

[Screenshot: eBay OAuth permission screen]
3
eBay redirects back to Pdztools with an auth code

After the seller grants access, eBay redirects to the Pdztools callback URL with a one-time authorization code. Pdztools exchanges this code for an access token and refresh token using the eBay OAuth token endpoint. Tokens are stored securely and scoped to this account only.

POST https://api.ebay.com/identity/v1/oauth2/token
✓
Account is connected and ready

Pdztools calls the eBay Identity API to fetch account details (username, account type, email) and links the account. The seller is returned to the eBay Accounts page where the connected account is now listed with today's sales and pending orders counts. All subsequent API calls use the stored token — the seller does not need to re-authenticate unless they revoke access.

[Screenshot: eBay Accounts page — account connected successfully]
Token storage & automatic refresh: OAuth access tokens are stored securely in the database, scoped per eBay account. Before every API call, Pdztools automatically exchanges the refresh token for a new access token via POST https://api.ebay.com/identity/v1/oauth2/token when the current token is expired. If the refresh token has been revoked (e.g., the seller disconnected from eBay), the account is immediately marked as suspended and no further API calls are made. Sellers can reconnect at any time by going through the OAuth flow again.
API rate limit compliance: Pdztools is designed to operate well within eBay's API call limits. Order sync runs on-demand or on a seller-configured schedule rather than continuously polling. Tracking updates are sent individually per order as fulfillment completes. Listing revisions are processed sequentially. No endpoint is called more frequently than the seller's actions require, and all requests carry valid OAuth tokens scoped to the individual seller's account.
Data retention & revocation: All eBay data is stored securely and access-scoped per seller account. Data is retained only while the seller's account is active. Sellers can revoke OAuth access at any time from eBay → Account → Manage Your Apps, which immediately terminates all API calls for that account. Upon account deletion, all associated eBay data is permanently removed within 30 days. See our Privacy Policy for full details.