> For the complete documentation index, see [llms.txt](https://checker-docs.gitbook.io/checker-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://checker-docs.gitbook.io/checker-docs/2.-integration/2.1-quick-integration-steps-for-rapid-api-integration.md).

# 2.1 Quick Integration: Steps for Rapid API Integration

The Checker dashboard simplifies the API integration process by providing users with a clear and practical interface for managing API tokens and accessing pre-built code examples. Follow the steps below to quickly integrate Checker’s API into your platform:

**2.1.1 Generating an API Token**

1. **Navigate to the "Generate a New Token" Section:**
   * Located in the top-left area of the dashboard, this section allows you to create unique API tokens.
   * Enter a descriptive token name (e.g., "MyProjectToken") to identify the token's purpose or usage.
2. **Generate the Token:**
   * Click the **"Generate"** button to create the token. Once generated, the token will be displayed alongside its name.
   * Be sure to copy and store the token securely. Tokens are sensitive credentials and should not be exposed in public repositories or code.
3. **Default Token:**
   * The dashboard provides a **default token** for immediate testing or integration. This token is visible and can be directly used, but users are encouraged to generate custom tokens for better organization and security.
4. **Token Management:**
   * If a token is no longer needed, use the trash icon next to it to delete the token.

**2.1.2 Accessing Code Examples for API Requests**

1. **Select Your Programming Language:**
   * Below the token management section, you'll find **"Code Examples"** with multiple language tabs such as **cURL, JavaScript, Python, PHP, Go, Java, and Ruby.**
   * Choose the programming language that matches your development environment.
2. **Pre-Built Request Examples:**
   * Each tab contains a pre-formulated code snippet for making an API request to verify an email address.
   * For example, the **cURL** snippet is as follows:

```
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.usechecker.com/v1/check?email=example@example.com"
```

* Replace `YOUR_API_KEY` with the token you generated and `example@example.com` with the email address you wish to verify.

3. **Test the API Request:**
   * Copy the code snippet, paste it into your development environment or terminal, and execute the request.
   * Verify that the response matches the expected output, confirming that your integration is working correctly.

**2.1.3 Verifying the API Integration**

1. **Run a Test Request:**
   * Use the provided **"Check"** button next to the API URL example to perform a quick verification directly from the dashboard. This allows you to confirm that your token is functioning as expected.
2. **Real-Time Feedback:**
   * Once a request is made, the **Activity** section on the dashboard updates dynamically, displaying the count of emails blocked by the API. This ensures that your integration is correctly set up and operational.


---

# 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://checker-docs.gitbook.io/checker-docs/2.-integration/2.1-quick-integration-steps-for-rapid-api-integration.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.