Fusion developer access

Trace data in your workflow.

Send an identifying field, receive a job ID, then retrieve your result with its source verdicts. This console calls the deployed API. It uses your Quarry API key and existing Quarry credits and does not simulate a successful lookup.

Open your Quarry workspace Access and billing

Live request console

Your Quarry API key (uses your existing Quarry credits)

I am authorized to research this target. This runs a real metered API request.

Connect your application

POST /api/quarry/trace
Authorization: Bearer YOUR_QUARRY_API_KEY
Content-Type: application/json

{"company":"Your authorized research target"}

A successful request returns HTTP 202 with a jobId. Check its status through GET /api/quarry/trace?job=JOB_ID using the same key. Results and credit charges belong to your Quarry organization.

HTTP 401 means access is missing; 429 includes retry-after; 503 means a dependency or provisioning is unavailable. Source verdicts are research evidence, not a guarantee that a person or contact is correct.

Create your API key in Quarry after accepting its acceptable-use policy. This console forwards requests to Quarry, which enforces account access and meters its existing credit balance. No separate Trace key or balance is required. HTTP 403 aup_required means the policy must be accepted in Quarry first.

Arrange API access