RESTRICTED API

API reference

This reference shows the request and response shape used during an approved pilot. Production hosts, credentials, fields, and limits are provided after access review.

Access

Each approved account receives credentials scoped to the agreed data category and delivery terms. Send the credential as a bearer token with every request.

# Illustrative header
Authorization: Bearer dr_live_...

List records

Retrieve records from an approved category. A response includes qualified records and a cursor when another page is available.

GET/v1/records

typeRequired

Approved record category.

limitOptional

Requested page size within account limits.

cursorOptional

Cursor returned by the prior page.

curl "https://api.datarecord.io/v1/records?type=professional&limit=100" -H "Authorization: Bearer dr_live_..."

Pagination

Use the opaque next_cursor from a response to request the next page. Do not construct cursors or assume a fixed ordering outside the documented response.

{
  "data": [ ... ],
  "next_cursor": "cursor_7ZK..."
}

Errors

400

Request parameters do not match the approved schema.

401

Credential is missing, expired, or not recognized.

403

The account is not approved for the requested category.

429

The account has reached its documented request limit.

Limits and usage

Limits and billable record definitions are agreed in the pilot terms. The primary commercial unit is a qualified delivered record or a refresh subscription, not an internal request or retry count.

Discuss API access