BI Export API Reference

BI Export lets you export account data for future import to the analytics tools. The data is stored in tables, which are connected using foreign key identifiers (like in a relational database). The following page describes the tables that are present in the export and their columns.

📘
The audit_log file in BI Data Export is limited to a maximum of 10,000,000 rows for the previous 180 days.

Table Parameters

attachment_file — Detailed information about file attachments

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`attachment_file_api_id`	String	API ID of attached file. Can be used to reference file via REST API or in backup	—	—	—	yes
`attachment_file_content_height`	Number	Height of image/video (if applicable)	—	—	—	—
`attachment_file_content_width`	Number	Width of image/video (if applicable)	—	—	—	—
`attachment_file_name`	String	Name of the attachment	—	—	—	yes
`attachment_file_size_bytes`	Number	Size of the attachment in bytes	—	—	—	yes
`user_id`	Number	ID of user who attached the file	—	`user`(`user_id`)	N:1	yes
`when_added`	Date	Date when file was attached	—	—	—	yes

audit_log — User's operations log

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`audit_log_object_id`	Number	ID of referenced object, e.g. task	—	—	—	—
`audit_log_object_title`	String	Name of referenced object, e.g. task	—	—	—	—
`audit_log_object_type`	String	Type of referenced object	—	—	—	—
`audit_log_operation_change_json`	String	JSON description of the change, containing additional attributes. The format depends on type of event	—	—	—	—
`audit_log_operation_origin_json`	String	Deprecated. This attribute will be removed in future versions of the schema. JSON description of the log record origin information	—	—	—	yes
`audit_log_operation_origin_location_country`	String	Country where the event originated	—	—	—	yes
`audit_log_operation_origin_location_state`	String	State where the event originated (if applicable)	—	—	—	—
`audit_log_operation_origin_user_time_zone`	String	Time zone of the event	—	—	—	—
`audit_log_operation_time`	Date	Time of the change in XXX	—	—	—	yes
`audit_log_operation_type`	String	Type of the event	—	—	—	yes
`operator_user_id`	Number	User that made the change (for user-initiated events)	—	`user`(`user_id`)	N:1	—

custom_field — Custom field definitions

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`custom_field_name`	String	Name of custom field	—	—	—	yes
`custom_field_type`	String	Type of custom field. Available values listed here: https://developers.wrike.com/documentation/api/methods/query-custom-fields	—	—	—	yes
`when_added`	Date	Date when the object was added	—	—	—	yes
`when_removed`	Date	Date when the object was removed. 3000-01-01 00:00:00 means that field is NOT deleted	—	—	—	yes

group — User groups

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`group_name`	String	Name of the group	—	—	—	yes
`when_added`	Date	Date when the object was added	—	—	—	yes
`when_removed`	Date	Date when the object was removed. 3000-01-01 00:00:00 means that object is NOT deleted	—	—	—	yes

group_to_user — Users membership in groups

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`is_admin`	Boolean	Whether the user is group admin	—	—	—	yes
`is_inherited`	Boolean	Whether the membership is inherited (meaning that the user is member of the group because he/she is part of another group that contains this group)	—	—	—	yes
`user_id`	Number	ID of the user	yes	`user`(`user_id`)	N:1	yes

recurrence — Information about recurrent tasks

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`recurrence_interval_end_date`	Date	Date when recurrence ends	—	—	—	—
`recurrence_interval_start_date`	Date	Date when recurrence starts	—	—	—	yes
`recurrence_name`	String	Name of the recurrence	—	—	—	yes
`recurrence_occurrence_limit`	Number	Limit of tasks that will be created by this recurrence	—	—	—	—
`recurrence_schedule_frequency`	Number	How often recurrence runs, in units defined by recurrence_schedule_type	—	—	—	yes
`recurrence_schedule_type`	String	Type of recurrence frequency. Possible values: Daily, Weekly, Monthly, Yearly	—	—	—	—
`recurrence_state`	String	State of recurrence. Possible values: Running, RunningInactive, Stopped	—	—	—	—

timelog_category — Timelog categories

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`timelog_category_name`	String	Name of timelog category	—	—	—	yes
`timelog_category_order`	Number	Priority order of the category	—	—	—	yes
`when_added`	Date	Date when the object was added	—	—	—	yes
`when_removed`	Date	Date when the object was removed. 3000-01-01 00:00:00 means that object is NOT deleted	—	—	—	yes
`workflow_id`	Number	Deprecated. This attribute will be removed in next versions of the schema. Always empty	—	`workflow`(`workflow_id`)	—	—

user — Users

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`email_address`	String	User's primary email	—	—	—	yes
`is_deactivated`	Boolean	Whether the user was deactivated	—	—	—	yes
`user_company`	String	Company of the user	—	—	—	—
`user_department`	String	Department of the user	—	—	—	—
`user_first_name`	String	First name	—	—	—	yes
`user_full_name`	String	Full (first and last) name	—	—	—	yes
`user_job_title`	String	Job title	—	—	—	—
`user_last_name`	String	Last name	—	—	—	yes
`user_phone`	String	Phone	—	—	—	—
`user_role`	String	User's role. Possible values: Bot, Owner, Admin, User, External, Collaborator	—	—	—	yes
`when_added`	Date	Date when the object was added	—	—	—	yes
`when_removed`	Date	Date when the object was removed. 3000-01-01 00:00:00 means that object is NOT deleted	—	—	—	yes

