> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/scheduling-artifacts.md).

# Single-use links and slot proposals

Issue a shareable artifact from an existing personal or group scheduling link instead of booking immediately.

## Single-use link

```http
POST /api/v1/accounts/WORKSPACE_ID/scheduling_links/KIND/LINK_ID/single_use_links
Authorization: Bearer YOUR_DISTRO_API_TOKEN
Content-Type: application/json
```

```json
{
  "invitee": { "name": "Alex Example", "email": "alex@example.com" },
  "expires_in_days": 7,
  "time_zone": "Europe/London",
  "idempotency_key": "offer-000123"
}
```

Required scope: `scheduling_links:write`. Expiry defaults to seven days when omitted.

## Slot proposal

Use the same route prefix ending in `/slot_proposals`. Supply `slot_tokens` from a recent availability response along with the supported invitee, expiry, timezone and idempotency fields.

```json
{
  "slot_tokens": ["FIRST_SLOT_TOKEN", "SECOND_SLOT_TOKEN"],
  "time_zone": "Europe/London",
  "expires_in_days": 7,
  "idempotency_key": "proposal-000123"
}
```

## Use the response

The response includes `artifact` with ID, kind, URL, HTML, plain text and expiry, plus `replayed`. A new artifact returns HTTP 201; a replay returns HTTP 200.

Use the returned HTML or plain text in your intended email/CRM handoff. Keep the generated URL intact: it includes the guest access information.

An issued link or proposal is not a confirmed booking or permanent slot hold. Check expiry and actual availability when the guest uses it.

See [Booking links](/scheduling/booking-links.md) for the product experience and [API retries](/developers/errors.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/developers/scheduling-artifacts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.