Medication and source change tracking

Read published changes#

GET /v1/changes returns published events with data and next_cursor. Omit since on the first request. limit accepts 1–100, default 50. Ordering by occurred_at and UUID provides stable pagination of available history.

curl --fail-with-body --get "$IABULA_API_BASE/v1/changes" \
  --header "X-API-Key: $IABULA_API_KEY" \
  --data-urlencode "limit=50"

Continue with since#

Send the returned next_cursor as since on the next request. Keep the cursor after an empty data list so polling can resume later. Do not reuse search cursors here. Persist a cursor only after successfully processing its events.

curl --fail-with-body --get "$IABULA_API_BASE/v1/changes" \
  --header "X-API-Key: $IABULA_API_KEY" \
  --data-urlencode "since=$IABULA_CURSOR" \
  --data-urlencode "limit=50"

An observed change is not a clinical conclusion#

Canonical events use created, updated or withdrawn. Source comparisons may use observed_in_source, changed_in_source and removed_from_source. Interpretation depends on entity_type, before, after and evidence.

Defensive synchronization#

Use the event ID to prevent duplicate processing in your integration. Inspect source evidence, version, URL, source_record_id and source_run_id when available. Delivery uses HTTP polling; V1 does not document change webhooks.

GET /v1/changes#

OpenAPI contract fields#