work_assignee — Information about task assignees and project owners

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`when_added`	Date	Date when the object was added	—	—	—	yes
`work_id`	Number	ID of project/task that has the assignee	yes	`work_item`(`work_id`)	N:1	yes

work_attachment — Attaches for tasks, projects, folders

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`user_id`	Number	ID of user that has added the first version of the attachment	—	`user`(`user_id`)	N:1	yes
`when_added`	Date	Date when the object was added	—	—	—	yes
`work_id`	Number	ID of work item (folder, project, task) that has the attachment	—	`work_item`(`work_id`)	N:1	yes

work_attachment_to_attachment_file — Versions of task/folder/project attachments

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`attachment_version`	Number	Version of the file	—	—	—	yes
`user_id`	Number	ID of user that has added this version of the attachment	—	`user`(`user_id`)	N:1	yes
`when_added`	Date	Date when the attachment was added in the comment	—	—	—	yes
`work_attachment_id`	Number	ID of the attachment	yes	`work_attachment`(`work_attachment_id`)	—	yes
`work_comment_id`	Number	Comment where the task was attached	—	`work_comment`(`work_comment_id`)	N:1	yes

work_change_revision — Change revisions (status, title, description etc.) of tasks, projects, and folders

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`user_id`	Number	User that made change	—	`user`(`user_id`)	N:1	yes
`when_work_changed`	Date	Date when change was made	—	—	—	yes
`work_id`	Number	ID of work item (folder, project, task) that was changed	—	`work_item`(`work_id`)	N:1	yes

work_comment — Information about comments in tasks, projects and folders

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`user_id`	Number	ID of user that made comment	—	`user`(`user_id`)	N:1	yes
`when_comment_created`	Date	When comment was made	—	—	—	yes
`work_id`	Number	ID of work item (folder, project, task) that was commented	—	`work_item`(`work_id`)	N:1	yes

work_comment_content — Comment contents in tasks, projects, and folders

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`work_comment_text`	String	Comment text	—	—	—	yes

work_comment_to_mention — Mentions of groups and users in comments

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`user_id`	Number	ID of mentioned user in the comment. empty if group was mentioned	yes	`user`(`user_id`)	N:1	—
`work_comment_id`	Number	ID of comment that has the mention	yes	`work_comment`(`work_comment_id`)	N:1	yes

work_custom_field — Custom field values

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`custom_field_value`	String	Custom field value	yes	—	—	—
`work_id`	Number	ID of work item (folder, project, task) that has custom field	yes	`work_item`(`work_id`)	N:1	yes

work_custom_field_history — Change history of task custom fields values

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`custom_field_id`	Number	ID of custom field definition	yes	`custom_field`(`custom_field_id`)	N:1	yes
`new_custom_field_value`	String	New value	—	—	—	—
`old_custom_field_value`	String	Old value	—	—	—	—
`user_resource_id`	Number	ID of user that made the change	yes	`user`(`user_id`)	N:1	yes
`work_id`	Number	ID of work item (folder, project, task) that has custom field	yes	`work_item`(`work_id`)	N:1	yes

work_description — Task/project/folder descriptions in HTML format

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`work_description_html`	String	Description of work item in HTML format: https://developers.wrike.com/documentation/api/datatypes/description	—	—	—	—

work_folder — Detailed information about folders

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`folder_default_workflow_stage_id`	Number	Deprecated. This attribute will be removed in future versions of the schema. Default status for newly created tasks in this folder	—	`workflow_stage`(`workflow_stage_id`)	—	—
`workflow_id`	Number	ID of folder's default workflow	—	`workflow`(`workflow_id`)	—	yes

work_graph — Information about parent and child relationships of projects, folders and tasks

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`when_added`	Date	Date when the relation was added	—	—	—	yes
`work_id`	Number	Parent work id	yes	`work_item`(`work_id`)	N:1	yes

work_item — Base information for tasks, projects, and folders

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`author_user_id`	Number	ID of user which created the item	—	`user`(`user_id`)	N:1	yes
`when_created`	Date	When the item was created	—	—	—	yes
`when_updated_last_time`	Date	Last update time	—	—	—	yes
`work_deleted_state`	String	Whether the item is deleted. Possible values: Actual, Deleted	—	—	—	yes
`work_name`	String	Name of the item	—	—	—	yes
`work_type`	String	Type of the item. Possible values: Folder, Project, Task	—	—	—	yes

work_project — Detailed information about projects

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`project_health_status`	String	Deprecated. This attribute will be removed in future versions of the schema. Was used to represent old project statuses: Green, Yellow, Red, OnHold, Cancelled, Completed	—	—	—	yes
`project_planned_due_date`	Date	Planned project end date	—	—	—	—
`project_planned_start_date`	Date	Planned project start date	—	—	—	—
`when_project_created`	Date	Deprecated. This attribute will be removed in future versions of the schema. date when project was created (similar to when_created in work_item)	—	—	—	yes
`workflow_stage_id`	Number	Status of the project	—	`workflow_stage`(`workflow_stage_id`)	N:1	—
`billing_type_id`	Number	Billing type of the project	—	—	—	—

