# 🕴️ GETTING STARTED

## ℹ️ Overview

TurinPay offers a powerful REST API that supports bitcoin lightning network and standard on-chain operations with action events associated allowing you to receive and send microtransactions instantly.

Our API uses HTTP response codes and returns all error responses in JSON. To explore the API as much as possible.

{% embed url="<https://codesandbox.io/s/serene-sid-riuss?fontsize=14&hidenavigation=1&theme=dark>" %}
Codesandbox from TurinPay
{% endembed %}

## 🔑 Authentication

The TurinPay API uses `API Keys` to authenticate requests. You can view and manage your API Keys in the API keys section.

Authentication to the API is performed with a key. Provide your API key on the `token` header.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API Requests without authentication will also fail.

## ⚠️ Errors

TurinPay uses conventional HTTP response codes to indicate the success or failure of an API request. Codes in the `2xx`range indicate success, in the `4xx`range indicate an error that failed given the information provided (usually a required parameter was omitted or incorrectly sent), in the `5xx`range indicate an error with TurinPay's servers.

| Status Code         | Meaning                                                                                | HTTP Response                                  |
| ------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------- |
| 200 - OK            | Everything worked as expected                                                          | `{ data: { ... } }`                            |
| 201 - OK            | Entity created with success                                                            | `{ data: object }`                             |
| 400 - Bad Request   | The request was unacceptable, often due to an incorrect or missing required parameter. | `{ success: false, message: 'Error details' }` |
| 404 - Not Found     | The requested resource doesn't exist                                                   | `{ success: false, message: 'Error details' }` |
| 500 - Server Errors | Something went wrong with TurinPay's servers                                           | `{ success: false, message: 'Error details' }` |


---

# 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.turinpay.com/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.