---
title: "Get a Loop Link"
method: GET
path: "/v1/loop/links/{link_id}"
tags: ["Loop Links"]
---

# Get a Loop Link

`GET /v1/loop/links/{link_id}`

## Path parameters

- `link_id` string, required

## Response `200`

Successful Response

- PublicLink
  - `link_id` string, required — Loop Link Identifier. E.g. `ber7ntO0ZHuFVCfrSNsN`
  - `expire_dt` string, date-time — Date/time the Loop Link is set to expire in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format. All dates are in UTC. E.g. `2023-05-08T00:29:45.859Z`
  - `metadata` object — Metadata can be used to further identify Loop Links in a way that makes sense for your system. The field is a key/value field that accepts string-based keys and string or numeric values. This can be useful for storing additional data such as a end-user identifier or store ID etc.
  - `name` string, required — Name of the Loop Link. This is for your own use as a way to differentiate your Loop Links. E.g. `Hotel ABC`
  - `status` 'active', required
  - `create_dt` string, date-time, required — Date/time the Loop Link was created in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format. All dates are in UTC. E.g. `2023-05-08T00:29:45.859Z`
  - `update_dt` string, date-time — Date/time the Loop Link was last updated in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format. All dates are in UTC. E.g. `2023-05-08T00:29:45.859Z`
  - `links` object, required — These are the links your end-users need to open to access the Loop UI for submitting missing events or feedback about existing events. The different link types are: - event: This URL will present a page for submitting missing events. - event_feedback: This URL will present a page for providing feedback about an existing event. When using the event link you can optionally provide the following query string parameters: - email: Email address of the end-user who is providing the feedback. This will be stored against the submission so the user can receive email notifications about their submission. When using the event_feedback link you can optionally provide the following query string parameters: - event_id: Event ID to provide the feedback for (if this is not provided, the user will be asked to enter an Event ID). - email: Email address of the end-user who is providing the feedback. This will be stored against the submission so the user can receive email notifications about their submission.
    - `event` string, uri, required — URL for submitting missing events.
    - `event_feedback` string, uri, required — URL for providing feedback about an existing event.

## Other responses

- `422` — Validation Error

---

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