---
title: "Get Activity By Id"
method: GET
path: "/api/ats/v1/activities/{id}"
tags: ["Activity"]
---

# Get Activity By Id

`GET /api/ats/v1/activities/{id}`

Returns a Activity object with the given id.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `include_raw_data` boolean — Include raw data in the response
- `include_custom_fields` boolean — Whether to include custom fields in the response.
- `expand` string — Which relations should be returned in expanded form. Multiple relation names should be comma separated without spaces. You can also specify required fields in [] for each relation name.

## Headers

- `x-connector-token` string, required

## Response `200`

Successful Response

- AtsActivity — The activity object is used to represent any activity in the ATS.
  - `id` string, uuid, required
  - `remote_id` string, nullable, required — The third-party API ID of the matching object.
  - `modified_at` string, required — This is the datetime that this object was last updated by Bindbee
  - `raw_data` object, nullable — This is the Raw data
  - `custom_fields` object, nullable, required — The custom fields related to the model
  - `user` string, nullable, required — The user who owns the activity.
  - `activity_type` 'NOTE' | 'EMAIL' | 'OTHER', nullable, required — The type of activity. If the value is not one of the defined enum values, the original value passed through will be returned.
  - `subject` string, nullable, required — The subject of the activity.
  - `body` string, nullable, required — The body of the activity. This can include notes, comments, or other relevant information.
  - `visibility` 'ADMIN_ONLY' | 'PUBLIC' | 'PRIVATE', nullable, required — Visibility of the activity. If the value is not one of the defined enum values, the original value passed through will be returned.
  - `candidate` string, nullable, required — Candidate who applied for the activity.
  - `remote_created_at` string, nullable, required — When the third party's candidate was created.

## Other responses

- `401` — Missing or invalid bearer authentication credentials.
- `403` — The credentials are valid but do not permit access to this resource, e.g. a connector token used on a different API category or a model whose writes are disabled.
- `404` — The requested resource was not found.
- `422` — Validation Error
- `429` — Rate limit exceeded.

---

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