Set or clear the short-lived visibility proof for an accessible conversation
curl --request POST \
--url https://app.communicate.so/api/v1/workspaces/{workspaceId}/member-notifications/visibility \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"conversationId": "<string>",
"visible": true
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({conversationId: '<string>', visible: true})
};
fetch('https://app.communicate.so/api/v1/workspaces/{workspaceId}/member-notifications/visibility', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.communicate.so/api/v1/workspaces/{workspaceId}/member-notifications/visibility"
payload = {
"conversationId": "<string>",
"visible": True
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"ok": true,
"visibleUntil": "2023-11-07T05:31:56Z"
}Notifications
Set or clear the short-lived visibility proof for an accessible conversation
Use an explicit notifications:read or notifications:write account grant, or an application session. Devices belong to the authenticated user; workspace settings retain live membership and agent access. Member summaries require the live owner/admin role. Cookie writes still require a trusted Origin. Provider acceptance alone does not establish device delivery.
POST
/
workspaces
/
{workspaceId}
/
member-notifications
/
visibility
Set or clear the short-lived visibility proof for an accessible conversation
curl --request POST \
--url https://app.communicate.so/api/v1/workspaces/{workspaceId}/member-notifications/visibility \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"conversationId": "<string>",
"visible": true
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({conversationId: '<string>', visible: true})
};
fetch('https://app.communicate.so/api/v1/workspaces/{workspaceId}/member-notifications/visibility', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.communicate.so/api/v1/workspaces/{workspaceId}/member-notifications/visibility"
payload = {
"conversationId": "<string>",
"visible": True
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"ok": true,
"visibleUntil": "2023-11-07T05:31:56Z"
}Authorizations
accountBeareraccountSessionlocalAccountSession
Opaque user-bound ca_ account credential. Each request checks live account scopes, verified email, expiry, revocation and the issuer session. Not a workspace ck_ key or OAuth access token.
Path Parameters
Minimum string length:
1Body
application/json
Response
Set or clear the short-lived visibility proof for an accessible conversation
Pattern:
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$