# List who a booking could go to (/docs/api-reference/scheduling-bookings/list-scheduling-reassign-candidates)

The environment's other active hosts: members of the event type first, in the order a pool would pick them, each saying whether they're free and why not. Things can change before you ask: reassigning decides again.

`GET https://api.coss.com/v1/scheduling/bookings/{id}/reassign_candidates`

Authenticate with your API key as a bearer token (`Authorization: Bearer coss_test_…`). Responses are JSON with snake_case fields; errors are `{ error: { type, code, message, param?, issues?, request_id } }` (https://coss.com/docs/api-reference/errors.md).

## Path parameters

- `id` (string, required): The booking's id.

## Query parameters

- `from_host` (string): The host who'd leave, when it could be several.

## Example request

TypeScript (the `coss` package):

```ts
import { Coss } from "coss";

const coss = new Coss({
  apiKey: process.env.COSS_API_KEY,
  baseUrl: "https://api.coss.com",
});

const { data, error } = await coss.scheduling.bookings.reassignCandidates("book_01kd2m9a0b1c2d3e4f5g6h7j8m");
```

HTTP:

```sh
curl -X GET "https://api.coss.com/v1/scheduling/bookings/book_01kd2m9a0b1c2d3e4f5g6h7j8m/reassign_candidates" \
  -H "Authorization: Bearer $COSS_API_KEY"
```

## Response 200

The candidates.

- `object` ("list", required)
- `data` (object[], required)
  - `object` ("scheduling.reassign_candidate", required)
  - `host` (string, required)
  - `uid` (string | null, required)
  - `name` (string, required)
  - `member` (boolean, required): Takes this event type, and fits what the booking was routed with. Otherwise it needs `any_host`.
  - `available` (boolean, required)
  - `reason` (string | null, required): Why they aren't available, the first of `reasons`.
  - `reasons` (string[], required): Everything in the way, each needing its override. `already_claimed` can't be overridden.
  - `load` (number, required): Their live bookings in the week from this one.
  - `rank` (number | null, required): Their place in who a pool would pick next, from 1. Null for a non-member.
  - `meeting_provider_missing` (boolean, required): They haven't connected what this booking's meeting needs, so it'd have none.
- `has_more` (boolean, required)

Example:

```json
{
  "object": "list",
  "data": [
    {
      "object": "scheduling.reassign_candidate",
      "host": "host_01kd2m9a0b1c2d3e4f5g6h7j8m",
      "uid": "doctor_518",
      "name": "Dr. Priya Raman",
      "member": true,
      "available": true,
      "reason": null,
      "reasons": [],
      "load": 4,
      "rank": 1,
      "meeting_provider_missing": false
    }
  ],
  "has_more": false
}
```

## Errors

- `400`: The `Coss-Version` header names an unknown API version (`invalid_api_version`).
- `401`: The API key is missing, invalid, revoked or expired (`authentication_error`).
- `403`: The API key lacks the permission this endpoint needs (`permission_error`), or its organization is suspended (`organization_suspended`).
- `404`: Nothing with this id or uid exists in the environment (`not_found`).
- `422`: The request failed validation (`validation_error`, see `issues`), or can't be done: see `code`.
- `429`: Too many requests with this API key (`rate_limited`), or too many requests with invalid keys from this address (`too_many_failed_authentications`). Retry after `Retry-After` seconds. Successful responses carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` (seconds until the limit is fully restored).
- `500`: Unexpected server error (`api_error` / `internal_error`).
- `503`: The API key could not be verified right now; retry (`service_unavailable`).