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

# Your first request

> Verify your token and list the connectors in your workspace.

This walkthrough verifies your API token works, then lists the connectors
configured in your workspace. You need an API token; see
[Authentication](/getting-started/authentication) if you do not have one.

<Steps>
  <Step title="Check who you are">
    `GET /api/users/me` returns the user your token belongs to.

    ```bash theme={null}
    curl https://api.askparable.com/api/users/me \
      -H "Authorization: Bearer $PARABLE_API_TOKEN"
    ```

    ```json Response theme={null}
    {
      "data": {
        "id": "018f2a3b-...",
        "name": "Jordan Rivera",
        "email": "jordan@example.com",
        "status": "ACTIVE",
        "roles": ["..."],
        "timezone": "America/New_York"
      },
      "meta": {
        "requestId": "req_..."
      }
    }
    ```

    A `401` here means the token is wrong or revoked. A `200` with your own
    user record means authentication is working.
  </Step>

  <Step title="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.

    ```bash theme={null}
    curl "https://api.askparable.com/api/vendors/tenant-connector-instances" \
      -H "Authorization: Bearer $PARABLE_API_TOKEN"
    ```

    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.
  </Step>

  <Step title="Explore your data catalog">
    See which tables your workspace has in the data lake, grouped by
    pool (`providers`, `artifacts`, `parables`, `workspace`):

    ```bash theme={null}
    curl "https://api.askparable.com/api/catalog/catalog?includeHealth=true" \
      -H "Authorization: Bearer $PARABLE_API_TOKEN"
    ```

    What the pools hold is covered in
    [Your data lake](/data).
  </Step>
</Steps>

## The response envelope

Every endpoint wraps its payload the same way:

| Field             | Purpose                                                        |
| ----------------- | -------------------------------------------------------------- |
| `data`            | The resource or list you asked for.                            |
| `meta.requestId`  | Unique id for the request. Include it when contacting support. |
| `meta.totalCount` | Total item count on paginated list responses.                  |
| `links`           | Pagination links, when applicable.                             |

Every endpoint uses this envelope. Include `meta.requestId` when you
contact support about a specific call.

## Next steps

<Columns cols={2}>
  <Card title="API Reference" icon="book" href="/api-reference/overview">
    Every endpoint, with parameters, response shapes, and a live
    playground.
  </Card>

  <Card title="Connectors" icon="plug" href="/connectors/overview">
    Connectors, taps, and how data lands in your lake.
  </Card>
</Columns>