Skip to main content
This walkthrough verifies your API token works, then lists the connectors configured in your workspace. You need an API token; see Authentication if you do not have one.
1

Check who you are

GET /api/users/me returns the user your token belongs to.
Response
A 401 here means the token is wrong or revoked. A 200 with your own user record means authentication is working.
2

List your configured connectors

Each connector your workspace has set up (GitHub, Jira, Slack, and so on) is a connector instance with a computed sync status.
The response lists every configured instance with its current status, so this one call is enough to build a sync-health check into your own monitoring.
3

Explore your data catalog

See which tables your workspace has in the data lake, grouped by pool (providers, artifacts, parables, workspace):
What the pools hold is covered in Your data lake.

The response envelope

Every endpoint wraps its payload the same way: Every endpoint uses this envelope. Include meta.requestId when you contact support about a specific call.

Next steps

API Reference

Every endpoint, with parameters, response shapes, and a live playground.

Connectors

Connectors, taps, and how data lands in your lake.