Record an SLA milestone for a support request reply
curl --request POST \
--url https://app.communicate.so/api/v1/workspaces/{workspaceId}/support-requests/{requestId}/sla/milestones \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"episodeNumber": 123,
"messageId": "<string>",
"observedAt": "2023-11-07T05:31:56Z"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({episodeNumber: 123, messageId: '<string>', observedAt: '2023-11-07T05:31:56Z'})
};
fetch('https://app.communicate.so/api/v1/workspaces/{workspaceId}/support-requests/{requestId}/sla/milestones', 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}/support-requests/{requestId}/sla/milestones"
payload = {
"episodeNumber": 123,
"messageId": "<string>",
"observedAt": "2023-11-07T05:31:56Z"
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){}Workspaces
Record an SLA milestone for a support request reply
Use an explicitly scoped user-bound account bearer credential or an application session. Scope grants are intersected with live membership, role, tenant isolation, agent access and plan limits; a credential does not grant an owner role. Invitation acceptance requires the verified recipient email.
POST
/
workspaces
/
{workspaceId}
/
support-requests
/
{requestId}
/
sla
/
milestones
Record an SLA milestone for a support request reply
curl --request POST \
--url https://app.communicate.so/api/v1/workspaces/{workspaceId}/support-requests/{requestId}/sla/milestones \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"episodeNumber": 123,
"messageId": "<string>",
"observedAt": "2023-11-07T05:31:56Z"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({episodeNumber: 123, messageId: '<string>', observedAt: '2023-11-07T05:31:56Z'})
};
fetch('https://app.communicate.so/api/v1/workspaces/{workspaceId}/support-requests/{requestId}/sla/milestones', 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}/support-requests/{requestId}/sla/milestones"
payload = {
"episodeNumber": 123,
"messageId": "<string>",
"observedAt": "2023-11-07T05:31:56Z"
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){}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:
1Minimum string length:
1Body
application/json
Required range:
x <= 9007199254740991Available options:
first_response, next_response, handoff_pickup, approval_review, verified_resolution Minimum string length:
1Available options:
accepted, failed, uncertain, cancelled Available options:
substantive, clarification, policy_refusal, acknowledgement, routing, handoff, internal_note 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))$Response
Record an SLA milestone for a support request reply