The Password Pusher JSON API.

This API allows for both anonymous and authenticated access.

For more information including language-specific examples to copy, see: docs.pwpush.com/docs/json-api/

Authentication

To authenticate, get your API token from the API token page and then apply it in your API calls as request headers:

'Authorization': "Bearer <token>"

Examples

Curl

curl -X POST -H "Authorization: Bearer YOUR_API_TOKEN" --data "password[payload]=mypassword" https://pwpush.com/p.json

For more information including language-specific examples to copy, see: docs.pwpush.com/docs/json-api/

February 2025 Update (v1.4)

Added a new version endpoint to get the current application version, API version, and edition information. This will be expanded soon to include more information.

February 2025 Update (v1.3)

The API has been updated to use Bearer tokens for authentication and a general cleanup of the API.

The X-User-Email and X-User-Token headers are deprecated although they will probably still be supported indefinitely for v1 of the API (and not carried into the eventual APIv2).

Some clients may need minor updates if they were relying on non-standard behavior.

If something has broken recently, please see this pull request for more details.

May 2024 Update

/f and /r paths are now merged into /p. Please use /p/* & /p.json for all new API calls.

Resources

Pushes
Interact directly with pushes.

Resource Description
GET /p/:url_token.json Retrieve a push.
POST /p.json Create a new push.
GET /p/:url_token/preview.json Helper endpoint to retrieve the fully qualified secret URL of a push.
GET /p/:url_token/audit.json Retrieve the audit log for a push.
DELETE /p/:url_token.json Expire a push: delete the payload and expire the secret URL.
GET /p/active.json Retrieve your active pushes.
GET /p/expired.json Retrieve your expired pushes.

Version

Resource Description
GET /api/v1/version.json Get the version details of the application and the API.