Get Payment Binding by Id sale.paymentItemShipment.get

Scope: sale

Who can execute the method: administrator

This method retrieves the payment binding to the shipment by ID.

Method Parameters

Required parameters are marked with *

Name `type`	Description
id* `sale_payment_item_shipment.id`	Identifier of the payment binding to the shipment

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":1183}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.paymentitemshipment.get

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":1183,"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/sale.paymentitemshipment.get

try
        {
        	const response = await $b24.callMethod(
        		"sale.paymentitemshipment.get",
        		{
        			"id": 1183
        		}
        	);
        	
        	const result = response.getData().result;
        	console.info(result);
        }
        catch( error )
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'sale.paymentitemshipment.get',
                    [
                        'id' => 1183,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            // Your logic for processing data
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error getting payment item shipment: ' . $e->getMessage();
        }

BX24.callMethod(
            "sale.paymentitemshipment.get",
            {
                "id": 1183
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error());
                } else {
                    console.info(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'sale.paymentitemshipment.get',
            [
                'id' => 1183
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP status: 200

{
            "result": {
                "paymentItemShipment": {
                    "dateInsert": "2024-04-15T10:53:42+02:00",
                    "id": 1183,
                    "paymentId": 1025,
                    "shipmentId": 2471,
                    "xmlId": "myXmlId"
                }
            },
            "time": {
                "start": 1713171284.974848,
                "finish": 1713171285.256904,
                "duration": 0.2820558547973633,
                "processing": 0.035675048828125,
                "date_start": "2024-04-15T11:54:44+02:00",
                "date_finish": "2024-04-15T11:54:45+02:00"
            }
        }

Returned Data

Name `type`	Description
result `object`	Root element of the response
paymentItemShipment `sale_payment_item_shipment`	Information about the payment binding to the shipment
time `time`	Information about the request execution time

Error Handling

HTTP status: 400

{
            "error": 201240400001,
            "error_description": "payment item does not exist"
        }

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
`201240400001`	Payment binding to the shipment not found
`200040300010`	Insufficient permissions to read payment binding data
`100`	Parameter `id` not specified
`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

Update Payment Link to Shipment

Get List of Links

Get Payment Binding by Id sale.paymentItemShipment.get

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning