> For the complete documentation index, see [llms.txt](https://docs.tendar.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tendar.co/documentation/onboarding/overview.md).

# Overview

The Onboarding Service is the foundation of every Tendar integration. It provides a suite of APIs that let you create and manage customer profiles, verify identities through KYC checks, and send OTPs - everything you need to onboard users securely before granting them access to lending, disbursement, or any other Tendar product.

### How it works

***

Integrating the Onboarding Service into your platform follows a straightforward flow:

{% stepper %}
{% step %}

### Authenticate

Include your secret key in the `Authorization` header of every request (`Bearer <your_secret_key>`). All endpoints are scoped to your company, so the data you create and query is isolated to your account. Read the [Authentication](/documentation/getting-started/authentication.md) Article for better understanding
{% endstep %}

{% step %}

### Create a user

Register your customer by sending their profile information (name, email, phone, date of birth, etc.) to the [Create User](/documentation/onboarding/user-management.md#create-a-user) endpoint. Tendar returns a unique `user_id` that you'll reference across all other API calls.
{% endstep %}

{% step %}

### Continue to other services

Once onboarded, the user is available across the entire Tendar ecosystem — Credit Score, Disbursement, Recollection, and BNPL services.
{% endstep %}
{% endstepper %}

### Base URL

***

All Onboarding Service endpoints are served under:

Production

```bash
https://api.tendar.co/onboarding
```

Sandbox

```bash
https://tendar-onboarding-dev-v2.fly.dev
```

### Core Features

***

The Onboarding Service is organized into three main modules:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-user-group">:user-group:</i></h4></td><td><strong>User Management</strong></td><td>Create, update, list, and export your customers.</td><td><a href="/documentation/onboarding/user-management.md">User Management</a></td></tr><tr><td><h4><i class="fa-key">:key:</i></h4></td><td><strong>OTP (One-Time Password)</strong></td><td>Send and verify OTPs through email, SMS, or both.</td><td><a href="/documentation/onboarding/one-time-password.md">One Time Password</a></td></tr><tr><td><h4><i class="fa-face-viewfinder">:face-viewfinder:</i></h4></td><td><strong>KYC (Know Your Customer)</strong></td><td>Run identity verifications against Nigerian government databases.</td><td><a href="/documentation/onboarding/know-your-customer.md">Know Your Customer</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tendar.co/documentation/onboarding/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
