> ## Documentation Index
> Fetch the complete documentation index at: https://rubie.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

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

<img src="https://mintcdn.com/rubie/DLW5AGCveJXj9war/images/hero.png?fit=max&auto=format&n=DLW5AGCveJXj9war&q=85&s=e21ee40382bdb3027901bc1c344bced7" alt="Hero" className="rounded-xl" width="1000" height="525" data-path="images/hero.png" />

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

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect an end user's account and run a Blueprint against it, end to end.
  </Card>

  <Card title="Connect an account" icon="key" href="/guides/hosted-credential-collection">
    Collect credentials through a Rubie-hosted form, without secrets touching
    your servers.
  </Card>

  <Card title="Trigger a run" icon="play" href="/guides/blueprint-runs">
    How to send structured API data and poll a run to completion.
  </Card>
</CardGroup>

## 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](/api-reference/credential-sessions/create-credential-session)
for the full schemas and an interactive playground.