Public API to Birst Integration

How Datrise loads Public API into Birst

Datrise syncs Public API's records, response payloads, pagination cursors, request parameters, schemas, and fetch timestamps into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

Public API: Generic REST endpoint pulled on a schedule.

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Public API entities map to Birst

Public API entity	Birst object	Notes
records	`public_api_records`	id PK · custom fields → flattened columns
response payloads	`public_api_response_payloads`	id PK · linked to public_api_records
pagination cursors	`public_api_pagination_cursors`	id PK · linked to public_api_records
request parameters	`public_api_request_parameters`	id PK · linked to public_api_records

FAQ

How does Datrise handle Public API's custom fields in Birst?

Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Birst types.

How does the Public API to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

Connect Public API to Birst the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.