Dillien VDR

Get the buyer side's due-diligence review of a data room: for each file and request with review activity, whether it is marked reviewed, the review comment, and the findings noted on it, each graded POSITIVE, NEUTRAL, NEGATIVE or CRITICAL with a description and a recommendation. Buyers only: where the user is the seller (`stakeholder.party` in list_data_rooms) this returns not found. Items with no review activity are left out; get_request_list and list_data_room_files list every item, and `number` joins them. Long lists come back in pages: when the result has a nextOffset, call again with offset set to it until nextOffset is null.

get_buyer_reviews

Get the request list of a data room: the due-diligence information requests, resolved and unresolved alike, in item-number order. Pass a resolution file's fileId to get_file. Long lists come back in pages: when the result has a nextOffset, call again with offset set to it until nextOffset is null.

get_request_list

Read a file from a data room by id. Text files are returned as text, spreadsheets and documents (PDF, .docx, .xlsx, .pptx) are extracted to text, and images are returned as images. Obtain dataRoomId and fileId from list_data_rooms and list_data_room_files, or a reply attachment's fileId from list_questions.

get_file

List the questions and answers (Q&A) of a data room: questions asked about a file, a request or the room as a whole, each with its posted replies, and `author.party` saying which side wrote each. A question's `target` names what it is about by the same fileId or requestId the other tools use; a question with no `replies` has not been answered. Reply attachments are files: pass their fileId to get_file. Pass targetId to list only the questions about one file or request. Long lists come back in pages: when the result has a nextCursor, call again with cursor set to it, and the same targetId, until nextCursor is null.

list_questions

List the Dillien data rooms the current user can access. Each room carries its id, title, description, `type`, whether it is finished or frozen, and `stakeholder` — which side of that transaction the current user is on (`party`: BUYER or SELLER) and their role in it. `party` is decided per room, so read it per room. Use list_data_room_files with a dataRoomId to browse its folders and files.

list_data_rooms

Browse the folders and files of a single data room, with the room's own context and the current user's side of the transaction. Only items the user may view are returned. The result is a flat list: every entry says whether it is a folder or a file and names its parentFolderId, and all folders come before all files. Long rooms come back in pages: when the result has a nextCursor, call again with cursor set to it until nextCursor is null. A folder's own parent may arrive on a later page, so the folder structure is only complete once it is. Each file includes an id to pass to get_file.

list_data_room_files