# Data Types

When a data source is connected, the data is transformed into a common data schema to provide consistency of the data, regardless of where it was sourced. For example a Facebook post and an X post will both be transformed into a common social post record, matching the [social post schema](https://common.schemas.verida.io/social/post/v0.1.0/schema.json).

### Social: Post

* **Description:** A social media post
* **Link:** <https://common.schemas.verida.io/social/post/v0.1.0/schema.json>
* **Data sources:** X (Twitter), Facebook

### Social: Following

* **Description:** An account the user is following
* **Link:** <https://common.schemas.verida.io/social/following/v0.1.0/schema.json>
* **Data sources:** Youtube, Discord, Facebook, X

### Social: Favourite

* **Description:** A favourite of the user (ie: Liked Youtube video)&#x20;
* **Link:** <https://common.schemas.verida.io/favourite/v0.1.0/schema.json>
* **Data sources:** Youtube

### Email

* **Description:** An email
* **Link:** <https://common.schemas.verida.io/social/email/v0.1.0/schema.json>
* **Data sources:** X (Twitter), Facebook

### File

* **Description:** A file. Note: Files on third party platforms are typically not stored, rather linked to (ie: Google Doc link)
* **Link:** <https://common.schemas.verida.io/file/v0.1.0/schema.json>
* **Data sources:** Google Drive, User uploads via Verida Vault web interface

### Social: Chat Group

* **Description:** A chat group
* **Link:** <https://common.schemas.verida.io/social/chat/group/v0.1.0/schema.json>
* **Data sources:** Telegram

### Social: Chat Message

* **Description:** A chat message
* **Link:** <https://common.schemas.verida.io/social/chat/message/v0.1.0/schema.json>
* **Data sources:** Telegram

### Social: Calendar

* **Description:** A calendar
* **Link:** <https://common.schemas.verida.io/social/calendar/v0.1.0/schema.json>
* **Data sources:** Google Calendar

### Social: Calendar Event

* **Description:** An event within a calendar
* **Link:** <https://common.schemas.verida.io/social/event/v0.1.0/schema.json>
* **Data sources:** Google Calendar


---

# Agent Instructions: 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:

```
GET https://docs.verida.ai/data-apis/data-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.