---
title: "GetExerciseById"
method: GET
path: "/api/v1/exercises/{exerciseId}"
tags: ["exercises"]
---

# GetExerciseById

`GET /api/v1/exercises/{exerciseId}`

## Path parameters

- `exerciseId` string, required — The unique identifier of the exercise to retrieve.

## Response `200`

Retrive Exercise by id

- object
  - `success` boolean, required — Indicates whether the request was successful
  - `data` object, required — Exercise data
    - `exerciseId` string, required — The id of the exercise
    - `name` string, required — The name of the exercise.
    - `equipments` string[], required — List of equipment required for the exercise.
    - `bodyParts` string[], required — Primary body parts targeted by the exercise.
    - `exerciseType` string, required — Type of exercise (e.g., strength, cardio).
    - `targetMuscles` string[], required — Primary muscles targeted by the exercise.
    - `secondaryMuscles` string[], required — Secondary muscles engaged during the exercise.
    - `keywords` string[], required — Keywords associated with the exercise for searchability.
    - `overview` string, required — Detailed description of the exercise and its benefits.
    - `instructions` string[], required — Step-by-step instructions to perform the exercise.
    - `exerciseTips` string[], required — Tips to perform the exercise safely and effectively.
    - `variations` string[], required — Variations of the exercise to target different muscles or equipment.
    - `relatedExerciseIds` string[] — IDs of related exercises.
    - `videoUrl` string
    - `imageUrl` string
    - `imageUrls` object — An object mapping resolution keys (e.g., 360p, 480p, 720p, 1080p) to URLs for static images of the exercise.
      - `360p` string
      - `480p` string
      - `720p` string
      - `1080p` string

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
- `403` — The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
- `404` — The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.
- `405` — The request method is not supported by the target resource. The server must generate an Allow header field in a 405 response containing a list of the target resource's currently supported methods.
- `409` — This response is sent when a request conflicts with the current state of the server.
- `412` — The requested operation cannot be completed because certain conditions were not met. This typically occurs when a required resource state or version check fails.
- `429` — The user has sent too many requests in a given amount of time ("rate limiting")
- `500` — The server has encountered a situation it does not know how to handle.

---

[API](https://skmtc.dev/ascendapi/apis/exercisedb-v1.md) · [All operations](https://skmtc.dev/ascendapi/apis/exercisedb-v1/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ascendapi/exercisedb-v1/revisions/c5d4e79509c5/schema)