---
title: "Bind the matching SLA policy to a support request"
method: POST
path: "/workspaces/{workspaceId}/support-requests/{requestId}/sla/bind"
tags: ["Workspaces"]
---

# Bind the matching SLA policy to a support request

`POST /workspaces/{workspaceId}/support-requests/{requestId}/sla/bind`

## Request

- Base URL: `https://app.communicate.so/api/v1`
- URL: `https://app.communicate.so/api/v1/workspaces/{workspaceId}/support-requests/{requestId}/sla/bind`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `__Secure-better-auth.session_token`
  - API key in cookie `better-auth.session_token`

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.

## Path parameters

- `workspaceId` string, required
- `requestId` string, required

## Request body

- BindSupportRequestSlaRequest
  - `priority` string, required
  - `teamId` string
  - `observedAt` string, date-time

## Response `200`

Bind the matching SLA policy to a support request

- BindSupportRequestSlaResponse

## Other responses

- `400`: Invalid request, timezone, resource association or confirmation.
- `401`: Missing, invalid, expired or revoked account credential or application session.
- `403`: Required account scope, live verified identity, membership or role permission is missing.
- `404`: Workspace or addressed resource is not visible to this member.
- `500`: Unexpected server failure.
- `503`: Authorization service temporarily unavailable.

---

[API](https://skmtc.dev/communicate/apis/communicate-public-rest-api-2.md) · [All operations](https://skmtc.dev/communicate/apis/communicate-public-rest-api-2/llms.txt) · [OpenAPI document](https://skmtc.dev/communicate/apis/communicate-public-rest-api-2/revisions/db6be3d36733?raw)