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

# Quick Start

## Create your first Noty project:

After registering and logging in to Noty, we take you to onboarding to create your first project. When you finish onboarding, you will be directed to the main screen of your project. On this screen, you can access your API key.

If you need to find your API Key later, click on the three dots in the upper right corner of the project screen and go to Project settings. Here you can see your API Key; if there is a security problem, you can regenerate it.

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

## Send your events to Noty:

## Send your first event

<mark style="color:green;">`POST`</mark> `https://usenoty.com/api/v1/send`

This endpoint is used to send your events to Noty.

#### Headers

| Name                                            | Type   | Description         |
| ----------------------------------------------- | ------ | ------------------- |
| Content-Type<mark style="color:red;">\*</mark>  | String | application/json    |
| Authorization<mark style="color:red;">\*</mark> | String | Bearer: YOUR\_TOKEN |

#### Request Body

| Name                                      | Type      | Description                                                                                                                                                                                                                                                       |
| ----------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| channel<mark style="color:red;">\*</mark> | string    | The channel you'd like to send an event to.                                                                                                                                                                                                                       |
| message                                   | String    | Notification message.                                                                                                                                                                                                                                             |
| level                                     | Integer   | **Low**, **Normal**, and **High** levels can be defined here. If you leave this field blank, we will send a Low level notification. For more details, you can take a look at [Notification Levels](/quick-start/starting-with-the-basics/notification-levels.md). |
| date                                      | Timestamp | By default, we store the current date and time. Use this field to send a different day and time. The date must be sent in "Y-m-d H:i:s" format.                                                                                                                   |

{% tabs %}
{% tab title="200: OK " %}
Take a look at an example for publishing events.

{% tabs %}
{% tab title="cURL" %}

{% endtab %}
{% endtabs %}
{% endtab %}
{% endtabs %}


---

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

```
GET https://docs.usenoty.com/quick-start/quick-start.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.