Skip to main content
Try it live: PDF Search and Delete Text → API Tester — send a real request from your browser.

POST /v1/pdf/edit/delete-text

When using regular expressions in JSON payloads, ensure that backslashes are properly escaped. For example, a single backslash \ should be written as \\.

Attributes

Attributes are case-sensitive and should be inside JSON for POST request. for example: { "url": "https://example.com/file1.pdf" }

Showing Redacted Text

By default when we delete text using post-tag-pdf-edit-delete-text it will simply remove text leaving a space where the text was. In the case where you need to blackout deleted text it can be acheived using following profiles parameters.
  • Set UsePatch parameter to true.
  • Set PatchColor parameter to color we want to use for redacting in hex format. For example: 'PatchColor': '#000000'.
In case we want to only blackout text, but not remove it so that we can still copy it, we can do so using RemoveTextUnderPatch parameter and set it to false.
If RemoveTextUnderPatch is set to false then a user could still copy the text making the redaction less secure than you might require!

Query parameters

No query parameters accepted.

Responses

Example Payload

To see the request size limits, please refer to the Request Size Limits.

Example Response

To see the main response codes, please refer to the Response Codes page.
Inconsistent URL Encoding in cURL Output: When using cURL to make API requests, the output JSON may show URL characters encoded as Unicode escape sequences. For example, the ampersand character (&) may appear as \u0026 in the cURL output. This is normal JSON encoding behavior and does not affect the validity of the URL. The URL will function correctly when used, as JSON parsers automatically decode these escape sequences. If you’re parsing the response programmatically, your JSON parser will handle this conversion automatically.

Code Samples