Use case
Use it when your backend generates or receives PDFs and needs consistent title, author, subject, or keywords for search and records.
PDF Tools API
Normalize metadata for generated documents, archives, and document management systems.
Credits
1 Credit / call
1 Credit per successful API request. Failed processing attempts are refunded automatically.
Pricing
1,000 Credits = $1
Every signed-in user receives 100 free API Credits each month.
Endpoint
/api/external/pdf-tools/edit-metadataUse your API Key in the x-api-key header.
Use it when your backend generates or receives PDFs and needs consistent title, author, subject, or keywords for search and records.
curl -X POST https://itextmaster.com/api/external/pdf-tools/edit-metadata \
-H 'x-api-key: YOUR_API_KEY' \
-F 'file=@input.pdf;type=application/pdf' \
-F 'options={"title":"Updated title","author":"iTextMaster","subject":"API generated document"}' \
--output metadata-updated.pdfcurl -X POST https://itextmaster.com/api/external/pdf-tools/edit-metadata \
-H 'x-api-key: YOUR_API_KEY' \
-F 'file=@input.pdf;type=application/pdf' \
-F 'options={"title":"Updated title","author":"iTextMaster","subject":"API generated document"}' \
--output metadata-updated.pdfcurl -X POST https://itextmaster.com/api/external/pdf-tools/edit-metadata \
-H 'Content-Type: application/json' \
-H 'x-api-key: YOUR_API_KEY' \
-d '{
"file": { "name": "input.pdf", "dataBase64": "JVBERi0xLjcK..." },
"options": {"title":"Updated title","author":"iTextMaster","subject":"API generated document"}
}' \
--output metadata-updated.pdfimport { writeFile } from 'node:fs/promises';
const response = await fetch('https://itextmaster.com/api/external/pdf-tools/edit-metadata', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': process.env.ITEXTMASTER_API_KEY
},
body: JSON.stringify({
file: { name: 'input.pdf', dataBase64: 'JVBERi0xLjcK...' },
options: {"title":"Updated title","author":"iTextMaster","subject":"API generated document"}
})
});
if (!response.ok) {
throw new Error(await response.text());
}
await writeFile('metadata-updated.pdf', Buffer.from(await response.arrayBuffer()));import os
import requests
response = requests.post(
'https://itextmaster.com/api/external/pdf-tools/edit-metadata',
headers={
'Content-Type': 'application/json',
'x-api-key': os.environ['ITEXTMASTER_API_KEY'],
},
json={
'file': {'name': 'input.pdf', 'dataBase64': 'JVBERi0xLjcK...'},
'options': {'title': 'Updated title', 'author': 'iTextMaster', 'subject': 'API generated document'}
},
)
response.raise_for_status()
with open('metadata-updated.pdf', 'wb') as f:
f.write(response.content)invalid_api_keyThe x-api-key header is missing, invalid, or has been rotated.
insufficient_creditsThe account does not have enough API Credits for the request.
pdf_tool_processing_failedThe file, options, or PDF structure could not be processed. Failed processing attempts are refunded automatically.
metadata-updated.pdf with X-Credits-Charged: 1 and X-Credit-Balance response headers.
Content-TypeContent-DispositionX-Credits-ChargedX-Credit-BalanceEach successful Edit Metadata API request uses 1 Credit. 1,000 Credits cost $1, and every signed-in user receives 100 free API Credits each month.
Failed processing attempts are refunded automatically, and the API returns an error response you can log or retry.
No. Keep API Keys server-side and call the endpoint from your backend, queue, or automation job when you need to edit metadata.
Create an API Key, test Edit Metadata API, and buy more Credits only when automation volume grows.