E-commerce Store Database API
Enrich domains with verified e-commerce store data: platform, country, category, PSP, shipping carriers, contacts, merchant size, technology signals, and CRM-ready flat fields.
API v2 domain enrichment
Authorization: Bearer YOUR_API_KEYcurl -H "Authorization: Bearer YOUR_API_KEY" "https://shoprank.com/api/v2/domains/aboutyou.com"curl -H "Authorization: Bearer YOUR_API_KEY" "https://shoprank.com/api/v2/me"Use this zero-credit endpoint for connection tests without spending credits.
curl -H "Authorization: Bearer YOUR_API_KEY" "https://shoprank.com/api/v2/fields"https://shoprank.com/api/openapi.yamlImport this spec into Postman, gateway tooling, or internal API catalogs.
Use merchant_size_score (0-100 percentile) for granular filtering, or map
merchant_size_band directly to a CRM/Clay dropdown. Bands are derived from score:
99+ is top_1_percent, 95-98 is top_1_to_5_percent,
90-94 is top_5_to_10_percent, 75-89 is top_10_to_25_percent,
and below 75 is long_tail. merchant_size_country_band applies
the same buckets relative to the store's country.
Common API workflows
Use the API when you need the same e-commerce store fields inside signup flows, CRM enrichment, Clay workflows, or internal account scoring.
Enrich signup domains
Check whether inbound domains are active e-commerce stores and attach country, platform, category, PSP, carrier, and contact fields.
Score e-commerce accounts
Use merchant_size_score and merchant_size_country_score to route larger merchants without exposing raw revenue estimates.
Sync CRM and Clay fields
API v2 returns flat, stable fields that match exports, so RevOps can map responses into CRM, Clay, spreadsheets, or internal tools.
Simple access model
Fields are unlocked by package. Locked fields return upgrade_required before credits are spent.
| Package | Example unlocked fields |
|---|---|
| Standard | domain, country, country_iso, state, state_iso, city, is_ecommerce, primary_platform, meta_title, meta_description, tech, tech_maturity_level, estimated_monthly_tech_spend, payment_providers, emails, phones, social, website_year, website_month, commoncrawl_web_presence_bucket, commoncrawl_web_presence_trend_12m |
| Premium | company_name, vat_number, store_age_tier, first_seen_year, cross_border_domains |
| Enterprise | merchant_size_score, merchant_size_band, merchant_size_country_score, merchant_size_country_band, merchant_size_confidence, merchant_size_source, cross_border_cluster_size_range |
Try API v2
Log in to reveal your API key, run live API tests, and track credit usage. Free accounts include 50 credits.
Security defaults
- Use the
Authorization: Bearerheader for API v2. Query-string keys are kept only for legacy compatibility. - Keep production keys out of URLs, browser history, logs, screenshots, and third-party tools.
- Merchant size is returned as relative score and band only; raw revenue amounts and dollar ranges are intentionally not exposed.
Migrating from API v1
| Area | API v1 | API v2 |
|---|---|---|
| Authentication | ?api_key=... |
Authorization: Bearer ... |
| Company identifier | item.company_id |
vat_number |
| Company name | item.company_name |
company_name |
| Page metadata | item.meta_title, item.meta_description |
meta_title, meta_description |
| Response shape | Legacy item object |
Flat typed fields |
| Missing domain | 404 Not found |
200 with found: false |
| Access control | Legacy package behavior | Field-level upgrade_required before credits are spent |
API v1 remains available for existing integrations. New integrations should start with API v2.