> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-developers/sdks/calendario/propiedades.md).

# Propiedades

## `appointmentToken`

Esta propiedad permite acceder al token que se obtiene al momento de cargar la URL proveniente del email de confirmación o recordatorio.

```javascript
calendar.appointmentToken;
// ...
```

## `date`

Esta propiedad corresponde a la fecha fallback utilizada cuando no se proporciona una fecha en los métodos que lo requieren y también para otros métodos que almacenan estados.

```javascript
calendar.date
// 2023-04-03T17:00:00.000Z
```

## `type`

Corresponde al tipo de agendamiento que se realizará y afectará el comportamiento cuando ejecutes ciertos métodos del SDK.

El valor puede ser `service` o `user`.

{% hint style="info" %}
No sobreescribas el valor mediante la propiedad, utiliza el método [`change`](/es-developers/sdks/calendario/metodos.md#change).
{% endhint %}

```javascript
calendar.type
// service or user
```


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.videsk.io/es-developers/sdks/calendario/propiedades.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.