Get Information About Attached File disk.attachedObject.get
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
diskWho can execute the method: a user with "Read" access permission for the required file
The method disk.attachedObject.get returns information about the attached file.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the file attachment record, which is the link connecting the disk file with other objects. To obtain the connection identifier, use methods that return attached files. For example, if the file is attached to a task, you can find out the connection identifier using the tasks.task.get method. |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":495}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/disk.attachedObject.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":495,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/disk.attachedObject.get
try
{
const response = await $b24.callMethod(
'disk.attachedObject.get',
{
id: 495,
}
);
const result = response.getData().result;
console.log('Retrieved object:', result);
processResult(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'disk.attachedObject.get',
[
'id' => 495
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error retrieving attached object: ' . $e->getMessage();
}
BX24.callMethod(
'disk.attachedObject.get',
{
id: 495
},
function (result) {
if (result.error()) {
console.error(result.error());
} else {
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'disk.attachedObject.get',
[
'id' => 495
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"ID": "495",
"OBJECT_ID": "8903",
"MODULE_ID": "tasks",
"ENTITY_TYPE": "tasks_task",
"ENTITY_ID": "3845",
"CREATE_TIME": "2025-12-23T10:31:24+02:00",
"CREATED_BY": "1269",
"DOWNLOAD_URL": "https://test.bitrix24.com/bitrix/tools/disk/uf.php?attachedId=495&auth[auth]=d78a4a690000071b006e2cf2000004f5000007746b9ad166e1b9bd67b8848714afc5a7&action=download&ncc=1",
"NAME": "Picture.png",
"SIZE": "52486"
},
"time": {
"start": 1766489404,
"finish": 1766489404.720053,
"duration": 0.72005295753479,
"processing": 0,
"date_start": "2025-12-23T11:30:04+02:00",
"date_finish": "2025-12-23T11:30:04+02:00",
"operating_reset_at": 1766490004,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object containing data about the attached file |
|
ID |
Identifier of the file attachment record |
|
OBJECT_ID |
Identifier of the file |
|
MODULE_ID |
Module where the file is used |
|
ENTITY_TYPE |
Type of the linked object |
|
ENTITY_ID |
Identifier of the item to which the file is attached |
|
CREATE_TIME |
Time of the attachment creation |
|
CREATED_BY |
Identifier of the user who attached the file |
|
DOWNLOAD_URL |
Link to download the file |
|
NAME |
Name of the file |
|
SIZE |
Size of the file in bytes |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error":"ERROR_NOT_FOUND",
"error_description":"Could not find entity with id `X`"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
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 |
Value |
|
|
Could not find entity with id |
Attached file with the specified |
|
|
Access denied |
Insufficient rights to read the attached file |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- How to Create a Comment in a Task and Attach a File
- How to Create a Task with an Attached File
- How to Upload a File to a Task