Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The official status item names a 500 Internal error for the Negotiation API's sendOfferToInterestedBuyers method and remains unresolved.
- eBay says this call sends discounted offers to interested buyers and notifies those buyers.
- A 500 response alone does not confirm whether an offer was created, and the public guide does not promise idempotency for this write request.
- Before retrying, check the listing in Seller Hub β Manage Offers and compare it with your request time, listing ID and response logs.
What has eBay confirmed?
eBay Developers' production API status page lists sendOfferToInterestedBuyers Negotiation API returning 500 Internal error. It gives a last-update time of October 15, 2026 at 00:07:19 (GMT-0700); the status remained Unresolved when checked, and eBay says it is aware of the issue and working on a resolution.
The notice does not give an incident start time, affected marketplaces, application scope or recovery ETA. It confirms an open issue for this specific method, not an outage across every eBay API or marketplace.
Why not resend immediately after a 500?
The Negotiation API lets sellers send discounted offers to buyers who have shown interest in an item. eBay gives adding a listing to a Watch list or abandoning it in a cart as examples of that interest, and says buyers are notified when offers are sent.
A 500 is a server-error response, but the status notice does not say whether an offer may already have been created. The public guide also makes no idempotency guarantee for this write request, so verify the result before replaying it.
Check the offer in Seller Hub first
Open Seller Hub, find the listing that triggered the error, and go to Manage Offers to review any created offer and its status. eBay's guide identifies this view as the place to monitor and manage offers sent to buyers.
If a matching offer is present, do not send the same discount again without reviewing its status. If none appears, do not treat the missing page entry as official confirmation that a retry is safe; keep the logs and follow the status notice.
Which details help diagnose the call?
Keep the method name, listing ID, selected marketplace, request time, HTTP status, response body and any eBay request identifier returned. Compare these with the listing's Manage Offers record so the API attempt and seller-visible result are assessed together.
The notice does not identify a region, network path or client version as the cause. For an eBay API 500, start with the official status and your application logs; do not blame a proxy, DNS or a particular country without evidence.
When should automated sending resume?
At the time of this check, eBay still marked the incident Unresolved and had not posted a recovery time. Teams using this method can pause automatic retries and match each failed listing and request time against Seller Hub.
After eBay updates the status, resume according to your own review and deduplication controls. Before a manual retry, check whether the original request left an offer and have an authorized seller operator confirm the discount; do not use a real buyer flow as an unauthorized test.
Sources
Frequently Asked Questions
Does this 500 issue affect every eBay marketplace?
The public status item does not name affected marketplaces or regions. It identifies the sendOfferToInterestedBuyers method in the Negotiation API.
Does HTTP 500 prove that no offer was sent?
No. The notice does not say whether the service created an offer. Check the listing's Manage Offers view in Seller Hub and your application logs first.
Does eBay guarantee idempotent retries for sendOfferToInterestedBuyers?
The cited public guide makes no idempotency guarantee. Do not assume a repeated request cannot send another offer or notification just because the first response was 500.
Where can I review offers already sent?
eBay's guide says to open the item in Seller Hub and use Manage Offers to review and manage offers.
Has eBay posted an ETA?
The status page says Unresolved and that eBay is working on the issue; it does not list a recovery ETA.