send message to dooray messenger

find dooray calendars

find dooray events of calendars

register dooray events on a calendar

find dooray account members by name or userCode

find dooray account members by id

List Dooray projects accessible to the token or get one project by ID. A /task/{projectId}/{postId} URL provides projectId directly, while a legacy /project/tasks/{postId} URL contains only postId and requires project discovery. find_projects requires type, scope, and state; use page and size to exhaust every relevant filter combination because one page is not proof that a project or post is inaccessible. find_project requires projectId.

Find Dooray task posts in one project or a comma-separated set of accessible project IDs. Parse the URL first: /task/{projectId}/{postId} provides both IDs, while legacy /project/tasks/{postId} provides only postId and requires project discovery with dooray_project. Query the known or candidate project IDs with size up to 100 and continue through pages until the returned post ID matches; a lookup under one wrong project ID or only the first page does not prove that the post is unavailable. The matching post response contains the task body, so do not call dooray_post_logs unless comments or activity were explicitly requested. When the post has fileIdList, treat every ID as a downloadable body file, commonly an inline image, and call dooray_post_file_download with the same verified projectId and postId. Always try that direct download even if dooray_post_files is empty or returns AUTH_FORBIDDEN_ERROR.

find comments and activity logs of a Dooray post

find a specific comment or activity log of a Dooray post

add a comment to a Dooray post

update a comment or activity log of a Dooray post

List regular attachments only. This is not an availability check for inline body images in dooray_posts.fileIdList. The endpoint can be empty or return AUTH_FORBIDDEN_ERROR while direct dooray_post_file_download calls still succeed, so never use this result alone to conclude that body files cannot be read.

Download a Dooray post file by fileId through authenticated redirects to a local temporary directory. Authorization is forwarded only to the configured API origin and the HTTPS file-api.dooray.com download service; arbitrary redirect origins receive no Dooray token. Use this for every ID from the matching dooray_posts.fileIdList, including inline body images, with the same verified projectId and postId; it also supports regular attachment file IDs. dooray_post_files is not a prerequisite, and an empty result or AUTH_FORBIDDEN_ERROR from that separate endpoint does not imply that this direct download will fail. On success, the result contains filePath, fileName, mimeType, size, and temporary; inspect filePath with an appropriate local image viewer or document parser. A fetch failure or timeout is transient and must not be reported as a permission denial; retry or report the transport problem separately. Only report a body file as forbidden or missing when this direct request returns a terminal Dooray response such as 403 or 404 with the verified projectId, postId, and fileId.

get os time date