Use this API when you have barcodes and need the Amazon listing behind them.
Use it for catalog imports, supplier files, and product-matching tools.
curl -X POST "https://app.rocketsource.io/api/v3/convert" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"marketplace":"US","ids":["012345678905"]}'const response = await fetch("https://app.rocketsource.io/api/v3/convert", {
method: "POST",
headers: {
Authorization: "Bearer YOUR_TOKEN",
"Content-Type": "application/json",
},
body: JSON.stringify({
marketplace: "US",
ids: ["012345678905", "9780306406157"],
}),
});
const matches = await response.json();Take UPC, EAN, ISBN, or GTIN values from supplier files and find the matching Amazon listings.
Check whether incoming records map to Amazon listings before they reach your review or buying workflow.
Use the same conversion flow for book identifiers and standard retail barcodes without changing your process.
Power a lightweight matching step inside spreadsheets, scripts, or internal apps that need Amazon ASINs.
Use the conversion section that matches your source data, whether it is UPC, EAN, ISBN, or GTIN.
Send the identifiers you want to look up and keep the request scoped to the records you are processing now.
Check which identifiers returned ASINs and which ones did not match.
Use the returned ASINs in your product analysis, buying process, or catalog records.
No. UPC, EAN, and ISBN requests use the same conversion endpoint. The documentation provides a separate example for each input type.
Non matching items are omitted from the response, so your code should expect partial results.
Rocket Source accepts UPC, EAN, and ISBN values through the conversion endpoint. GTIN is the umbrella term for these barcode formats, so use the matching UPC or EAN value from your data.
Yes. It is a good fit for small to medium batches inside automation, or as one step in a larger file processing workflow.
Read the technical documentation, or compare plans when you are ready to use the API.