Quorvex API · read only

Current trial and FDA signals, in your team’s workflow.

Connect to one focused endpoint for recent ClinicalTrials.gov and FDA signal records. Use it to support biotech intelligence research with source links and event dates close at hand.

Open API key settings View plans

Request example

GET · JSON

curl \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  "$QUORVEX_BASE_URL/api/v1/signals"

Set QUORVEX_BASE_URL to your Quorvex app origin. The API settings page also provides a curl snippet for your current app.

Endpoint: GET /api/v1/signals
Authentication: Bearer token
Records: Trials + FDA
Access: Read only

Endpoint reference

A small, predictable response.

Send a GET request to /api/v1/signals with a valid bearer token. The feed returns up to eight recent trial records and eight recent FDA records, sorted by event date. It accepts no write operation or documented filter parameters.

Missing, invalid, or revoked tokens receive HTTP 401. Signal records include a source-specific kind, title, source URL, source name, and ISO-formatted event date.

Response fields

Field reference for the current feed.

owner: string; The key owner label returned by the feed.
signals: array; Recent signal records, sorted newest first.
kind: "trial" | "fda"; The signal record type.
title: string; The source record title.
sourceUrl: string; A link to the underlying source record.
sourceName: string; Sponsor and source, when available.
publishedAt: string; The source event date in ISO format.

The API currently returns only trial and fda records. The wider product’s other signal sources are not part of this endpoint response.

For healthcare and biotech intelligence

Put source-linked signals where your team reviews them.

Track clinical-trial movement

Bring recent ClinicalTrials.gov signal records into an internal research view for pipeline and study monitoring.

Follow FDA signals

Review recent FDA records alongside trial activity when preparing regulatory and competitive research.

Keep source context close

Use each record’s title, source link, source label, and event date to send analysts back to the underlying record.

Access path

Check your plan, review usage, create a key.

Team and Enterprise subscription owners can review API usage in the app. The dashboard shows recorded requests; its displayed allowance is labeled as a sample default, not an enforced request cap.

Team API usage API key settings

1. Confirm API plan access

Published pricing currently lists bearer-token API access with Enterprise. Team includes API usage reporting, but pricing does not list direct API access as a Team feature.

See current plans

2. Review team API usage

The usage view requires an active Team or Enterprise subscription and is limited to the subscription owner or an administrator. It includes request history and usage totals.

3. Create a bearer token

API key settings require sign-in and an active subscription, active trial, or enabled account-level free-access override. The current key routes check authentication but do not enforce a plan; follow the published plan entitlement before using the feed. A new token is shown once, and the page supplies a curl snippet for the current app.

One endpoint. Source-linked records.

Review the plan details or continue to the existing API-key flow. Signing in and plan access checks remain in place on those app surfaces.

Review pricing API key settings