List the external resources linked into a workspace
Returns the provider resources that have been linked or mounted into the workspace. Requires both the `resources:read` and `integrations:read` workspace permissions.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
workspaceId*stringSuccess
application/json- response
data*array<>curl -X GET 'https://api.snoze.dev/v1/workspaces/string/integrations/resources'{ "data": [ { "id": "string", "workspaceId": "string", "connectionId": "string", "provider": "string", "externalType": "string", "externalId": "string", "name": "string", "surfaceKind": "generic", "ownership": "external", "capabilities": [ "browse" ], "mimeType": "string", "canonicalUrl": "string", "parentExternalId": "string", "revision": "string", "providerCreatedAt": "string", "providerModifiedAt": "string", "metadata": {}, "syncStatus": "current", "lastSyncedAt": "string", "createdAt": "string", "updatedAt": "string" } ]}Materialize one level of a mounted folder's children
Expands a mounted provider folder by creating native workspace items for one level of its provider children and archiving children that have disappeared upstream, then drops the workspace's cached provider content so later reads are fresh. Requires the `integrations:read`, `integrations:write`, `resources:read`, and `resources:write` workspace permissions because the refresh reads provider content and mutates workspace items. Naturally idempotent per child: re-running is the refresh path rather than a duplicate import.
Read the content of a linked external resource
Fetches a linked resource's current content from its provider and returns it in the format the provider exposes, along with its revision, whether it is read-only, and a fallback URL when Snoze cannot render it. Requires the `resources:read` workspace permission, re-checked on every request. Content is read as the caller: a resource on a workspace-shared install is readable by any member, while one linked through a teammate's personal OAuth account is readable only by that teammate or by a caller whose own connected account can reach it — anyone else receives `resource_access_denied` (403) before any provider call. Content is served from a short-lived encrypted mirror scoped to the credential used, so a response may be up to a few minutes stale while it refreshes.