---
title: "Get technical service dependencies"
method: GET
path: "/service_dependencies/technical_services/{id}"
tags: ["Service Dependencies"]
---

# Get technical service dependencies

`GET /service_dependencies/technical_services/{id}`

Get all immediate dependencies of any technical service.
Technical services are also known as `services`.

For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#services)

Scoped OAuth requires: `services.read`

## Path parameters

- `id` string, required

## Headers

- `Accept` string, required
- `Content-Type` 'application/json', required

## Response `200`

An array of service relationships.

- object
  - `relationships` object[] — List of all the technical service's dependencies
    - `supporting_service` object — The reference to the service that supports the technical service.
      - `id` string
      - `type` string
    - `dependent_service` object — The reference to the service that is dependent on the technical service.
      - `id` string
      - `type` string
    - `id` string
    - `type` string

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `401` — Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.

---

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