Add a connector

If the source your app needs is not available, add a connector in PDP-Connect/data-connectors. Each connector lives in its own folder, connectors/<key>/, and is published as a signed, versioned artifact.

Fork data-connectors and install

Fork PDP-Connect/data-connectors, then install from the repository root:

npm ci

Create the connector folder

Create connectors/<key>/. Copy the layout of an existing connector with the same kind of access. For example, connectors/oura/ uses a personal access token and connectors/google_calendar/ uses OAuth:

File	What it holds
`manifest.json`	Source, display name, setup (how the user connects), streams and their record schemas, version
`index.ts`	The collector that fetches records and emits them per stream
`schemas.ts`	Record validators for each stream
`*.test.ts`	Tests that exercise the real collection logic
`icon.svg`	The source’s icon

The PDPP Collection Profile defines the manifest format. Start with public_listing.tier: "development".

Run the checks

npx tsx --test connectors/<key>/*.test.ts
npm run verify --workspace @pdpp/polyfill-connectors
cd packages/polyfill-connectors && node --import tsx scripts/conformance.ts <key>

conformance runs every check in order and prints the next action for anything that does not pass. The connector checklist explains each check and what each tier requires.

Open a pull request

Open a pull request against PDP-Connect/data-connectors. Maintainers publish the signed artifact from main after merge.

The full authoring guide is AUTHORING.md.

Get started

Build

Ship

Extend

References

Vana SDK

Vana Account

Vana Account (mainnet)

Data Connectors

Grants and permissions

Vana L1

​References