> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/events/one-off-links.md).

# One-off invite links

Create single-use invite links for a dCal event. Each link books the event once, for one person, then stops working. Learn how to create, copy and revoke links, what each state means, what the guest s

A one-off invite link books an event once, then stops working. Send each link to one person: a client you want to see this week, a candidate for an interview, a partner you are fitting in. Combined with a hidden event, it lets you offer times that nobody else can book.

A link is a pass to an existing event, not a new event: it uses that event's length, hours, booking window, location, questions and reminders.

***

**Step 1:** Open **Events** and click **Edit** on the event. In **General**, find **Visibility and sharing**. One-off invite links work on saved events only: on a new event, the section reads **Save this event before creating invite links.** Create the event first, then come back to it.

***

**Step 2 (recommended):** Tick **Hidden** and click **Save changes**. While the event is visible, the **One-off invite links** section shows a notice: anyone with the event's normal link can still book it, so an invite link limits nothing. Once the event is hidden, the invite links are the only way to book it.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-67a4796c82f42daaadbae59412888766e9829190%2Fdcal-one-off-links-01-public-notice.png?alt=media" alt="The One-off invite links section with its hint, the boxed notice shown while the event is visible on the booking page, the Create invite link button and the line No invite links yet."><figcaption><p>The notice disappears as soon as you tick <strong>Hidden</strong>.</p></figcaption></figure>

***

**Step 3:** Click **Create invite link**. dCal creates the link and copies it straight away: **Invite link created and copied.** If your browser blocks copying, you see **Invite link created.** instead, and the link's path (`/booking/{code}`) stays visible in the list so you can select it.

The link has the shape `book.dcal.ai/booking/{code}`, with a long random code. It does not reveal your handle or the event name.

***

**Step 4:** Paste the link into an email, a chat or a text message to the one person who should book. When they book, the link is used up.

***

## The list of links

Every link you create for the event is listed in the section, newest first.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-f3f65fb8012ff0e9ba5667882c282a362b2533d6%2Fdcal-one-off-links-03-list.png?alt=media" alt="The list of invite links with three rows in the states Ready to send, Revoked and Used, each with its creation date and a Copy button, and a Revoke button on the live link"><figcaption><p>Each row shows the link, its state, when you created it and what you can do with it.</p></figcaption></figure>

| State             | What it means                                                | Actions              |
| ----------------- | ------------------------------------------------------------ | -------------------- |
| **Ready to send** | Not used yet. It books the event once.                       | **Copy**, **Revoke** |
| **Used**          | Someone booked with it. It no longer opens the booking page. | **Copy**             |
| **Revoked**       | You switched it off before it was used.                      | **Copy**             |

* **Copy** copies the full link and shows **Link copied.** It also works on used and revoked links, so you can check which link you sent.
* **Revoke** switches a link off at once, with no confirmation, and shows **Invite link revoked.** A revoked link cannot be switched back on: create a new one.
* If an action fails, the section shows **Could not do that. Try again.**

Creating and revoking links take effect immediately. You do not need to click **Save changes**.

***

## What the guest sees

* **A link that is ready:** the same booking page as the event, with its times, questions and confirmation, even when the event is hidden.
* **A used or revoked link:** a message titled **This invite link has already been used**, which asks them to request a new link from you. There are no buttons on it.
* **A mistyped link:** **Page not found**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-54aca8d8eacd081be2664cde1a83430a0f82d233%2Fdcal-one-off-links-04-used-link.png?alt=media" alt="The public page for a used invite link with the title This invite link has already been used, boxed, and a short explanation"><figcaption><p>What someone sees when they open a link that was already used.</p></figcaption></figure>

Invite link pages are kept out of search engines.

***

## Rules

* One booking per link. A seat on a [group event](https://docs.dapta.ai/dcal/events/group-events.md) counts as a booking.
* Cancelling the booking does not bring the link back. To let the person book again, create a new link.
* Links have no expiry date: a link stays ready until it is used or you revoke it.
* There is no limit on how many links an event can have.
* Links work on visible events, hidden events and team events.
* If you delete the event, its links show **Page not found**.
* Members create and revoke links on their own events. Links for team events need an owner or an admin.

## Related

* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md): hide an event and the other options.
* [Events (booking links)](https://docs.dapta.ai/dcal/events.md): the Events page and its quick actions.
* [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md): what happens after the booking.
* [Group events (seats)](https://docs.dapta.ai/dcal/events/group-events.md): links on events with several seats.


---

# 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 by asking a question.

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

```
GET https://docs.dapta.ai/dcal/events/one-off-links.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 `automate deployments from our CI pipeline` 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.
