Skip to main content
GET
Search CoworkerDataFiles
A CoworkerDataFile is a file attached to a customer’s record. Files can be kept internal or shared with the customer on the Members Portal. When a file is shared (AvailableToUser = true), the customer receives an email notification and can view or download the file from the Files tab under My Activity on the Members Portal. You can request a digital signature (RequestDigitalSignature = true) — once the customer signs the document, a signed copy is automatically stored in SignedFileDataFileName. The notes in Description are included in the email notification sent to the customer. Supported formats include .pdf, .docx, .xlsx, .jpg, .png, and other common types (max 10 MB). Files can be linked to a document template, a proposal, or a coworker contract via the respective GUID fields.

Authentication

This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header. The authenticated user must be a full unrestricted administrator or have the CoworkerDataFile-List role.

Query Parameters

Pagination & Sorting

integer
default:"1"
The page number to retrieve.
integer
default:"25"
The number of records per page.
string
The property name to sort results by (e.g. Name, CreatedOn).
integer
Sort direction. 0 for ascending, 1 for descending.

Filters

integer
Filter by location ID.
string
Filter by location name.
integer
Filter by iD of the customer this file belongs to.
string
Filter by full name of the customer.
string
Filter by record type of the customer (Individual or Company).
string
Filter by company name of the customer.
string
Filter by billing name of the customer.
string
Filter by name of the file or document.
string
Filter by notes included in the email notification sent to the customer when the file is shared.
boolean
Filter by whether the file is shared with the customer and visible on the Members Portal.
boolean
Filter by whether to request a digital signature from the customer.
string
Filter by name of the uploaded file.
string
Filter by uRL of a new file to upload (replaces the existing file).
boolean
Filter by set to true to remove the existing uploaded file.
string
Filter by name of the signed copy of the document, created automatically after the customer signs it.
string
Filter by uRL of a new signed file to upload (replaces the existing signed copy).
boolean
Filter by set to true to remove the existing signed copy.
string
Filter by file extension (e.g. pdf, docx, jpg).
boolean
Filter by whether the customer has been billed for this file.
boolean
Filter by whether the customer has signed this document.
string
Filter by identifier used by the digital signature provider to track this document.
string
Filter by gUID of the document template used to generate this file.
string
Filter by email address to notify when the customer signs the document.
string
Filter by gUID of the proposal linked to this file.
string
Filter by gUID of the coworker contract linked to this file.

Range Filters

string
Filter records created on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records created on or before this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or before this date. Format: YYYY-MM-DDTHH:mm.

Code Examples

Simple listing

Filtering by Name

Range filters

Response

200

CoworkerDataFile[]
The list of CoworkerDataFile records matching the query. See the Get one CoworkerDataFile endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each CoworkerDataFile. The following fields are not populated in the Records[] response: Description, AvailableToUser, RequestDigitalSignature.To get all fields, fetch the full record using the Get one CoworkerDataFile endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.
integer
Current page number.
integer
Number of records per page.
string
The field used for sorting.
integer
The sort direction (0 = ascending, 1 = descending).
integer
Index of the first item on the current page.
integer
Index of the last item on the current page.
integer
Total number of matching records across all pages.
integer
Total number of pages.
boolean
Whether there is a next page of results.
boolean
Whether there is a previous page of results.
Example Response