If your workflow starts with a supplier spreadsheet, this API gives you a structured way to upload the file, retrieve the results, and export what your team needs.
It is designed for repeatable file-based analysis, not one-off manual lookups.
curl -X POST "https://app.rocketsource.io/api/v3/scans" \
-H "Authorization: Bearer YOUR_TOKEN" \
-F "file=@supplier-list.xlsx" \
-F 'attributes={"mapping":{"id":0,"cost":1},"options":{"marketplace_id":"US","name":"Supplier List"}}'curl -X POST "https://app.rocketsource.io/api/v3/scans/SCAN_ID" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"page":0,"per_page":100,"tableType":"products"}'Turn incoming CSV or XLSX supplier files into scan results that are easier to sort, review, and export.
Run the same scan workflow every time a new catalog lands in your inbox or storage bucket.
Let analysts and virtual assistants follow the same file workflow instead of handling each product by hand.
Export scan output as CSV, XLSX, or JSON, or push completed work into connected systems with webhooks.
Start with CSV or XLSX input that matches the columns your process expects.
Send the file with the scan request and any required attributes for the marketplace and file format.
Use the scan ID to retrieve the results once processing is complete, or let a webhook tell you when it is ready.
Download the output in CSV, XLSX, or JSON format, or send it to Google Sheets if that is part of your workflow.
The API docs show multipart uploads for CSV and XLSX files.
Yes. The docs include CSV, XLSX, JSON, and Google Sheets export options for completed scans.
No. You can retrieve results by scan ID, or use a webhook to notify your system when the scan changes state.
Yes. The API docs include a cancel endpoint for scans that are already in progress.
Read the technical documentation, or compare plans when you are ready to use the API.