The Password Pusher JSON API documentation.
This API allows for both anonymous and authenticated access.
To authenticate, get your API token from the API token page and then apply it in your API calls as request headers:
'X-User-Email': "<email>" 'X-User-Token': "<token>"
Example push creation with a payload, two attached files and an internal reference note:
curl -X POST -H "X-User-Email: <email>" -H "X-User-Token: MyAPIToken" -F "password[payload]=my_secure_payload" -F "password[note]=For New Employee ID 12345" -F "password[files][]=@/path/to/file/file1.extension" -F "password[files][]=@/path/to/file/file2.extension" https://pwpush.com/p.json
Example manual expiration of a push:
curl -X DELETE -H "X-User-Email: <email>" -H "X-User-Token: <token>" https://pwpush.com/p/fkwjfvhall92.json
May 2024 Update:
/f and /r are now merged into /p paths. Please use /p for all new API calls.
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. |