1. Configure the request
Use an HTTP API enrichment column with a domain input, POST JSON and Bearer authorization. Map the domain cell to one domains-array item. Keep the API key in a credential facility rather than a shared table column.
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 API enrichment column with a domain input, POST JSON and Bearer authorization. Map the domain cell to one domains-array item. Keep the API key in a credential facility rather than a shared table column.
Read the results array and map primary_platform, tech_stack, shopify_price_median, shopify_currency, icp_fit_score, is_real_merchant, has_b2b_wholesale and generic_emails. Preserve status so failures remain distinct from missing signals.
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.