# Notify API Overview

Use the Notify API to send invoice, customer and payment information to the Notify platform. Notify and your app back-end will communicate by sending HTTP requests back and forth.

This page provides an overview of the Notify API. The topics in the chapter deal with a number of specific aspects of the API. We recommend to read these topics entirely.

If you have any questions about integrating our API, please contact us. We are happy to help!

### The Notify REST API

The API implements a **Representational state transfer** (REST) architecture. Sounds technical, but it’s really quite easy. It mainly breaks down to HTTP-methods `GET`, `PATCH`, `POST` and `DELETE` matching the operations to **read**, **update**, **create** and **delete**.

REST also implies a nice and clean structure for URLs or endpoints. This means you can reach any part of the Notify API on `https://api.notify.cm/v2/` adding the name of the resource you want to interact with.

{% content-ref url="security" %}
[security](https://docs.notify.nl/security)
{% endcontent-ref %}

{% content-ref url="authentication" %}
[authentication](https://docs.notify.nl/authentication)
{% endcontent-ref %}

{% content-ref url="api-overview" %}
[api-overview](https://docs.notify.nl/api-overview)
{% endcontent-ref %}


---

# 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.notify.nl/master.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.