Skip to main content
The Evidence API searches non-citation research and regulatory records: patents, grants, clinical trials, FDA device/drug records, and adverse-event and safety-alert databases, sourced from Resolute’s evidence datasets. Every resource below follows the same four-endpoint pattern, so once you’ve used one, you’ve used them all. Need an API key? On Pro, create one in the API Console. Creating a key doesn’t grant every optional scope; see Authentication for feature access. For higher limits or managed credentials, contact sales.
Evidence isn’t included in a standard self-service Pro key. Each dataset requires its own scope (evidence:patents:api, evidence:grants:api, evidence:clinical-trials:api, and equivalents for the other datasets). Email sales to get a dataset scope added to your account, then generate a new key from the API Console so it picks up the scope.

​
The pattern

For a resource {resource} (e.g. patents): Search takes two parameters, and they work differently than the Search API:
  • q: free-text query. Supports AND, OR, NOT, and phrase matching with double quotes: q=CRISPR, q="gene therapy" AND cancer.
  • f: field filters, space-delimited, in field:"value" format (values must be double-quoted). Call the resource’s schema endpoint to see which fields are filterable.
Common filter fields by resource: Date range filters use gte/lt suffixes with no space before the suffix: f=dates.startDategte:"2024-01-01" dates.startDatelt:"2025-01-01". ISO dates, epoch milliseconds, and timezone offsets are all accepted; dates without a timezone are treated as UTC. Sorting uses s (default _relevance; call schema for sortable fields per resource) and sortDir, not the sort/sort_order names from Search. Pagination uses p (page number), not limit/offset.
Some fields in search and detail responses are either a plain string or an object shaped like {"id": "...", "name": "...", "highlighted": "..."}, depending on the query. Handle both, e.g. value.id ?? value.name ?? value.

​
Available resources

  • Search guide: the equivalent search over publications, with a different query syntax than Evidence
  • Full parameter reference: see Evidence in the API Reference tab; per-resource filters are best discovered via each resource’s /schema endpoint
  • Errors and rate limits: troubleshoot missing dataset scopes and retryable failures