Integration guide
Follow these steps to connect your application to the DocTools Base64 API.
-
Create an API key
Open and click “Generate New API Key” Copy and store the key securely; it is shown only once.
-
Authenticate every request
Send your key in the
X-API-Keyheader on all/api/v1/*calls. -
Try with Postman
Download or copy our Postman collection from the section. Import it into Postman, set the
api_keycollection variable to your key, and run the included requests. -
Encode files
POST /encodewith a multipart file upload or JSONcontent_base64. Files are encoded as-is — locked PDFs do not need a password. Or usePOST /encode-urlwith a public PDF or Base64 file URL that the server can reach; passpasswordonly when the source PDF is encrypted. The response includes inlinebase64, adocument_id, and abase64_urlfor later retrieval. -
Decode Base64
POST /decodewith raw Base64 or a DocTools envelope to download the original file bytes — no storage required. Or usePOST /decode-urlwith a public PDF or Base64 file URL that the server can reach and download directly; passpasswordonly when the source PDF is encrypted. -
Fetch stored documents
Use the
document_idfrom encode to get metadata, download Base64 text, or fetch the decoded file. Send only yourX-API-Key— stored downloads do not use a separate document password. Files are kept for 7 days.
API Key Management
About API Keys
API keys are used to authenticate your requests to our API. Keep your API key secure and do not share it publicly.
New API Key Generated
This key will only be shown once. Make sure to copy it now.
Base64 API
Encode files to Base64, decode text, and fetch stored documents by unique ID.
All endpoints use X-API-Key. Optional password on
encode-url and decode-url unlocks encrypted source PDFs
only; Click an endpoint to see example requests and responses.