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

# General Details

All the requests regarding Olympz API should be sent to: <mark style="color:blue;">**<https://olympz.com/api>.**</mark>

All the requests should contain the **Auth header** with an **authorization key** that will be sent to Merchant, e.g.:

```
POST /deposit/create HTTP/1.1
Host: olympz.com
Accept: application/json
Content-Type: application/json
Auth: fcd8766d4fa5b4a5c7198b87a5d0921d
```

***

Olympz API deals with **JSON** requests. All the requests, excluding **GET**, should be signed by a **secret key** that will be also sent to Merchant. For signing you need to deliver the md5 hash from a request body with a secret a key concatenating. Then the delivered hash is used in the **Sign header** and sent together with the request. The example of the hash calculation in **PHP**:

```
$secret_key = '1dfcd12ba13fff487a84cf50d8099297';
$request = '{"test":"test"}';
$sign = md5($request . $secret_key);
//49e8dde596382693c52ccc3d722e5229               
```

POST request will be written as:

```
POST /deposit/create HTTP/1.1
Host: olympz.com
Accept: application/json
Content-Type: application/json
Auth: fcd8766d4fa5b4a5c7198b87a5d0921d
Sign: 49e8dde596382693c52ccc3d722e5229
…
{"test":"test"}            
```

Whereas Olympz sends the requests to the Merchant system using the same rules and keys. Your integration keys should be received via email from the manager.&#x20;