Introduction

Rubie is a modern platform for building full-stack data migration and integration workflows.

Rubie allows you to build powerful data migration workflows to power your customer activation, onboarding, and integration processes - even when no API exists.

Connect a source account once and store its opaque credential_id. Then trigger the configured Blueprint with that credential whenever your application needs to send data, polling the resulting run until it reaches a terminal state and fetching its outputs when complete.

Companies of all sizes use Rubie for:

• Competitor data migration: Rip and replace your competition by offering a one-click data migration experience. Customers authenticate their legacy accounts and Rubie handles extracting, cleaning, and mapping the data into your system.
• Complex mapping exercises: Intelligently map large datasets from one external system into yours as a part of customer activation.
• Impossible integrations: Build workflows to access data across websites and applications that don’t have APIs.

Get Started

Quickstart

Connect an end user’s account and run a Blueprint against it, end to end.

Connect an account

Collect credentials through a Rubie-hosted form, without secrets touching your servers.

Trigger a run

How to send structured API data and poll a run to completion.

The integration surface

Whatever the underlying workflow does, the API you talk to is the same six endpoints. The paths below are relative to https://app.rubiehq.com/api/v1:

Method	Path	Purpose
POST	/credential-sessions	Start a hosted credential collection
GET	/credential-sessions/{id}	Poll until credential_id is ready
DELETE	/credentials/{credentialId}	Disconnect and revoke
POST	/blueprints/{blueprintKey}/trigger	Queue a Blueprint run
GET	/blueprint-runs/{runId}/status	Poll the run to a terminal state
GET	/blueprint-runs/{runId}/results	Retrieve completed run outputs

The interesting part — which system to log into, what to extract, how to map and validate it — lives in your Blueprint’s configuration rather than in this API. That’s what keeps the surface small: adding a new source system does not change the API shape. The strategy, Blueprint key, and expected data are configuration supplied by Rubie.

Browse the API Reference for the full schemas and an interactive playground.