Marking code verification statuses

The method is available for models: FBS and Express.

If you are using an API Key token, one of the accesses in the list is required to call the method

Returns the verification statuses of the marking codes in the order.

An order that contains jewelry or products with mandatory labeling in the system «Честный ЗНАК», can be converted to the status READY_TO_SHIP, only when:

  1. In the method PUT v2/campaigns/{campaignId}/orders/{orderId}/boxes You will send the following information to Yandex.Market:

    • Win for each piece of jewelry in the order;

    • marking codes in the system «Честный ЗНАК» for all products in the order for which it is required.

  2. All marking codes will be successfully verified.

⚙️ Limit: 100,000 requests per hour

Request

POST

https://api.partner.market.yandex.ru/v2/campaigns/{campaignId}/orders/{orderId}/identifiers/status

Path parameters

Name

Description

campaignId

Type: integer

The ID of the campaign (store) — The technical identifier that represents your store in the Yandex Market system when working through the API. It is uniquely linked to your store, but it is intended only for automated interaction.

You can find it using a query GET v2/campaigns or find it in the seller's office on the Market. Click on your account icon → Settings and in the menu on the left, select APIs and modules:

  • block Campaign ID;
  • tab Query log → drop-down list in the block Show logs.

⚠️ Do not confuse it with:

  • the store's identifier, which is displayed in the merchant's personal account.
  • advertising campaigns.

Min value: 1

orderId

Type: integer

The order ID.

Responses

200 OK

Information on checking the marking codes.

Body

application/json
{
  "status": "OK",
  "result": {
    "items": [
      {
        "id": 0,
        "uin": [
          null
        ],
        "cis": [
          null
        ]
      }
    ]
  }
}

Type: object

All of 2 types
  • Type: object

    status

    Type: string

    The type of response. Possible values:

    • OK — There are no errors.
    • ERROR — an error occurred while processing the request.

    Enum: OK, ERROR

    The standard wrapper for server responses.

    Example
    {
      "status": "OK"
    }
    
  • Type: object

    result

    Type: object

    items

    Type: object[]

    id

    Type: integer

    The product ID in the order.

    cis

    Type: object[]

    status

    Type: string

    The status of checking the marking code in the system «Честный ЗНАК»:

    • FAILED — couldn't verify the code.

      Please try again later or delete the marking code.

    • IN_PROGRESS — during the verification process.

    • NOT_ON_VALIDATION — the marking code has not been sent for verification.

    • OK — the check was successfully completed.

    • INVALID — verification failed. The sale of goods with this code is prohibited.

    Enum: OK, FAILED, IN_PROGRESS, INVALID, NOT_ON_VALIDATION

    value

    Type: string

    The marking code in the system «Честный ЗНАК».

    Example: example

    substatus

    Type: string

    Detailing the error when checking the marking code in the system «Честный ЗНАК»:

    • WRONG_OWNER_INN — verification failed. The INN of the code owner differs from the INN of the seller.

    • CIS_VALIDATION_ERROR — verification failed.

    • CIS_GTIN_NOT_FOUND — The marking code does not contain GTIN.

    • CIS_SERIAL_NUMBER_NOT_FOUND — The marking code does not contain a serial number.

    • INVALID_SYMBOLS_FOUND — The marking code contains invalid characters.

    • CRYPTO_TAIL_FORMAT_MISMATCH_CIS_TYPE — The format of the cryptographic signature does not correspond to the type of marking code.

    • INVALID_CRYPTO_TAIL — the cryptographic signature is not valid.

    • INVALID_CRYPTO_KEY — the cryptographic key is not valid.

    • VERIFICATION_FAILED_IN_EMITTER_COUNTRY — The marking code has not been verified in the country of the issuer.

    • UNSUPPORTED_AI_FOUND — The AI markings found in the code are not supported.

    • CIS_NOT_FOUND_IN_GIS_MT — the marking code was not found in ГИС МТ.

    • NOT_PLACED_ON_MARKET — The marking code has not been put into circulation.

    • NOT_PRINTED_ON_PACKAGE — The marking code is not printed on the package.

    • EXPIRED_ITEM — the marked product has expired.

    • SALE_BLOCKED_BY_OGB — The retail sale of products is blocked by the decision of the OGV.

    • ITEM_SOLD — the marked product has been sold.

    Returned only for the status INVALID.

    Enum: WRONG_OWNER_INN, CIS_VALIDATION_ERROR, CIS_GTIN_NOT_FOUND, CIS_SERIAL_NUMBER_NOT_FOUND, INVALID_SYMBOLS_FOUND, CRYPTO_TAIL_FORMAT_MISMATCH_CIS_TYPE, INVALID_CRYPTO_TAIL, INVALID_CRYPTO_KEY, VERIFICATION_FAILED_IN_EMITTER_COUNTRY, UNSUPPORTED_AI_FOUND, CIS_NOT_FOUND_IN_GIS_MT, NOT_PLACED_ON_MARKET, NOT_PRINTED_ON_PACKAGE, EXPIRED_ITEM, SALE_BLOCKED_BY_OGB, ITEM_SOLD

    Information on checking the marking codes in the system «Честный ЗНАК».

    Min items: 1

    Example
    [
      {
        "value": "example",
        "status": "OK",
        "substatus": "WRONG_OWNER_INN"
      }
    ]
    

    uin

    Type: object[]

    status

    Type: string

    LOGIN verification status:

    • FAILED — failed verification.

    • IN_PROGRESS — during the verification process.

    • NOT_ON_VALIDATION — The WIN has not been sent for verification or not all the WINs in the order have been transferred.

    • OK — the check was successfully completed.

    Enum: OK, IN_PROGRESS, FAILED, NOT_ON_VALIDATION

    value

    Type: string

    WIN the product.

    Example: example

    substatus

    Type: string

    Error details during verification УИНа.

    • UIN_MERCHANT_MISMATCH — УИН does not belong to your store.

    • UIN_MERCHANT_UNREGISTERED — the store is not connected to the system ГИИС ДМДК.

    • UIN_NO_DATA — УИН not found or blocked.

    Returned only for the status FAILED.

    Enum: UIN_MERCHANT_MISMATCH, UIN_MERCHANT_UNREGISTERED, UIN_NO_DATA

    Verification Information УИНов.

    Min items: 1

    Example
    [
      {
        "value": "example",
        "status": "OK",
        "substatus": "UIN_MERCHANT_MISMATCH"
      }
    ]
    

    A list of product IDs and information on checking codes.

    Example
    [
      {
        "id": 0,
        "uin": [
          {
            "value": "example",
            "status": "OK",
            "substatus": "UIN_MERCHANT_MISMATCH"
          }
        ],
        "cis": [
          {
            "value": "example",
            "status": "OK",
            "substatus": "WRONG_OWNER_INN"
          }
        ]
      }
    ]
    

    Information on checking the marking codes.

    Example
    {
      "items": [
        {
          "id": 0,
          "uin": [
            {
              "value": "example",
              "status": "OK",
              "substatus": "UIN_MERCHANT_MISMATCH"
            }
          ],
          "cis": [
            {
              "value": "example",
              "status": "OK",
              "substatus": "WRONG_OWNER_INN"
            }
          ]
        }
      ]
    }
    
    Example
    {
      "result": {
        "items": [
          {
            "id": 0,
            "uin": [
              {}
            ],
            "cis": [
              {}
            ]
          }
        ]
      }
    }
    

