1688 Search By Image API: one successful Base64 test
Observed result: on September 20, 2026, a generated unbranded bottle concept was compressed to a 192 × 192 JPEG and sent as raw Base64 with page: 1 and pageSize: 10. The response returned HTTP 200, business code: 0, and 10 first-page products. The usage record showed 10 credits deducted.
| Evidence field | Observed value |
|---|---|
| Input | Generated unbranded bottle concept, compressed to JPEG |
| Input method | Raw imageBase64, without a data-URL prefix |
| Request | Page 1, page size 10 |
| Result | HTTP 200, business code: 0, 10 rows |
| Usage | 10 credits deducted for the successful call |
| Earlier attempts | Three public-image-URL requests returned business code 13007; no credit deduction was observed |
Two selected rows appeared visually relevant to amber dropper bottles; one selected row was an off-target face mask. That mix is why image search should create a candidate list, not certify a factory or product match.
What the result can support
The result can support a shortlist of returned offerId values for subsequent Product Detail checks. It cannot establish manufacturer identity, product quality, material, compliance, intellectual-property rights, negotiated price or landed cost.
- Read the full 1688 sourcing analysis
- Open the 1688 Search By Image API documentation
- Follow the broader sourcing tutorial
The raw Base64 and all credentials are intentionally excluded from this public record.
Last reviewed: 2026-09-23 · Maintained by the official Nexscope team.
Put your next idea to work.
Follow another guide, inspect the evidence or find a focused tool for the task you are researching.
Bring a real ecommerce question.
Ask how to use a Nexscope workflow, suggest an improvement, or report a reproducible problem through the right public channel.