Get Epic Fields by Its Identifier tasks.api.scrum.epic.get
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
taskWho can execute the method: any user with access to Scrum
The method retrieves the values of the epic fields by its identifier id.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Epic identifier. You can get the identifiers of epics using the method |
|
withFiles |
Whether to return the epic files in the To retrieve an epic without files, pass |
Attention
The method treats the strings "false" and "N" in withFiles as true and returns the files. Pass a boolean false in a JSON request, or 0
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/tasks.api.scrum.epic.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":1,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/tasks.api.scrum.epic.get
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type EpicGetResult = {
id: number
groupId: number
name: string
description: string
createdBy: number
modifiedBy: number
color: string
files: Record<string, unknown>
}
try {
const response = await $b24.actions.v2.call.make<EpicGetResult>({
method: 'tasks.api.scrum.epic.get',
params: {
id: 1,
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info(result.id, result.name, result.color)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function getEpic() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'tasks.api.scrum.epic.get',
params: {
id: 1,
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info(result.id, result.name, result.color)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', getEpic)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.tasks.api.scrum.epic.get(
bitrix_id=1,
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$epicId = 1;
$response = $b24Service
->core
->call(
'tasks.api.scrum.epic.get',
[
'id' => $epicId,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting epic: ' . $e->getMessage();
}
const epicId = 1;
BX24.callMethod(
'tasks.api.scrum.epic.get',
{
id: epicId,
},
function(res)
{
console.log(res);
}
);
require_once('crest.php');
$result = CRest::call(
'tasks.api.scrum.epic.get',
[
'id' => 1
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "tasks.api.scrum.epic.get", b24.Params{
"id": 1,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("tasks.api.scrum.epic.get: %w", err)
}
// The response arrives as json.RawMessage — unmarshal it
// into a struct matching the response shape shown below on this page.
fmt.Printf("%s\n", res.Result)
Response Handling
HTTP status: 200
{
"result": {
"id": 2,
"groupId": 2,
"name": "User Registration",
"description": "Login form, registration, and password recovery",
"createdBy": 1,
"modifiedBy": 1,
"color": "#69dafc",
"files": {
"ID": "60",
"ENTITY_ID": "TASKS_SCRUM_EPIC",
"FIELD_NAME": "UF_SCRUM_EPIC_FILES",
"USER_TYPE_ID": "disk_file",
"XML_ID": null,
"SORT": "100",
"MULTIPLE": "Y",
"MANDATORY": "N",
"SHOW_FILTER": "N",
"SHOW_IN_LIST": "N",
"EDIT_IN_LIST": "N",
"IS_SEARCHABLE": "N",
"SETTINGS": {
"IBLOCK_ID": null,
"SECTION_ID": null,
"UF_TO_SAVE_ALLOW_EDIT": false
},
"USER_TYPE": {
"USER_TYPE_ID": "disk_file",
"CLASS_NAME": "Bitrix\\Disk\\Uf\\FileUserType",
"DESCRIPTION": "File (Drive)",
"BASE_TYPE": "int",
"TAG": [
"DISK FILE ID",
"DOCUMENT ID"
]
},
"VALUE": [
6
],
"ENTITY_VALUE_ID": 2,
"VALUE_EXISTS": true,
"VALUE_RAW": "a:1:{i:0;i:6;}",
"CUSTOM_DATA": {
"PHOTO_TEMPLATE": ""
},
"EDIT_FORM_LABEL": "UF_SCRUM_EPIC_FILES",
"TAG": "DOCUMENT ID"
}
},
"time": {
"start": 1790263942,
"finish": 1790263942.418237,
"duration": 0.4182369709014893,
"processing": 0,
"date_start": "2026-09-24T18:32:22+03:00",
"date_finish": "2026-09-24T18:32:22+03:00",
"operating_reset_at": 1790264542,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Epic data (Detailed Description) |
|
time |
Information about the request execution time |
result Object
|
Name |
Description |
|
id |
Epic identifier |
|
groupId |
Identifier of the Scrum to which the epic belongs |
|
name |
Epic name |
|
description |
Epic description |
|
createdBy |
Identifier of the user who created the epic |
|
modifiedBy |
Identifier of the user who last modified the epic. |
|
color |
Epic color |
|
files |
Epic files as the |
files Object
The file data you need is in the VALUE field. The other fields of the object contain internal metadata describing the custom field.
|
Name |
Description |
|
VALUE |
Identifiers of the files attached to the epic. These are attachment identifiers, not Drive file identifiers: you can retrieve the file name, download link, and Drive file identifier An empty array if there are no files |
|
VALUE_EXISTS |
Returned with the value |
|
FIELD_NAME |
Custom field code, always |
|
USER_TYPE_ID |
Custom field type, always |
|
ENTITY_VALUE_ID |
Epic identifier |
|
VALUE_RAW |
The |
The remaining fields describe the settings of the UF_SCRUM_EPIC_FILES custom field itself. They are the same for all epics and do not depend on the attached files:
|
Name |
Description |
|
ID |
Custom field identifier |
|
ENTITY_ID |
Object the field belongs to, always |
|
XML_ID |
External code of the field. |
|
SORT |
Field sort order |
|
MULTIPLE |
Whether the field accepts multiple values, always |
|
MANDATORY |
Whether the field is required, always |
|
SHOW_FILTER, SHOW_IN_LIST, EDIT_IN_LIST, IS_SEARCHABLE |
Field display settings in the interface, |
|
SETTINGS |
Field settings: |
|
USER_TYPE |
Field type description: |
|
CUSTOM_DATA |
Additional data of the field type |
|
EDIT_FORM_LABEL |
Field label in the edit form |
|
TAG |
Field type tag, |
Error Handling
HTTP status: 400
{
"error": "0",
"error_description": "Access denied"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Epic not found |
An epic with this |
|
|
|
Access denied |
The user has no access to the tasks of the group the epic belongs to |
|
|
|
Could not find value for parameter |
The |
|
|
|
Invalid value {stringValue} to match with parameter {id}. Should be value of type int. |
A non-numeric value was passed in |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |