1. Configure the request
Use an HTTP module to POST a JSON domains array with Content-Type application/json and a securely stored Authorization Bearer header. Start with one domain before batching up to 100.
Use the documented API with your automation tool. All credit packs include API access; this is an HTTP recipe rather than a native connector.
Content reviewed: · Evidence and limitations · 235-store benchmark
Use an HTTP module to POST a JSON domains array with Content-Type application/json and a securely stored Authorization Bearer header. Start with one domain before batching up to 100.
Iterate results and map each row by domain. Preserve currency with prices and handle explicit errors separately. This is an HTTP recipe, not a native connector or automatic result webhook.
Run a small paid test with a known domain, check the result and credit ledger, then verify downstream mapping. The web daily preview is separate from paid synchronous API calls. Do not store keys in URLs or public documents.
This request uses a fictional domain to demonstrate the JSON shape. Replace it with your own domain. Each new paid request can consume credits.
POST https://storetechscan.ytriple.dev/api/v1/inspect
Authorization: Bearer zsk_live_YOUR_KEY
Content-Type: application/json
{"domains":["sample-store.example"]}Full API reference| Stage 0 · Input & Credit | Stage 1 · Tech Stack, ESP & Pixels | Stage 2 · /products.json | Stage 3 · Business context | Stage 4 · Public contacts | |||
|---|---|---|---|---|---|---|---|
| # | Domain | Status / Credit | Platform | Tech Stack & Pixels | Product sample & prices | ICP Vertical & Model | Role Email & Socials |
| Submit domains above to run live inspection. | |||||||
No. Use its generic HTTP request capability and your StoreTechScan key. Native CRM sync and result webhooks are not included.
Do not assume retry deduplication. A new inspection can consume credits again. Keep successful responses and investigate an ambiguous timeout before replaying it.