← Revoked explained
For developers

Add sign-in and data sharing to your app

Use the public API to read current data from shares, collect responses, add OpenID Connect sign-in, or build a connected tool. People review and approve the access your integration requests.

What you can do

What you can build with the API

Watch the feature films ↗
01

Add sign-in to your service

Each Revoked server is an OpenID Connect provider. Use the authorization-code flow with PKCE and approve through the app. A web component, Flutter package and complete demo service are available.

Integrate sign-in ↗
02

Read current values from shared records

Read a share as JSON, CSV, vCard or iCal. Resolve grants when you need their current values and respect expiry, revocation and cache limits.

Shares & grants ↗
03

Build a tool that works with a vault

Propose shares, requests or attestations for owner approval. A basic connection reads status and views; further access is explicitly granted. Scoped API keys serve your own scripts.

Build a tool ↗
04

Automate requests and verify proofs

Receive request responses through callbacks, subscribe to webhook events, verify presentations or connect an assistant through the MCP interface.

Ways to connect ↗
Getting started

Set up your first integration

  1. 01

    Run or choose a server

    Use the official server for test data or start the Go service locally. Production base URLs belong to each server operator.

  2. 02

    Choose how your integration authenticates

    Use an API key for your own automation, a connected-tool flow for another person’s app, or OpenID Connect for service sign-in.

  3. 03

    Handle expired and revoked access

    Account for paused, expired and revoked links, server outages and permission changes. Parse error codes instead of matching message text.

The server and app are open source under AGPL-3.0; a modified version offered as a service must publish its source. The SDK packages and examples are MPL-2.0 and can be used in applications under any licence.

Built on the API

Example applications

Applications with their own interface, using a Revoked server for storage and access control.

01

Packet

A browser app that bundles documents and details into one packet, with a separate link for each recipient. Records live in a section under Packet’s own connection; each recipient link is a share. Packet has no backend or database of its own. The connection is approved in the Revoked app and can be paused or disconnected there.

Packet source code ↗
Packet’s recipient list for a packet named My next home. Two recipients, each with an active link, a Copy link button, a QR code button and a Revoke button. Below, Close packet revokes all active recipient links.
Documentation

Guides and reference