Verida AI Docs
  • Welcome
  • Getting Started
    • How it works
    • Developer Console
    • Get an API key
    • Authentication
    • Scopes
    • API Requests
    • Connectors
      • Build a Connector
    • Example Apps
  • Integrations
    • PersonalAgentKit
    • LangGraph
    • NEAR Protocol
    • Nillion Network
  • Data APIs
    • Overview
    • Data Types
    • API Endpoints
      • Queries
      • Search
      • AI Prompts
      • Actions
      • Other Endpoints
    • API Performance
    • Data examples
    • API Reference
  • Resources
    • Tutorials
      • Accessing User Data (Telegram)
    • Learn
      • Anatomy of an AI Agent
      • Dynamic Loading of Data for Realtime AI
      • Data Privacy Issues
      • Web3 & DePIN solves AI's privacy problems
      • Privacy Preserving AI Tech Stack
      • Confidential Compute Litepaper
    • AI Use Cases
    • Verida Vault
    • Privacy & Security
    • Pricing
    • Grants
    • Support
Powered by GitBook
On this page
  • Social: Post
  • Social: Following
  • Social: Favourite
  • Email
  • File
  • Social: Chat Group
  • Social: Chat Message
  • Social: Calendar
  • Social: Calendar Event
Export as PDF
  1. Data APIs

Data Types

PreviousOverviewNextAPI Endpoints

Last updated 2 months ago

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

  • Description: A social media post

  • Link:

  • Data sources: X (Twitter), Facebook

Social: Following

  • Description: An account the user is following

  • Link:

  • Data sources: Youtube, Discord, Facebook, X

Social: Favourite

  • Description: A favourite of the user (ie: Liked Youtube video)

  • Link:

  • Data sources: Youtube

Email

  • Description: An email

  • Link:

  • 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)

  • Data sources: Google Drive, User uploads via Verida Vault web interface

Social: Chat Group

  • Description: A chat group

  • Data sources: Telegram

Social: Chat Message

  • Description: A chat message

  • Data sources: Telegram

Social: Calendar

  • Description: A calendar

  • Data sources: Google Calendar

Social: Calendar Event

  • Description: An event within a calendar

  • Data sources: Google Calendar

Link:

Link:

Link:

Link:

Link:

social post schema
https://common.schemas.verida.io/social/post/v0.1.0/schema.json
https://common.schemas.verida.io/social/following/v0.1.0/schema.json
https://common.schemas.verida.io/favourite/v0.1.0/schema.json
https://common.schemas.verida.io/social/email/v0.1.0/schema.json
https://common.schemas.verida.io/file/v0.1.0/schema.json
https://common.schemas.verida.io/social/chat/group/v0.1.0/schema.json
https://common.schemas.verida.io/social/chat/message/v0.1.0/schema.json
https://common.schemas.verida.io/social/calendar/v0.1.0/schema.json
https://common.schemas.verida.io/social/event/v0.1.0/schema.json