Get a list of bindings sale.paymentItemShipment.list

Scope: sale

Who can execute the method: administrator

This method retrieves a list of payment bindings to shipments based on a filter.

Method Parameters

Name
type

Description

select
array

An array containing the list of fields to be selected (see fields of the sale_payment_item_shipment object).

If not provided or an empty array is passed, all available fields of payment bindings to shipments will be selected.

filter
object

An object for filtering the selected payment bindings to shipments in the format {"field_1": "value_1", ... "field_N": "value_N"}.

Possible values for field correspond to the fields of the sale_payment_item_shipment object.

An additional prefix can be assigned to the key to specify the filter behavior. Possible prefix values:

  • = — equals (works with arrays as well)
  • % — LIKE, substring search. The % symbol in the filter value does not need to be passed. The search looks for the substring in any position of the string.
  • > — greater than
  • < — less than
  • != — not equal
  • !% — NOT LIKE, substring search. The % symbol in the filter value does not need to be passed. The search goes from both sides.
  • >= — greater than or equal to
  • <= — less than or equal to
  • =% — LIKE, substring search. The % symbol needs to be passed in the value. Examples:
    • "mol%" — searching for values starting with "mol"
    • "%mol" — searching for values ending with "mol"
    • "%mol%" — searching for values where "mol" can be in any position
  • %= — LIKE (see description above)
  • !=% — NOT LIKE, substring search. The % symbol needs to be passed in the value. Examples:
    • "mol%" — searching for values not starting with "mol"
    • "%mol" — searching for values not ending with "mol"
    • "%mol%" — searching for values where the substring "mol" is not present in any position
  • !%= — NOT LIKE (see description above)

order
object

An object for sorting the selected payment bindings to shipments in the format {"field_1": "order_1", ... "field_N": "order_N"}.

Possible values for field correspond to the fields of the sale_payment_item_shipment object.

Possible values for order:

  • asc — in ascending order
  • desc — in descending order

start
integer

This parameter is used to manage pagination.

The page size of results is always static: 50 records.

To select the second page of results, the value 50 must be passed. To select the third page of results, the value is 100, and so on.

The formula for calculating the start parameter value:

start = (N-1) * 50, where N is the desired page number

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"select":["id","shipmentId","paymentId","xmlId","dateInsert"],"filter":{"paymentId":1025,"shipmentId":2467},"order":{"id":"desc"}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.paymentitemshipment.list
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"select":["id","shipmentId","paymentId","xmlId","dateInsert"],"filter":{"paymentId":1025,"shipmentId":2467},"order":{"id":"desc"},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/sale.paymentitemshipment.list
        
