---
title: "List Labels"
method: GET
path: "/v1/labels"
tags: ["Labels"]
---

# List Labels

`GET /v1/labels`

## Request

- Base URL: `https://api.linkedmash.com`
- URL: `https://api.linkedmash.com/v1/labels`
- Auth: one of:
  - OAuth 2 (client credentials, token URL `https://api.linkedmash.com/auth/oauth/token`, scopes: `library:read`)
  - HTTP bearer
  - API key in header `linkedmash-api-key`

List all labels for the authenticated user.

GET /v1/labels returns every label on the authenticated account, each with its numeric id, label_name and a metadata object. Labels are LinkedMash's tagging layer over saved posts; the ids returned here are what you pass as label_id when adding or removing labels in bulk.

This is the call to make before any labelling workflow, because it tells you which names already exist. Adding by label_name will create a label that is not in this list, so reading first is how you avoid ending up with 'AI', 'ai' and 'A.I.' as three separate labels.

## Response `200`

Successful response.

- object
  - `status` boolean, required
  - `data` object[], required
    - `id` integer, required
    - `label_name` string, required
    - `metadata` object, required

## Other responses

- `401`: Unauthorized. The Authorization header is missing or the key is not a valid LinkedMash API key. Create or rotate keys on the API page in your LinkedMash settings.
- `500`: Server Error. Something failed on our side. The body carries message "Failed to list all user labels". Retry once; if it persists the request is not the problem.

---

[API](https://skmtc.dev/linkedmash/apis/linkedmash-api.md) · [All operations](https://skmtc.dev/linkedmash/apis/linkedmash-api/llms.txt) · [OpenAPI document](https://skmtc.dev/linkedmash/apis/linkedmash-api/revisions/eef45d6fbea3?raw)