> This page is for version 2025-09-18 (default).
> For other versions, use one of these documentation indexes:
> - 2025-09-18 (default): https://apidocs.polytomic.com/2025-09-18/llms.txt
> - 2024-02-08: https://apidocs.polytomic.com/2024-02-08/llms.txt
> - 2023-04-25: https://apidocs.polytomic.com/2023-04-25/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://apidocs.polytomic.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://apidocs.polytomic.com/_mcp/server.

Polytomic Connect allows you to offer data integrations inside your own product.
Your customers connect their own systems from your UI, so you can sync data
between your systems and theirs. To automate your own Polytomic workspace
instead, see the [Quickstart](/2025-09-18/guides/quickstart).

## How it fits together

1. Create an organization per customer. See
   [Multitenancy](/2025-09-18/guides/connect/multitenancy).
2. [Create a Harbor](/2025-09-18/guides/connect/harbor) per customer to give
   your product's AI agent governed access to their data (alternatively, you can also connect your own database, data warehouse, cloud storage bucket, or any other storage system).
3. Have the customer authenticate their systems with
   [hosted](/2025-09-18/guides/connect/hosted) or [embedded](/2025-09-18/guides/connect/embedded)
   authentication.
4. Create [syncs](/2025-09-18/guides/concepts) between their systems
   and yours.

## Authentication

Polytomic provides the configuration form and handles OAuth for every connection
type, so you don't build either. You choose where the flow runs:

|               | Hosted                             | Embedded                      |
| ------------- | ---------------------------------- | ----------------------------- |
| Where it runs | A Polytomic-hosted window          | A React component in your app |
| Appearance    | Polytomic's layout, with your logo | Styled to match your product  |

Hosted authentication is the fastest to set up and works with any frontend.
Embedded authentication keeps the user in your app.

Both flows start by minting a Connect session on your backend with
[`POST /api/connections/connect/`](/2025-09-18/api-reference/connections/connect) and your
API key. The session token only works for that one connection, and expires after
5 minutes by default.