400 Bad Request

The request contains incorrect data. More information about the error

Body

application/json
{
  "status": "OK",
  "errors": [
    {
      "code": "example",
      "message": "example"
    }
  ]
}

Type: object

All of 1 type
  • Type: object

    All of 2 types
    • Type: object

      status

      Type: string

      The type of response. Possible values:

      • OK — There are no errors.
      • ERROR — an error occurred while processing the request.

      Enum: OK, ERROR

      The standard wrapper for server responses.

      Example
      {
        "status": "OK"
      }
      
    • Type: object

      errors

      Type: object[]

      code

      Type: string

      The error code.

      Example: example

      message

      Type: string

      Description of the error.

      Example: example

      A list of errors.

      Min items: 1

      Example
      [
        {
          "code": "example",
          "message": "example"
        }
      ]
      
      Example
      {
        "errors": [
          {
            "code": "example",
            "message": "example"
          }
        ]
      }
      

    A standard wrapper for server errors.

    Example
    {
      "status": "OK",
      "errors": [
        {
          "code": "example",
          "message": "example"
        }
      ]
    }
    

401 Unauthorized

The authorization data is not specified in the request. More information about the error

Body

application/json
{
  "status": "OK",
  "errors": [
    {
      "code": "example",
      "message": "example"
    }
  ]
}

Type: object

All of 1 type
  • Type: object

    All of 2 types
    • Type: object

      status

      Type: string

      The type of response. Possible values:

      • OK — There are no errors.
      • ERROR — an error occurred while processing the request.

      Enum: OK, ERROR

      The standard wrapper for server responses.

      Example
      {
        "status": "OK"
      }
      
    • Type: object

      errors

      Type: object[]

      code

      Type: string

      The error code.

      Example: example

      message

      Type: string

      Description of the error.

      Example: example

      A list of errors.

      Min items: 1

      Example
      [
        {
          "code": "example",
          "message": "example"
        }
      ]
      
      Example
      {
        "errors": [
          {
            "code": "example",
            "message": "example"
          }
        ]
      }
      

    A standard wrapper for server errors.

    Example
    {
      "status": "OK",
      "errors": [
        {
          "code": "example",
          "message": "example"
        }
      ]
    }
    

403 Forbidden

The authorization data is incorrect or access to the resource is prohibited. More information about the error

Body

