Skip to content

Quickstart

The Trace REST API lets you look up company technographics, firmographics, and partnership data. The base URL is https://api.tracedata.ai and every endpoint lives under /v1.

This page gets you from zero to a successful call in about two minutes.

API keys are created in the Trace app, under Settings → API Key (https://app.tracedata.ai/settings). Click create, copy the key, and store it somewhere safe — the full key is shown once and cannot be retrieved again.

Keys come in a few classes. For a quick start, a personal user key (prefix trace_…) is the right choice. See Authentication for the full breakdown of key classes and when to use each.

Look up a single company by domain (or by its Trace slug). Send your key in the X-API-Key header.

first-call.sh
curl https://api.tracedata.ai/v1/companies/stripe.com \
-H "X-API-Key: $TRACE_API_KEY"

GET /v1/companies/{identifier} returns the company’s core record. Fields that have no data are omitted rather than returned as null, so a real response may have fewer keys than the example below.

response.json
{
"name": "Stripe",
"slug": "stripe",
"primary_domain": "stripe.com",
"partnership_count": 214,
"domains": ["stripe.com"],
"investors": ["Sequoia Capital", "Andreessen Horowitz"]
}

Ask for more detail with the include query parameter. It accepts a comma-separated list; technologies and firmographics are supported here:

Terminal window
curl "https://api.tracedata.ai/v1/companies/stripe.com?include=technologies,firmographics" \
-H "X-API-Key: $TRACE_API_KEY"

That adds a technologies array (each item has tech_key, display_name, detection_count, first_seen, last_seen) and a firmographics object (industry, employee range, country, founded year, and rollup counts) to the response.

  • Authentication — key classes, header schemes, and which endpoints need a user-scoped key.
  • Credits & usage — what’s billable, rate limits, and how to back off cleanly.
  • Errors — status codes and error response shapes.
  • API Reference (interactive) — browse every endpoint and send live requests with your own key (live calls consume credits).