---
title: "Resolve a Service Record"
method: POST
path: "/service-records/{recordId}/resolve"
tags: ["Service Records"]
---

# Resolve a Service Record

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

Mark a service record as resolved. Use this endpoint to update the status of an open ticket to indicate that the issue has been addressed.

## Request body

- ResolveServiceRecordRequest
  - `solution` string, required — The details explaining the solution.
  - `resolutionStatus` string, required — The relevant status for this resolution (Closed, Merged, etc).
  - `closureInformation` string, required — The information categorizing how the service record was closed.
  - `shareWithRequestUser` boolean — Specifies whether to send an email notification about the note with the service record's requester user.

## Response `200`

Service record is successfully resolved.

## Other responses

- `400` — The request was invalid or cannot be served
- `401` — Authentication information is missing or invalid
- `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/versions/38a43a1b2981/schema)