Sandbox
What a test key reads, for trying the API at no cost.
A test key (hyd_test_) reads the sandbox: eleven companies whose records are frozen, with
the same fields and evidence as any record. Make one in the dashboard's API keys page.
| Domain | Name |
|---|---|
adyen.com | Adyen |
atlassian.com | Atlassian |
duolingo.com | Duolingo |
ericsson.com | Telefonaktiebolaget LM Ericsson |
monzo.com | Monzo |
ovhcloud.com | OVHcloud |
rakuten.co.jp | Rakuten Group, Inc. |
sap.com | SAP |
shopify.com | Shopify |
skoda-auto.com | Škoda Auto |
stripe.com | Stripe |
- Reads of these companies answer as a live key's would. Any other domain is a
404. - Enrichments and batches have ended by the time they're answered (
200). A test key's batch takes up to 100 domains. A sandbox company succeeds; any other domain fails asenrichment_failed, and a name can endname_ambiguousorname_not_found. Awebhook_urlgets its message, signed with your workspace's secret. - Cost: nothing. A workspace's test keys make at most 1,000 calls a day, 100 of them
enrichments or batches with a
webhook_url, and are rate-limited like live keys. Their calls show on the usage page astest. - One thing a test key can't show is a
202: its enrichments have always ended.