# Create Destination

### Register Destination(Endpoint)&#x20;

To register an endpoint, click on the "Register" button. Currently, the system allows only one endpoint to be created at a time. Once an endpoint is created, the "Register" button will disappear. Upon clicking "Register," a popup will appear, requiring you to enter the following details.

{% stepper %}
{% step %}
URL

Ensure the entered HTTPS URL is valid and ready to receive data via the POST method.
{% endstep %}

{% step %}

#### Auth Type

When registering a new endpoint, choose the authentication type that aligns with your backend capabilities. Rest assured, your secret keys and tokens will be securely stored to ensure data protection and privacy.
{% endstep %}
{% endstepper %}

<figure><img src="/files/4CvF6TBABdQBQwD8WRXA" alt=""><figcaption></figcaption></figure>

Explore Different Authentication Methods

1. Default
2. Custom SHA-256 HMAC Signature
3. Basic Auth
4. Bearer Token
5. Api Key

***

#### Default Type

Selecting the default type means there is no authentication. Our system will call your API without any authentication but will include our default headers.

***

#### Custom SHA-256 HMAC Signature

When selecting the custom SHA-256 HMAC Signature, you are opting for a more secure form of authentication. You need to define your header key and specify the signing secret that your backend supports. This method ensures that the communication between your system and the API is encrypted and authenticated, protecting it from tampering and unauthorized access. Ensure that both the client and server agree on the signing secret and header key to successfully implement this authentication type.

<figure><img src="/files/adTjlh88AwHzz9KEBB7b" alt=""><figcaption></figcaption></figure>

***

Basic Auth

When you select Basic Auth, you will need to enter both a username and a password. Your password will be securely stored and should be kept confidential to prevent unauthorized access. It's advisable to use a strong password, combining letters, numbers, and special characters, to enhance security.

<figure><img src="/files/j6msKKGjArQ6dqtg7VbW" alt=""><figcaption></figcaption></figure>

***

#### Bearer Token

When you select Bearer Token, you must provide the token value without prefacing it with **"Bearer"**. The request will be sent with the Authorization header properly formatted to include the Bearer token automatically. Ensure the token is kept secure and never shared inappropriately.

<figure><img src="/files/CpJaggQrmu0MIbnaSocG" alt=""><figcaption></figcaption></figure>

***

#### Api Key&#x20;

To select an API Key, include both the key and its corresponding value. Also, specify where to include the key, either in the header or as a query parameter.

<figure><img src="/files/bn0USxLfBC1xRBeqw8oo" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.insurgrid.com/data-webhook-page/destination/create-destination.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
