> For the complete documentation index, see [llms.txt](https://ledsak.gitbook.io/docs-for-ledsak/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ledsak.gitbook.io/docs-for-ledsak/integrations/website.md).

# Website

## Webhook Integration Documentation

### Endpoint

**URL:**\
`https://api-v2.ledsak.ai/api/webhook/website/webhook`

**Request Method:**\
`POST`

### Description

This endpoint is used to send a webhook to a website. It requires a raw JSON request body containing client information, source details, branch location, and lead details.

***

### Request Format

#### **Headers**

Ensure the request contains the appropriate headers, such as:

```json
jsonCopy codeContent-Type: application/json
```

#### **Request Body**

The request body must be in JSON format and include the following fields:

| Field          | Type   | Description                                                                         |
| -------------- | ------ | ----------------------------------------------------------------------------------- |
| `client`       | string | The client associated with the webhook.  ([Find Client ID](#user-content-fn-1)[^1]) |
| `source`       | string | The source of the webhook.                                                          |
| `branch`       | string | Name of the branch location.                                                        |
| `lead_details` | array  | An array containing details about the lead. Each object in the array must include:  |

#### Client ID:

1. Go to Integrations
2. Click on Website View
3. See the Client Credentials: (Client id)

<figure><img src="/files/j2IbgANgRbWi4WHk6fV1" alt=""><figcaption><p>Click on Website Leads view.</p></figcaption></figure>

#### Source:

<figure><img src="/files/QBJk03ZyVlX4anXGYIHG" alt=""><figcaption><p>Lead Source</p></figcaption></figure>

#### Branch:

<figure><img src="/files/ihN8Dz9hvcVN9p2KykFh" alt=""><figcaption><p>Branch List</p></figcaption></figure>

#### Lead Details:

* `lead_field` (string): The name of the lead field.
* `lead_value` (string): The corresponding value for the lead field.

#### **Example Request Body**

{% code title="jsonCopy code" %}

```json
{
  "client": "example_client",
  "source": "website",
  "branch": "Main Branch",
  "lead_details": [
    {
      "lead_field": "name",
      "lead_value": "John Doe"
    },
    {
      "lead_field": "email",
      "lead_value": "johndoe@example.com"
    }
  ]
}
```

{% endcode %}

***

### Response

#### **Status Code**

`200 OK`

### Created Lead Succesfull

```json
{
  "message": "Successfully created",
  "lead_id": "6645f7c17aff889d10509de5"
}
```

[^1]: Go to Client ID


---

# 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://ledsak.gitbook.io/docs-for-ledsak/integrations/website.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.