application/json
{
  "status": "OK",
  "errors": [
    {
      "code": "example",
      "message": "example"
    }
  ]
}

Type: object

All of 1 type
  • Type: object

    All of 2 types
    • Type: object

      status

      Type: string

      The type of response. Possible values:

      • OK — There are no errors.
      • ERROR — an error occurred while processing the request.

      Enum: OK, ERROR

      The standard wrapper for server responses.

      Example
      {
        "status": "OK"
      }
      
    • Type: object

      errors

      Type: object[]

      code

      Type: string

      The error code.

      Example: example

      message

      Type: string

      Description of the error.

      Example: example

      A list of errors.

      Min items: 1

      Example
      [
        {
          "code": "example",
          "message": "example"
        }
      ]
      
      Example
      {
        "errors": [
          {
            "code": "example",
            "message": "example"
          }
        ]
      }
      

    A standard wrapper for server errors.

    Example
    {
      "status": "OK",
      "errors": [
        {
          "code": "example",
          "message": "example"
        }
      ]
    }
    

404 Not Found

The requested resource was not found. More information about the error

Body

application/json
{
  "status": "OK",
  "errors": [
    {
      "code": "example",
      "message": "example"
    }
  ]
}

Type: object

All of 1 type
  • Type: object

    All of 2 types
    • Type: object

      status

      Type: string

      The type of response. Possible values:

      • OK — There are no errors.
      • ERROR — an error occurred while processing the request.

      Enum: OK, ERROR

      The standard wrapper for server responses.

      Example
      {
        "status": "OK"
      }
      
    • Type: object

      errors

      Type: object[]

      code

      Type: string

      The error code.

      Example: example

      message

      Type: string

      Description of the error.

      Example: example

      A list of errors.

      Min items: 1

      Example
      [
        {
          "code": "example",
          "message": "example"
        }
      ]
      
      Example
      {
        "errors": [
          {
            "code": "example",
            "message": "example"
          }
        ]
      }
      

    A standard wrapper for server errors.

    Example
    {
      "status": "OK",
      "errors": [
        {
          "code": "example",
          "message": "example"
        }
      ]
    }
    

420 Method Failure

The resource access limit has been exceeded. More information about the error

Body

application/json
{
  "status": "OK",
  "errors": [
    {
      "code": "example",
      "message": "example"
    }
  ]
}

Type: object

All of 1 type
  • Type: object

    All of 2 types
    • Type: object

      status

      Type: string

      The type of response. Possible values:

      • OK — There are no errors.
      • ERROR — an error occurred while processing the request.

      Enum: OK, ERROR

      The standard wrapper for server responses.

      Example
      {
        "status": "OK"
      }
      
    • Type: object

      errors

      Type: object[]

      code

      Type: string

      The error code.

      Example: example

      message

      Type: string

      Description of the error.

      Example: example

      A list of errors.

      Min items: 1

      Example
      [
        {
          "code": "example",
          "message": "example"
        }
      ]
      
      Example
      {
        "errors": [
          {
            "code": "example",
            "message": "example"
          }
        ]
      }
      

    A standard wrapper for server errors.

    Example
    {
      "status": "OK",
      "errors": [
        {
          "code": "example",
          "message": "example"
        }
      ]
    }
    

500 Internal Server Error

Internal error of Yandex. Market. More information about the error

Body

application/json
{
  "status": "OK",
  "errors": [
    {
      "code": "example",
      "message": "example"
    }
  ]
}

Type: object

All of 1 type
  • Type: object

    All of 2 types
    • Type: object

      status

      Type: string

      The type of response. Possible values:

      • OK — There are no errors.
      • ERROR — an error occurred while processing the request.

      Enum: OK, ERROR

      The standard wrapper for server responses.

      Example
      {
        "status": "OK"
      }
      
    • Type: object

      errors

      Type: object[]

      code

      Type: string

      The error code.

      Example: example

      message

      Type: string

      Description of the error.

      Example: example

      A list of errors.

      Min items: 1

      Example
      [
        {
          "code": "example",
          "message": "example"
        }
      ]
      
      Example
      {
        "errors": [
          {
            "code": "example",
            "message": "example"
          }
        ]
      }
      

    A standard wrapper for server errors.

    Example
    {
      "status": "OK",
      "errors": [
        {
          "code": "example",
          "message": "example"
        }
      ]
    }
    

No longer supported, please use an alternative and newer version.

A unique identification number for jewelry.

The manufacturer receives the UIN when he registers the product in the system of control over the turnover of precious metals and stones — GIIS DMDK.

What is GTIN?
GTIN — This is a unique number assigned to a product in a single international database. GS1. This number generates an EAN, UPC, or ISBN barcode.

How to make sure that the product is in the database
You can check the code on verification page on the GS1 association's website. If the product is not found, request the GTIN code from your supplier.

How to get a GTIN for your products
To receive GTIN codes, the manufacturer needs to join the GS1 association and register the products.