Read everything your organization holds, for retention, eDiscovery and data-loss prevention.
Discovery reads what the servers hold regardless of who in the organization may open it, and leaves nothing out because it was deleted: a deleted record is answered marked deleted, a deleted message keeps its text, and a deleted file still downloads. It changes nothing.
discovery scope. See Tokens.limit and cursor. See Paging.discovery.read, with the path read.To archive an organization, list its resources, read each one's records, messages and files, then each person's direct messages. To stay current afterwards, follow the audit log and re-read what its events name.
https://tensorworks.net/enterprise/v1GET /organization
The organization the token belongs to.
id string name string owner_id string plan string enterprise.created_at string domains string[] curl "https://tensorworks.net/enterprise/v1/organization" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": {
"id": "2f9b…",
"name": "Acme",
"owner_id": "8c1d…",
"plan": "enterprise",
"created_at": "2026-03-02T09:14:07.220Z",
"domains": [
"acme.com"
]
}
}GET /users
Everyone on the organization's team or once on it, in the order they were added. People who were removed stay listed with status removed.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string | null email string name string role string owner, admin, limited-admin, member (full access) or limited.status string active, invited or removed.directory boolean invited_at string joined_at string | null memberships object[] joined_at and left_at (null for the time they are on it now). Someone removed and invited again has several. Their sessions and direct messages are answered only from within these.curl "https://tensorworks.net/enterprise/v1/users" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": [
{
"id": "8c1d…",
"email": "dana@acme.com",
"name": "Dana Ortiz",
"role": "owner",
"status": "active",
"directory": false,
"invited_at": "2026-03-02T09:14:07.220Z",
"joined_at": "2026-03-02T09:14:07.220Z",
"memberships": [
{
"joined_at": "2026-03-02T09:14:07.220Z",
"left_at": null
}
]
}
],
"next_cursor": null
}GET /users/{user}/sessions
The browser sessions a person signed in with while they were on the organization's team, oldest first. {user} is their account id.
Only sessions begun within one of the person's memberships are answered: none from before they joined or after they were removed or left, and none of someone invited who never joined (404).
A session's id is what every audit event carries as session. The IP address and browser are recorded once, at sign-in, so look a session up here to learn where any action came from.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string created_at string method string password, code (a two-factor code), passkey, sso, or registration for a new account.ip string | null user_agent string browser string Chrome.expires_at string ended_at string | null end_reason string | null signed_out, password_changed (a new password ends every other session) or expired.curl "https://tensorworks.net/enterprise/v1/users/$USER/sessions" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": [
{
"id": "b7e4…",
"created_at": "2026-11-10T13:58:02.101Z",
"method": "sso",
"ip": "198.51.100.7",
"user_agent": "Mozilla/5.0 …",
"browser": "Chrome",
"expires_at": "2026-11-17T13:58:02.101Z",
"ended_at": "2026-11-10T18:20:44.019Z",
"end_reason": "signed_out"
}
],
"next_cursor": null
}GET /agents
The organization's AI agents, removed ones too.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string name string connection string oauth for one a person connected, link for one made with an agent link.created_by string | null status string active or removed.created_at string curl "https://tensorworks.net/enterprise/v1/agents" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"GET /projects
Every project, archived ones too. The organization's home, which holds the resources outside any project, is listed first under the organization's own id with home true.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string name string parent_id string | null home boolean archived_at string | null created_at string | null curl "https://tensorworks.net/enterprise/v1/projects" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"GET /resources
Every resource of every project, archived ones too: boards, chatrooms, document repositories, calendars, websites, domains and phone numbers.
kind string board, chat, documents, website, calendar, domains or phones.project string limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string kind string name string project_id string archived_at string | null created_at string curl "https://tensorworks.net/enterprise/v1/resources?kind=chat" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": [
{
"id": "c05e…",
"kind": "chat",
"name": "General",
"project_id": "2f9b…",
"archived_at": null,
"created_at": "2026-03-02T09:14:08.412Z"
}
],
"next_cursor": null
}GET /resources/{resource}
One resource, with the collections it holds and how many records each has, deleted ones counted. Use the collection names with Records.
id, kind, name, project_id, archived_at, created_at collections object curl "https://tensorworks.net/enterprise/v1/resources/$BOARD" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": {
"id": "a91f…",
"kind": "board",
"name": "Roadmap",
"project_id": "5d20…",
"archived_at": null,
"created_at": "2026-04-11T10:02:55.007Z",
"collections": {
"card_events": 214,
"cards": 58,
"columns": 4
}
}
}GET /resources/{resource}/records
One collection of a resource in full, in the collection's own order: a board's cards, columns and card_events, a calendar's events, a phone line's calls and texts, a domain's dns_records, and so on, as the resource lists them.
A record's fields are as they are now. What a field held before its last change is not kept: the audit log records that it changed, by whom and when. For chat, Messages answers the full history of each message instead.
collection string Requiredlimit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string order string created_at string updated_at string deleted boolean fields object curl "https://tensorworks.net/enterprise/v1/resources/$BOARD/records?collection=cards" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": [
{
"id": "6be2…",
"order": "0000019a…",
"created_at": "2026-10-28T08:40:12.530Z",
"updated_at": "2026-11-09T16:22:03.914Z",
"deleted": false,
"fields": {
"title": "Launch checklist",
"column_id": "0c7a…",
"position": "a1",
"assignee_id": "8c1d…"
}
}
],
"next_cursor": null
}GET /resources/{resource}/messages
A chatroom's messages, threads included, oldest first. Each is answered as it was sent, with every edit made since, how it reads now, and whether and when it was deleted.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string id string order string created_at string thread_id string | null sender object user_id for a person or agent_id for an agent, and the name shown when it was sent.body string mentions string[] channel boolean @channel.edits object[] at) and the text it was changed to (body).current_body string body.deleted boolean deleted_at string | null reactions object[] emoji, user_id and at.files object[] hash, name and size. Download each through the conversation’s files.curl "https://tensorworks.net/enterprise/v1/resources/$CHATROOM/messages" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"id": "41aa…",
"order": "0000019a…",
"created_at": "2026-11-10T14:03:22.480Z",
"thread_id": null,
"sender": {
"user_id": "8c1d…",
"agent_id": null,
"name": "Dana Ortiz"
},
"body": "Ship it Friday",
"mentions": [],
"channel": false,
"edits": [
{
"at": "2026-11-10T14:05:10.002Z",
"body": "Ship it Monday"
}
],
"current_body": "Ship it Monday",
"deleted": true,
"deleted_at": "2026-11-10T15:11:45.300Z",
"reactions": [
{
"emoji": "👍",
"user_id": "77b0…",
"at": "2026-11-10T14:04:01.118Z"
}
],
"files": [
{
"hash": "9f86d0…",
"name": "plan.pdf",
"size": 482113
}
]
}GET /resources/{resource}/files
The files a resource holds, deleted ones too: a document repository's files, a board's card attachments, and the files shared in a chatroom.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string hash string order string name string size integer folder_id string | null uploaded_by string | null created_at string deleted boolean curl "https://tensorworks.net/enterprise/v1/resources/$FILES/files" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": [
{
"hash": "9f86d0…",
"order": "0000019a…",
"name": "plan.pdf",
"size": 482113,
"folder_id": null,
"uploaded_by": "8c1d…",
"created_at": "2026-11-10T14:03:20.115Z",
"deleted": false
}
],
"next_cursor": null
}GET /resources/{resource}/files/{hash}/content
The file's bytes, decrypted, exactly as they were uploaded. Unlike the MCP API's file transfers, there is no envelope to open. A deleted file still downloads.
The response is application/octet-stream with the file's size as Content-Length and its name in Content-Disposition. Verify the download against hash, the SHA-256 of its bytes.
curl "https://tensorworks.net/enterprise/v1/resources/$FILES/files/$HASH/content" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN" \
-o plan.pdftest "$(sha256sum plan.pdf | cut -d" " -f1)" = "$HASH"GET /users/{user}/conversations
Whom a person has exchanged direct messages with, among the organization's people and agents. {user} is their account id.
Direct messages are read between two of the organization's own: people on its team now or before, and its agents. A conversation with someone outside the organization is not answered.
Direct messages belong to the two people, not to the organization, so only what they exchanged while both were on its team is answered: the times their memberships overlap. Messages from before either joined, or after either left, are not counted here nor answered below; two who were never on the team at once have no conversation (404).
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string with object type (user or agent) and id.messages integer latest_at string curl "https://tensorworks.net/enterprise/v1/users/$USER/conversations" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"{
"data": [
{
"with": {
"type": "user",
"id": "77b0…"
},
"messages": 42,
"latest_at": "2026-11-10T17:45:09.660Z"
}
],
"next_cursor": null
}GET /conversations/{user}/{other}/messages
The direct messages between two of the organization's people or agents, in either order, answered as a chatroom's messages are: as sent, with edits and deletions.
Only messages sent while both were on the team are answered, each as it stood when the last of those times ended: an edit, deletion or reaction made later is left out.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string curl "https://tensorworks.net/enterprise/v1/conversations/$USER/$OTHER/messages" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"GET /conversations/{user}/{other}/files
The files two people shared in direct messages, answered as a resource's files are. Download one from GET /conversations/{user}/{other}/files/{hash}/content, which answers as File content does. Only files shared while both were on the team are listed or downloaded.
limit integer cursor string next_cursor of the page before, to read on from it.oldest string latest string curl "https://tensorworks.net/enterprise/v1/conversations/$USER/$OTHER/files" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN"curl "https://tensorworks.net/enterprise/v1/conversations/$USER/$OTHER/files/$HASH/content" \
-H "Authorization: Bearer $TENSORWORKS_TOKEN" \
-o shared.pngQuestions or something missing? Contact us.