You are going to put some data to update, for example, restrictions of the specific allotment. Your credentials are:

Endpoint URL: /echannel/rate_plan_allotment_plans/

{
    "id": 111111,
    "rate_plan": 66666,
    "disable_flexible": true,
}

So the data you are going to send consists of parameters: "id", "rate_plan", "disable_flexible" these are in request body and authentication token parameter that is sent via GET with name "token" encoded in url.

To generate signature for this request you should form the string by pattern:

<name1>=<value1>...<nameN>=<valueN>

All parameters in that string are going in alphabetical order. The parameters list should contain all parameters that you are going to send including private token in the form:

private=f5347f1fa2dd2c5fb778a4cea8483c25

So we will add private token to that list of parameters, then sort the keys, concatenate them with their values and then concatenate again with each other as mentioned before. In the end we will come up with string like:

disable_flexible=true;id=111111;private=f5347f1fa2dd2c5fb778a4cea8483c25;rate_plan=66666;token=2523e7d3be4393983732d02652216a81

To generate signature use md5 hashing against the string. In this example signature is:

    47bd4263f87f6d177b07705867e72967

So the final request url will be:

/echannel/rate_plan_allotment_plans/?token=2523e7d3be4393983732d02652216a81&sign=47bd4263f87f6d177b07705867e72967

And request body is:

{
    "id": 111111,
    "rate_plan": 66666,
    "disable_flexible": true,
}

Using curl the request will look like:

curl -d '{"id":111111, "rate_plan": 66666, "disable_flexible": true}' -X PUT /echannel/rate_plan_allotment_plans/?token=2523e7d3be4393983732d02652216a81&sign=47bd4263f87f6d177b07705867e72967

Every api response support pagination. Let's study the support using simple get request to the API:

/echannel/hotels/?sign=3f821e082f7b155bc6ab7520d3cd05e7&pk=609198278&token=5329d9e05a9621a09575a3e8607264cf

• num_pages shows how many pages resultset has
• page is index of selected page. First page index is 1
• limits is quantity of results shown per page

{
    "num_pages": 1,
    "page": 1,
    "limits": 10,
    "hotels": [
        {
            "id": 609198278,
            "name": "Тест отель"
        }
    ]
}

If you want to change pagination bahaviour you may add pagination parameters to request. To change limits add it to url with desired value. For example this will make API to show 100 results per page, as you can see limits=100 was appended to url

/echannel/hotels/?sign=3f821e082f7b155bc6ab7520d3cd05e7&pk=609198278&token=5329d9e05a9621a09575a3e8607264cf&limits=100

Lets assume you've made request like:

/echannel/hotels/?sign=3f821e082f7b155bc6ab7520d3cd05e7&pk=609198278&token=5329d9e05a9621a09575a3e8607264cf&limits=2

And the response was:
Paginator indicates that two pages are available (num_pages = 2) and page number 1 is selected and we display 2 results per page.

{
    "num_pages": 2,
    "page": 1,
    "limits": 2,
    "hotels": [
        {
            "id": 609198278,
            "name": "Test hotel 1"
        },
        {
            "id": 609198279,
            "name": "Test hotel 2"
        }
    ]
}

To request second page append page parameter to url with value 2, like that, and the response will contain the second page:

/echannel/hotels/?sign=3f821e082f7b155bc6ab7520d3cd05e7&pk=609198278&token=5329d9e05a9621a09575a3e8607264cf&limits=2&page=2

Each request supports different data formats. To specify data format you're going to use simply add format parameter to your url like:

This url specifies format - json
Note: json format is default, if you want to use json formatting you don't need t specify format at all.

/echannel/hotels/?sign=b7c916d6d03acad9dbbca53c323169f1&format=json&token=5329d9e05a9621a09575a3e8607264cf

Supported formats are:

• json
• xml

Json

The json formatting is pretty simple.

{
   "object_field": [
        "list_item1",
        "list_item2",
        "list_item3"
   ],
   "str_field": "string",
   "int_field": 123,
   "decimal": 123.23
}

Xml

Valid xml requires version header and root node.
To form xml assume that your object is root node of xml and is called "root". So you should just create separate nodes for your object fields, name them after corresponding fields and put value as content, with the only exception: list values are wrapped with separate "item". As for now all structures are plain and so we don't need to handle nested objects.
So to send xml data you should wrap all nodes into one: "root" node.

<root>
   <object_field>
       <item>list_item1</item>
       <item>list_item2</item>
       <item>list_item3</item>
   </object_field>
   <str_field>string</str_field>
   <int_field>123</int_field>
   <decimal>123.23</decimal>
</root>