work_project_to_task — Relationships between projects and tasks (for any level of nesting)

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`work_project_id`	Number	ID of the project	yes	`work_item`(`work_id`)	N:1	yes
`work_task_id`	Number	ID of the task	yes	`work_item`(`work_id`)	N:1	yes

work_space — Information about spaces

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`access_type`	String	Space access type. Possible values: Private, Public, Personal	—	—	—	yes

work_space_user — Information about users of spaces

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`user_id`	Number	Id of user	yes	`user`(`user_id`)	N:1	—
`user_role`	String	Space user role. Possible values: Guest, Member, Manager, UserLeft	—	—	—	yes

work_task — Detailed information about tasks

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`effort`	Number	Planned effort in minutes	—	—	—	—
`effort_mode`	String	Effort type. Possible values: Fulltime, Basic	—	—	—	—
`recurrence_id`	Number	ID of recurrence set on the task	—	`recurrence`(`recurrence_id`)	1:1	—
`task_completed_date`	Date	When task was completed	—	—	—	—
`task_duration_days`	Number	Duration of task in days	—	—	—	—
`task_importance`	String	Task importance. Possible values: Normal, High, Low	—	—	—	yes
`task_planned_due_date`	Date	Planned end date	—	—	—	—
`task_planned_start_date`	Date	Planned start date	—	—	—	—
`task_planning_type`	String	Planning type. Possible values: Planned, Backlog, Milestone	—	—	—	yes
`task_workflow_stage_group`	String	Status group of the task. Possible values: Active, Completed, Deferred, Cancelled	—	—	—	yes
`workflow_stage_id`	Number	Status of the task	—	`workflow_stage`(`workflow_stage_id`)	N:1	yes
`billing_type_id`	Number	Billing type of the task	—	—	—	—

work_task_dependency — Task dependencies

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`predecessor_task_work_id`	Number	ID of predecessor task	yes	`work_task`(`work_id`)	N:1	yes
`successor_task_work_id`	Number	ID of successor task	yes	`work_task`(`work_id`)	N:1	yes
`user_id`	Number	ID of user that created the dependency	—	`user`(`user_id`)	N:1	yes
`when_added`	Date	Date when the dependency was added	—	—	—	yes

work_timelog — Time logged for tasks

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`timelog_category_id`	Number	ID of timelog category	—	`timelog_category`(`timelog_category_id`)	N:1	—
`timelog_datetime`	Date	When time was logged	—	—	—	yes
`timelog_minutes`	Number	Amount of logged time in minutes	—	—	—	yes
`user_id`	Number	User that logged time	—	`user`(`user_id`)	N:1	yes
`when_added`	Date	Date when the timelog was added	—	—	—	yes
`work_id`	Number	Task that has the timelog	—	`work_task`(`work_id`)	N:1	yes

work_timelog_comment — Comments for timelogs

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`timelog_comment_text`	String	Timelog comment	—	—	—	—

work_workflow_stage_history — History of task status changes

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`new_workflow_stage_id`	Number	New status	—	`workflow_stage`(`workflow_stage_id`)	N:1	yes
`old_workflow_stage_id`	Number	Old status	—	`workflow_stage`(`workflow_stage_id`)	N:1	yes
`user_id`	Number	User who changed status	yes	`user`(`user_id`)	N:1	yes
`work_id`	Number	Task ID	yes	`work_item`(`work_id`)	N:1	yes

workflow — Workflows

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`is_strict_workflow`	Boolean	Whether the workflow has locked transtitions	—	—	—	yes
`when_added`	Date	Date when the object was added	—	—	—	yes
`when_removed`	Date	Date when the object was removed. 3000-01-01 00:00:00 means that object is NOT deleted	—	—	—	yes
`workflow_name`	String	Workflow name	—	—	—	yes

workflow_stage — Workflow statuses

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`when_added`	Date	Date when the stage was added	—	—	—	yes
`when_removed`	Date	Date when the stage was removed. 3000-01-01 00:00:00 means that stage is NOT deleted	—	—	—	yes
`workflow_id`	Number	ID of workflow	—	`workflow`(`workflow_id`)	N:1	yes
`workflow_stage_color`	String	Color of the status. Possible values described here: https://developers.wrike.com/documentation/api/methods/query-workflows	—	—	—	yes
`workflow_stage_group`	String	Group of the status. Possible values described here: https://developers.wrike.com/documentation/api/methods/query-workflows	—	—	—	yes
`workflow_stage_name`	String	Name of the status	—	—	—	yes
`workflow_stage_order`	Number	Order of the status	—	—	—	yes

work_task_flexible_effort — Flexible effort for task

Column name	Type	Description	Primary key	Foreign key	Cardinality	Required
`user_id`	Number	User id	—	—	—	—
`date`	Date	-	—	—	—	—
`effort_minutes`	Number	-	—	—	—	—