Password Manager
Developers
Last updated 4 October 2026
Let your customers give your app a specific credential from their Password Manager vault — without your app ever seeing the vault, and without our server ever seeing the secret.
How it works
- Sign in to the developer console with Google or email, start the free sandbox (synthetic data, your own account only) and register your application (redirect URIs, an X25519 public key, scopes; confidential server app or public native app). Our team reviews it before it can be used with other people.
- Connect: your user signs in on password-manager.in and approves your app with OAuth 2.1 (authorization code + PKCE).
- Ask: your server creates a secret request, for example “GST portal credential: username, password”.
- Approve: the user's phone shows the request. They choose the item and the fields, and whether you get it once, for 10 minutes or until they revoke it.
- Receive: the phone encrypts the chosen fields for your public key and signs them; our server relays only that ciphertext. You decrypt it with your private key.
What you can and cannot do
- Scopes:
identity.basic,secret.request,secret.receive,shared.items.read,events.read. - There is no API to list, search or read a user's vault. Every secret needs the user's approval on their phone.
- Users see your app, its key fingerprint and its activity, and can revoke access at any time.
Security requirements
- Exact-match
httpsredirect URIs, PKCE (S256) and astatevalue on every authorization. - Keep your client secret and X25519 private key on your server only. We never receive your private key.
- Short-lived access tokens (15 minutes); refresh tokens rotate on every use and are revoked if reused.
- Do not log, store longer than needed or forward received secrets.
Subscriptions and limits
- Production use needs an approved application and an active API subscription. Published plans and prices appear in the developer console; payment is reviewed manually and nothing is charged automatically.
- Each plan sets hard limits: requests per second/minute/hour/day, included billable operations per calendar month (UTC), concurrent requests, payload and page size, encrypted storage, applications, credentials and webhooks. No unlimited usage and no automatic overage charges.
- Only a successfully created secret request is billable. Status polling, reads, errors and idempotent retries are free.
Read the documentation OpenAPI Developer console
Questions or registration help: info@password-manager.in