§ Protection

Change PDF Password API

Takes two passwords: `password` is the current one, `newPassword` is the replacement. The old password stops working immediately, and both the user and owner password are set to the new value.

Get an API key Read the docs

Endpoint: POST /pdf/change-password
Inputs: Exactly 1 protected PDF
Returns: application/pdf, protected with the new password
Limits: 20 MB per file, 3,000 pages. AES-256.
Price: $0.001

§ 01 The request

One POST, and the file comes back.

POST /pdf/change-password

curl -sS --fail-with-body \
  -o rotated.pdf \
  -H "Authorization: Bearer $OHMYWRAP_KEY" \
  -F "file=@locked.pdf" \
  -F "password=$DOC_PASSWORD" \
  -F "newPassword=$NEW_PASSWORD" \
  https://api.ohmywrap.com/pdf/change-password

Options

None. Send the file and nothing else. An options object is still accepted, but any key inside it is 422 invalid_options.

Worth knowing

`newPassword` is a declared secret field: it is accepted only here, capped like a password rather than a file, and redacted everywhere `password` is. Passwords never travel inside the `options` JSON, where a validation error could echo them back.

§ 03 Nearby

Other pdf endpoints

All pdf endpoints

Your first /pdf/change-password call takes one line of curl.

Ten thousand calls cost ten dollars, the pack never expires, and nothing you send is kept.

Get an API key Read the docs

10,000 calls for $10. No subscription, no expiry.