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

# Building path

Chift gives you two ways to build on top of your end-users' financial tools. Both start from the same [connectors, consumers, and connections](/guides/how-it-works). What differs is **who writes the integration logic** and **who triggers it**.

<CardGroup cols={2}>
  <Card title="Unified API" icon="code" href="/guides/unified-api/overview">
    **You build the integration and you have the lead.** You call Chift's endpoints directly and read or write your end-users' data whenever your product needs to.
  </Card>

  <Card title="Syncs" icon="arrows-rotate" href="/guides/syncs/overview">
    **Chift builds the integration and triggers the flows.** We set up the synchronisation with you and run it on an event or a schedule, with no integration code on your side.
  </Card>
</CardGroup>

## How they compare

|                                  | Unified API              | Syncs                                                     |
| -------------------------------- | ------------------------ | --------------------------------------------------------- |
| Who writes the integration logic | You                      | Chift                                                     |
| Who triggers it                  | Your product, on demand  | Chift, on an event or a schedule                          |
| Integration code on your side    | Yes                      | None                                                      |
| Reading and writing data         | You call the Unified API | Chift runs the flow; you read status and can trigger runs |

Most developers start with the **Unified API**. **Syncs** suit teams who would rather delegate both the build and the running of the flow to Chift.

<Note>
  New to the terms *connector*, *consumer*, and *connection*? Read [How it works](/guides/how-it-works) first.
</Note>