Public API to MySQL Integration

How Datrise loads Public API into MySQL

Datrise syncs Public API's records, response payloads, pagination cursors, request parameters, schemas, and fetch timestamps into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Public API: Generic REST endpoint pulled on a schedule.

MySQL: Widely used OSS relational engine (InnoDB).

How Public API entities map to MySQL

Public API entity	MySQL object	Notes
records	`public_api_records`	id PK · custom fields → JSON 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 MySQL?

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Public API to MySQL 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.