// callListMethod: Retrieves all data at once. Use only for small selections (< 1000 items) due to high memory usage.
        
        try {
          const response = await $b24.callListMethod(
            'sale.paymentitemshipment.list',
            {
              "select": [
                "id",
                "shipmentId",
                "paymentId",
                "xmlId",
                "dateInsert",
              ],
              "filter": {
                "paymentId": 1025,
                "shipmentId": 2467,
              },
              "order": {
                "id": "desc",
              }
            },
            (progress) => { console.log('Progress:', progress) }
          )
          const items = response.getData() || []
          for (const entity of items) { console.log('Entity:', entity) }
        } catch (error) {
          console.error('Request failed', error)
        }
        
        // fetchListMethod: Retrieves data in parts using an iterator. Use it for large data volumes to optimize memory usage.
        
        try {
          const generator = $b24.fetchListMethod('sale.paymentitemshipment.list', {
            "select": [
              "id",
              "shipmentId",
              "paymentId",
              "xmlId",
              "dateInsert",
            ],
            "filter": {
              "paymentId": 1025,
              "shipmentId": 2467,
            },
            "order": {
              "id": "desc",
            }
          }, 'ID')
          for await (const page of generator) {
            for (const entity of page) { console.log('Entity:', entity) }
          }
        } catch (error) {
          console.error('Request failed', error)
        }
        
        // callMethod: Manually controls pagination through the start parameter. Use it for precise control of request batches. For large datasets, it is less efficient than fetchListMethod.
        
        try {
          const response = await $b24.callMethod('sale.paymentitemshipment.list', {
            "select": [
              "id",
              "shipmentId",
              "paymentId",
              "xmlId",
              "dateInsert",
            ],
            "filter": {
              "paymentId": 1025,
              "shipmentId": 2467,
            },
            "order": {
              "id": "desc",
            }
          }, 0)
          const result = response.getData().result || []
          for (const entity of result) { console.log('Entity:', entity) }
        } catch (error) {
          console.error('Request failed', error)
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'sale.paymentitemshipment.list',
                    [
                        'select' => [
                            'id',
                            'shipmentId',
                            'paymentId',
                            'xmlId',
                            'dateInsert',
                        ],
                        'filter' => [
                            'paymentId'  => 1025,
                            'shipmentId' => 2467,
                        ],
                        'order' => [
                            'id' => 'desc',
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result->error()) {
                error_log($result->error());
                echo 'Error: ' . $result->error();
            } else {
                echo 'Success: ' . print_r($result->data(), true);
            }
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error fetching payment item shipments: ' . $e->getMessage();
        }
        
BX24.callMethod(
            "sale.paymentitemshipment.list", {
                "select": [
                    "id",
                    "shipmentId",
                    "paymentId",
                    "xmlId",
                    "dateInsert",
                ],
                "filter": {
                    "paymentId": 1025,
                    "shipmentId": 2467,
                },
                "order": {
                    "id": "desc",
                }
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error());
                } else {
                    console.info(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'sale.paymentitemshipment.list',
            [
                'select' => [
                    'id',
                    'shipmentId',
                    'paymentId',
                    'xmlId',
                    'dateInsert',
                ],
                'filter' => [
                    'paymentId' => 1025,
                    'shipmentId' => 2467,
                ],
                'order' => [
                    'id' => 'desc',
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        

Response Handling

HTTP status: 200

{
            "result": {
                "paymentItemsShipment": [
                    {
                        "dateInsert": "2024-04-11T16:59:21+02:00",
                        "id": 1180,
                        "paymentId": 1025,
                        "shipmentId": 2467,
                        "xmlId": "bx_6617fac9afe1e"
                    }
                ]
            },
            "total": 1,
            "time": {
                "start": 1713172802.193215,
                "finish": 1713172802.464073,
                "duration": 0.2708580493927002,
                "processing": 0.018366098403930664,
                "date_start": "2024-04-15T12:20:02+02:00",
                "date_finish": "2024-04-15T12:20:02+02:00"
            }
        }
        

Returned Data

Name
type

Description

result
object

The root element of the response

paymentItemsShipment
sale_payment_item_shipment[]

An array of objects containing information about the selected payment bindings to shipments

total
integer

The total number of records found

time
time

Information about the execution time of the request

Error Handling

HTTP status: 400

{
            "error": 0,
            "error_description": "error"
        }
        

Name
type

Description

error
string

String error code. It may consist of digits, Latin letters, and underscores

error_description
error_description

Textual description of the error. The description is not intended to be shown to the end user in its raw form

Possible Error Codes

Code

Description

200040300010

Insufficient rights to read the elements of the shipment's tabular part

0

Other errors (e.g., fatal errors)

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred, please contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

An internal server error has occurred, please contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

405

ERROR_BATCH_METHOD_NOT_ALLOWED
Method is not allowed for batch usage

The current method is not allowed to be called using batch

400

ERROR_BATCH_LENGTH_EXCEEDED
Max batch length exceeded

The maximum length of parameters passed to the batch method has been exceeded

401

NO_AUTH_FOUND
Wrong authorization data

Invalid access token or webhook code

400

INVALID_REQUEST
Https required

The methods must be called using the HTTPS protocol

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is available only on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user whose access token or webhook was used to call the method lacks permissions

404

ERROR_MANIFEST_IS_NOT_AVAILABLE
Manifest is not available

The manifest is not available

403

insufficient_scope
The request requires higher privileges than provided by the webhook token

The request requires higher privileges than those provided by the webhook token

401

expired_token
The access token provided has expired

The provided access token has expired

403

user_access_error
The user does not have access to the application

The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users

500

PORTAL_DELETED
Portal was deleted

The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning