---
title: "List all attack path types"
method: GET
path: "/api/v2/attack-path-types"
tags: ["Attack Paths", "Enterprise"]
---

# List all attack path types

`GET /api/v2/attack-path-types`

Lists all possible attack path types

## Query parameters

- `sort_by` string — Sort by column. Can be used multiple times; prepend a hyphen for descending order. See parameter description for details about which columns are sortable.
- `finding` string — Filter results by column string value. Valid filter predicates are `eq`, `~eq`, `neq`.

## Response `200`

OK

- object
  - `data` string[]

## Other responses

- `400` — **Bad Request** This could be due to one of the following reasons: - JSON payload is missing or malformed - Path or query parameters are missing or invalid/malformed - The data sent is not valid (ex- sending a `string` in an `integer` field)
- `401` — **Unauthorized** This endpoint failed an authentication requirement. Either the client tried to access a protected endpoint without being authenticated, or an auth validation failed (ex- invalid credentials or expired token).
- `404` — **Not Found** This error typically comes from operations where a valid ID was passed to the request to look up an entity but the entity could not be found.
- `429` — **Too Many Requests** The client has sent too many requests within a certain time window and tripped the rate limiting middleware.
- `500` — **Internal Server Error** This is usually the result of either an unexpected database or application error. The client may try modifying or resending the request, but the error is likely not related to the client doing something wrong.

## Changes

- **2026-04-01** `40bf219eced6` — 1 breaking
  - added the pattern `^((eq|~eq|neq):)?[^:]+$` to the `query` request parameter `finding`
- **2026-04-01** `6aaeba6ecdc5` — 1 info
  - removed the pattern `^((eq|~eq|neq):)?[^:]+$` from the `query` request parameter `finding`
- **2026-04-01** `674e0a229e8a` — 1 breaking
  - added the pattern `^((eq|~eq|neq):)?[^:]+$` to the `query` request parameter `finding`
- **2026-01-12** `a426ff0abf8f` — 1 info
  - removed the pattern `^((eq|~eq|neq):)?[^:]+$` from the `query` request parameter `finding`

[Change history](https://skmtc.dev/specterops/apis/bloodhound-api/changes/api/v2/attack-path-types/get.md)

---

[API](https://skmtc.dev/specterops/apis/bloodhound-api.md) · [All operations](https://skmtc.dev/specterops/apis/bloodhound-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/specterops/bloodhound-api/revisions/6d4b33f1714e/schema)