---
title: "Send a Message from a Service Record"
method: POST
path: "/service-records/{recordId}/message"
tags: ["Service Records"]
---

# Send a Message from a Service Record

`POST /service-records/{recordId}/message`

Send an email notification directly from a specific service record to an end user or agent.

## Request body

- ServiceRecordMessage
  - `recipientUserIds` string[], required — The unique SysAid ID of the users and/or groups to receive this message. The ID must be prefixed with a "g" (group) or a "u" (user) according to its type. Example "u12345","g67890"
  - `subject` string, required — The subject of the message.
  - `body` string, required — The body of the message
  - `ccUserIds` string[] — The unique SysAid ID of the users and/or groups to CC on this message. The ID must be prefixed with a "g" (group) or a "u" (user) according to its type. Example "u12345","g67890"

## Response `200`

Message successfully added to the service record

## Other responses

- `400` — The request was invalid or cannot be served
- `401` — Authentication information is missing or invalid
- `403` — The server understood the request but refuses to authorize it
- `404` — The specified resource was not found
- `409` — The request could not be completed due to a conflict with the current state of the resource. This typically occurs when attempting to create a duplicate resource, update a resource that has been modified by another process, or when business rules prevent the operation.

---

[API](https://skmtc.net/sysaid/apis/sysaid-public-api.md) · [All operations](https://skmtc.net/sysaid/apis/sysaid-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sysaid/sysaid-public-api/revisions/38a43a1b2981/schema)