Why sending offers needs a Full Access eBay connection

Why in-app and auto-offers need Full Access, and what a read-only connection gets instead when sending an offer to a buyer.

This article explains why sending an offer to a buyer from inside DashVue, whether by hand or through auto-offers, requires a Full Access eBay connection, and what happens instead if your account is connected as read-only.

Why sending an offer is a write action

Sending an offer is not a case of DashVue simply displaying information it has already pulled from eBay. It is a live write back to eBay: DashVue has to call eBay on your behalf and place a genuine offer against a listing, for a buyer to accept, decline or ignore. Any action that changes something on your eBay account, rather than just reading it, needs the stronger of the two connection types eBay allows a third-party app to hold.

DashVue supports two access levels for your eBay connection: Full Access, which can read your account and also make changes such as publishing listings or sending offers, and read-only, which can view and draft but cannot push anything back to eBay. Sending an offer sits firmly in the write category, so it is gated behind Full Access wherever it appears in the product.

Where this gate applies

The Full Access requirement is enforced on the server side, in the endpoint DashVue uses to send an offer. It checks the access level on your eBay connection before it will place an offer, so this is not just a front-end suggestion. It applies consistently across every place in DashVue that can trigger an offer:

  1. Sending a one-off offer to a buyer from the Send Offer screen.
  2. Sending the same offer to every eligible listing at once.
  3. Any auto-offer rule you have set up to run automatically.

If your eBay connection is read-only, none of these can complete, because the account simply does not hold the permission eBay requires to write an offer.

What a read-only connection gets instead

DashVue does not just block the action and leave you stuck. On a read-only connection, the Send Offer screen still shows your eligible listings, but instead of an in-app send button, the eligible card gives you a “Send Offer on eBay” link that takes you straight to eBay’s own send-offers page for that listing. The read-only path on your Offers overview works the same way, pointing you out to eBay rather than pretending the action can happen in DashVue. This means you can still act on the offer, just by finishing the send on eBay’s own site rather than inside DashVue.

Full Access is required to send offers in-app

Read-only connections cannot send offers or run auto-offers from DashVue. This is enforced by the access level check in DashVue’s send-offer endpoint, not just hidden in the interface. With a read-only connection, DashVue instead links you out to eBay’s own send-offers page so you can send the offer there. To send offers and run auto-offers directly in DashVue, your eBay connection needs to be upgraded to Full Access.

Why DashVue draws the line this way

Keeping read-only connections genuinely read-only is a deliberate choice. It means you can connect an account to try DashVue’s profit tracking and listing tools without granting write permission to eBay until you are ready, and it means DashVue never attempts a write action on your eBay account that your connection has not actually authorised. When you do want the in-app send button and auto-offers, moving to Full Access is what unlocks them, alongside the other write actions in DashVue such as publishing listings.

Last updated 2026-07-04.

Was this article helpful?

Related articles