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 October 6 API 1487 notes confirm retirement and removal of reference docs and dedicated WSDL types.
- September 21 was the planned date; October 6 is confirmation, not an exact stopping time for every route.
- Affected jobs call GetAdFormatLeads, not all Trading API, ordinary orders or every seller.
- REST Leads is the replacement direction. Production access, seller consent and current methods need separate verification; the old call is no lasting rollback.
Retirement is confirmed, but dates still differ
Trading API 1487 notes dated October 6, 2026 confirm GetAdFormatLeads retired and its reference docs/dedicated WSDL types removed. The earlier conclusion that a deadline passed without official confirmation no longer applies.
September 21 was previously planned. It differs from the October 6 formal note, which gives no exact stop time for every region, app or request route and no universal fixed error response.
Do not treat the old call as sustainable. A surviving documentation page or historical success cannot override the retirement notice.
Locate the actual affected jobs
GetAdFormatLeads retrieves leads for lead-generation listings, typically Classified Ads. Find the call in schedules, integration configuration and existing logs, then trace reports, CRM and follow-up dependencies.
Ordinary order sync without this call need not be rewritten because Trading has a new release. Retirement does not close all Trading API or all Classified Ad functionality.
Hypothetical example: a daily inquiry job fails but reports zero leads. Separate successful empty results from failed retrieval instead of treating failure as no inquiries. This is not a site test.
Check replacement authorization before switching
The Q4 2025 newsletter identifies REST Leads API for active Classified Ad listings. That establishes direction, not production approval for every app.
The overview checked September 22 labels Limited Release for approved developers and requires seller authorization with sell.leads scope. Scope means permitted operations; changing a URL does not supply it.
The complete current overview was inaccessible at October 7 review, leaving any changed access/scope unknown. Confirm current overview, methods or support before switching; old Trading keysets and Sandbox success do not establish production permission.
Match job purpose to methods
The newsletter lists getClassifiedLeads for active listings and getClassifiedLeadsByItem for a particular listing. Determine whether the old job aggregates or selects an item before choosing.
Check current method time windows, filters, fields, pagination and empty-result behavior. Similar XML/REST parameter names do not justify mechanical transfer; unreviewed parameters are not asserted as a contract here.
Reconcile lead ID, listing, time and missing contact fields. Preserve explicit missing states rather than overwriting existing information with empty strings or deleting history on API error.
Preserve data when migration fails
Using existing approved test permission, compare a fixed seller/listing/window. Restore downstream writes or follow-ups only after data/fields support the task; do not add production calls to probe retirement.
If access is unapproved or reconciliation differs, pause affected writes/notifications and preserve history and human handling. Retired GetAdFormatLeads cannot be long-term rollback.
Completion needs established access, seller authorization, interpretable data and distinguishable failures. HTTP success alone does not verify all pages, fields and downstream operations.
Separate eligibility, authorization and transport
Record time, request ID, method and response, then check app approval, user token, seller ownership and method rules. With no universal retirement-error contract, one status cannot establish every cause.
DNS, TLS, timeouts and proxy authentication are separate layers for the connection troubleshooting guide. Fixed exits restore neither retired calls nor new API/seller authorization.
Change one variable at a time. Replacing app, account, listing, consent and network together makes incidental success poor evidence of migration completion.
Sources
Frequently Asked Questions
Must existing leads be deleted?
Retirement is no deletion instruction. Follow existing authorized purposes and retention, avoiding blanking records on missing fields or failure.
Can old reference pages still generate clients?
1487 says references and dedicated WSDL types were removed. Saved docs/code explain history, not current availability.
Must order sync use Leads API?
No. Leads serves Classified Ad inquiries, not orders generally. First establish whether the task actually calls GetAdFormatLeads.