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

# Introduction

<Note>
  Welcome to Wiseflow's API documentation. Build enterprise-grade onboarding experiences with our powerful API suite.
</Note>

## Overview

Our REST API enables you to programmatically manage customer onboarding workflows, automate data collection, and streamline verification processes.

<CardGroup cols={2}>
  <Card title="Customers" icon="users" href="/api-reference/customers/overview">
    Manage both business (B2B) and individual (B2C) customer profiles
  </Card>

  <Card title="Forms" icon="book" href="/api-reference/forms/overview">
    Create and manage dynamic data collection forms
  </Card>

  <Card title="Onboarding Sessions" icon="rocket" href="/api-reference/sessions/overview">
    Track and manage customer onboarding progress
  </Card>

  <Card title="Workflows" icon="code-branch" href="/api-reference/workflows/overview">
    Design and automate custom onboarding journeys
  </Card>
</CardGroup>

## Authentication

<CodeGroup>
  ```bash Authentication theme={null}
  curl --request GET \
    --url https://api.wiseflow.ai/v1/customers \
    --header 'Authorization: Bearer YOUR_API_KEY'
  ```
</CodeGroup>

All API requests require authentication using Bearer tokens. Include your API key in the Authorization header of each request.

<Warning>
  Keep your API keys secure and never expose them in client-side code. Use environment variables for storing sensitive credentials.
</Warning>

## Response Format

All API endpoints return JSON responses and use standard HTTP response codes:

<ResponseField name="200 - OK" type="success">
  The request was successful
</ResponseField>

<ResponseField name="400 - Bad Request" type="error">
  The request was invalid or missing required parameters
</ResponseField>

<ResponseField name="401 - Unauthorized" type="error">
  Authentication failed or token is invalid
</ResponseField>

<ResponseField name="404 - Not Found" type="error">
  The requested resource doesn't exist
</ResponseField>

<ResponseField name="429 - Too Many Requests" type="error">
  Rate limit exceeded
</ResponseField>