---
title: "Where to fetch the bytes of a file"
method: POST
path: "/disk.sync.content.get"
tags: ["disk"]
---

# Where to fetch the bytes of a file

`POST /disk.sync.content.get`

Turns the download identifier of a card into a link to the content of that file.

The method answers with a link and never with bytes: `url` is fetched with an ordinary GET
and needs no header, no session and no scope beyond the one this call was already made
with. `expiresAt` says when the link stops being accepted; ask for a new one rather than
storing this one. A link is cheap to ask for again, and asking again is what re-checks the
rights - so a client planning a long queue of downloads should ask shortly before it
fetches rather than collect links in advance.

The rights of the caller are checked twice: once here, and once more when the link is
presented. A right taken away in between is a refused download, not an open one.

ACCESS_DENIED is the single answer to everything an identifier can be wrong about - a file
the caller does not see, a file whose content this portal calls unavailable, an identifier
of a kind the portal does not serve, an identifier that was never issued at all. They are
one answer on purpose: the identifier is opaque, and telling those cases apart would let
the objects of a portal be probed through the refusals.

OBJECT_NOT_FOUND says something narrower and is never a way to learn whether an object
exists: it is answered only for an object the caller does see and whose content is gone
from the portal.

## Request body

- object
  - `downloadId` string, required — The identifier the card of the object carries in its own downloadId, passed back unchanged. It is opaque: it is neither built by the client nor read by it, and a card that offers no content carries no such field to pass back.

## Response `200`

The answer of the method.

- object
  - `result` object
    - `item` BitrixDiskContentlinkdto
      - `url` string
      - `expiresAt` string, date-time

## Other responses

- `400` — FEATURE_NOT_SUPPORTED, BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
- `403` — ACCESS_DENIED
- `404` — OBJECT_NOT_FOUND
- `429` — BITRIX_REST_V3_EXCEPTION_RATELIMITEXCEPTION

## Changes

- **2026-09-29** `f6be0a558c33` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/bitrix24/apis/bitrix24-rest-v3-api/changes/disk.sync.content.get/post.md)

---

[API](https://skmtc.dev/bitrix24/apis/bitrix24-rest-v3-api.md) · [All operations](https://skmtc.dev/bitrix24/apis/bitrix24-rest-v3-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bitrix24/apis/bitrix24-rest-v3-api/revisions/f6be0a558c33?raw)