---
title: "Retrieve the incoming references for an item with the provided ID."
method: GET
path: "/authoring/v1/references/incoming/{classification}/{id}"
tags: ["Authoring reference"]
---

# Retrieve the incoming references for an item with the provided ID.

`GET /authoring/v1/references/incoming/{classification}/{id}`

Use the `/references/incoming/{classification}/{id}` endpoint to retrieve the incoming references for an item with the provided ID.

 ### Examples: ###
 #### A simple lookup of the incoming references for one item ####

 ##### Request: #####
 ~~~
     "{baseURL}/authoring/v1/references/incoming/content-type/cad2e430-beed-40d0-bb57-1c86c4f912c0"
 ~~~
 ##### Response: #####
 ~~~
 {
    "offset": 0,
    "limit": 200,
    "href": "/authoring/v1/references/incoming/content-type/cad2e430-beed-40d0-bb57-1c86c4f912c0?offset=0&limit=200",
    "items": [
      {
        "id": "2107a014-51f7-4161-96e2-d8eac6ad7dd9",
        "classification": "content"
      },
      {
        "id": "367a067a-d49e-4a40-b16a-18442fd3b6ba",
        "classification": "content"
      }
    ]
}
 ~~~
 #### A simple lookup of the incoming references for one item with metadata ####
 Instead of just getting the content hub IDs, you can also request to retrieve metadata for each item.

 The metadata returned are the default fields that are returned by authoring search API (`authoring/v1/search`).
 ##### Request: #####
 ~~~
     "{baseURL}/authoring/v1/references/incoming/content-type/cad2e430-beed-40d0-bb57-1c86c4f912c0?include=metadata"
 ~~~
 ##### Response: #####
 ~~~
 {
    "offset": 0,
    "limit": 200,
    "href": "/authoring/v1/references/incoming/content-type/cad2e430-beed-40d0-bb57-1c86c4f912c0?offset=0&limit=200",
    "items": [
      {
        "id": "2107a014-51f7-4161-96e2-d8eac6ad7dd9",
        "classification": "content",
        "metadata": {
          "id": "content:2107a014-51f7-4161-96e2-d8eac6ad7dd9",
          "name": "Slide6",
          "classification": "content",
          "type": "Slide",
          "typeId": "cad2e430-beed-40d0-bb57-1c86c4f912c0",
          "locale": "en",
          "lastModified": "2017-06-09T04:09:35.622Z",
          "lastModifier": "Thomas Watson",
          "lastModifierId": "8bd88336-648c-46a6-80d4-73c0e81fb4fa",
          "created": "2017-06-09T01:21:07.524Z",
          "creator": "Thomas Watson",
          "creatorId": "8bd88336-648c-46a6-80d4-73c0e81fb4fa",
          "status": "ready",
          "thumbnail": "/authoring/v1/resources/28dcd9c49b0d45fb8c7bf045cc0582db?fit=inside%7C220:145"
        }
      },
      {
        "id": "367a067a-d49e-4a40-b16a-18442fd3b6ba",
        "classification": "content",
        "metadata": {
          "id": "content:367a067a-d49e-4a40-b16a-18442fd3b6ba",
          "name": "Slide2",
          "classification": "content",
          "type": "Slide",
          "typeId": "cad2e430-beed-40d0-bb57-1c86c4f912c0",
          "locale": "en",
          "lastModified": "2017-06-09T01:20:20.757Z",
          "lastModifier": "Thomas Watson",
          "lastModifierId": "8bd88336-648c-46a6-80d4-73c0e81fb4fa",
          "created": "2017-06-09T01:20:13.104Z",
          "creator": "Thomas Watson",
          "creatorId": "8bd88336-648c-46a6-80d4-73c0e81fb4fa",
          "status": "ready"
        }
      }
    ]
  }
 ~~~
 #### Using fl parameter to request specific metadata fields ####
 Just like the search API, the `fl` parameter can be used to request specific fields including the `document` field, which is the entire API representation of the item.

 Note: When the `fl` parameter is used, the `id` field is also always returned.
 ##### Request: #####
 ~~~
     "{baseURL}/authoring/v1/references/incoming/content-type/cad2e430-beed-40d0-bb57-1c86c4f912c0?include=metadata&fl=name"
 ~~~
 ##### Response: #####
 ~~~
     {
    "offset": 0,
    "limit": 200,
    "href": "/authoring/v1/references/incoming/content-type/cad2e430-beed-40d0-bb57-1c86c4f912c0?offset=0&limit=200",
    "items": [
      {
        "id": "2107a014-51f7-4161-96e2-d8eac6ad7dd9",
        "classification": "content",
        "metadata": {
          "id": "content:2107a014-51f7-4161-96e2-d8eac6ad7dd9",
          "name": "Slide6"
        }
      },
      {
        "id": "367a067a-d49e-4a40-b16a-18442fd3b6ba",
        "classification": "content",
        "metadata": {
          "id": "content:367a067a-d49e-4a40-b16a-18442fd3b6ba",
          "name": "Slide2"
        }
      }
    ]
  }
 ~~~
<br />User roles: admin, manager, editor, viewer

## Path parameters

- `id` string, required
- `classification` string, required

## Query parameters

- `fl` string[]
- `include` string[]
- `offset` integer
- `limit` integer

## Response `200`

Successfully returns the incoming references paged result.

- object
  - `limit` integer — The page size.
  - `offset` integer — The number of items to skip from the beginning of the list.
  - `href` string — A link to the current page.
  - `next` string — A link to the next page. Only shown if a next page exists.
  - `previous` string — A link to the previous page. Only shown if a previous page exists.
  - `items` object[]
    - `id` string — the id of the item.
    - `classification` string — Every item in content hub has a classification the classification and id combine to make a unique id across different types of items in content hub.
    - `metadata` object — The metadata property is only added if you use include=metadata. Additionally the contents of this object mirrors what is returned by search which is why the search `fl` parameter is available for use here. So with fl=id,name The name and id will be added. The id will always be included

## Other responses

- `429` — Too Many Requests, the server has reached a limit, the request must be sent again at a later time.

---

[API](https://skmtc.net/goacoustic/apis/acoustic-content-api.md) · [All operations](https://skmtc.net/goacoustic/apis/acoustic-content-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/goacoustic/acoustic-content-api/revisions/677305266d89/schema)