Request Header Format

Request Header Format

Example request header:

login:123/NIC-REG/adm
password:QWERTYADM
lang:ru
request:order
operation:create
subject-contract:3457/NIC-D
request-id:20011220103455.12345@nic.ru

The request header consists of the following fields:

  • login

The Partner Agreement number and authorization type specified in the request. This field contains, separated by forward slashes (/), the Agreement number, Agreement type (for Partners, NIC-REG), and password type (adm for administrative or tech for technical; see Access Rights for details).

Example:

3/NIC-REG or 3/NIC-REG/adm (administrator authorization)
3/NIC-REG/tech (technical authorization)

  • password

The Partner's password (administrative or technical, depending on the value specified in the login field). The password may contain Latin letters and digits. See also the information on authorization using administrative and technical passwords.

  • lang

The language in which the request execution response will be returned (including error messages and explanatory comments). If this field is omitted, the response will be returned in Russian. Possible values:
ru — responses in Russian;
en — responses in English.

  • request

The request type. One of the following values, depending on the request: contract, order, service-object, service, contact, server.

  • operation

The request command. One of the following values, depending on the request: search, get, create, update, delete, swap.

  • subject-contract

The Customer Agreement number. This field must be specified in all cases except: creation of a new Customer Agreement (request:contract, operation:create); search for Customer profiles (request:contract, operation:search); creation of Partner contact records for international and foreign country-code domains (.COM, .NET, .TV, .ME, .TEL, .TRAVEL, etc.) (request:contact, operation:create).

  • request-id

A unique request identifier assigned by the Partner. This field is returned unchanged in the response header. It may be used by the Partner to correlate responses with submitted requests. The field may contain any characters and may not exceed 64 characters in length.

Recommended format: YYYYMMDDHHMMSS.PROC_NUM@partner-web-site, where:

YYYYMMDD — date in numeric format;
HHMMSS — time accurate to the second;
PROC_NUM — Unix process identifier;
partner-web-site — the Partner's domain name.

Using this format facilitates request tracking when the Partner contacts Rucenter Technical Support.


The order of fields in the header is arbitrary. Duplicate fields are not permitted. The header must be separated from the request body by a blank line.

Всё ещё остались вопросы?