Bots
Dynamic Document API bots
If one of these user agents shows up in your logs, a customer of ours made a document or an image with a file from your site, or named a file on your server in a request to our API. Neither bot crawls the web.
The user agents
| Rendering engine | Mozilla/5.0 (compatible; DynamicDocumentApiRenderer/1.0; +https://dynamicdocumentapi.com/renderer)Fetches the files a customer’s request points to: render data loaded from a URL, PDFs to merge, files to attach to a PDF and other files a document uses. Requests that the engine’s browser makes while it loads a web page can carry the browser’s own user agent instead. |
|---|---|
| Image proxy | DynamicDocumentApiImageProxy/1.0 (+https://dynamicdocumentapi.com/bot)Belongs to the canvas editor in our dashboard. When a customer places an image by its web address, the proxy fetches the image so that the editor can show it: image files only, up to 20 MB, with at most three redirects. |
How they behave
- They request only files that a customer named, directly or in a
document. They don’t follow links and don’t crawl, so they don’t
read
robots.txt. - They send no cookies or credentials of their own. For a web page it turns into a PDF, a customer can add their own headers or login, and we send those to that site only.
- The requests come from our servers in Germany. A public file that is used often may be served from our cache instead of being fetched again.
Blocking them
Block the user agent, or answer its requests with
403. The customer’s document then goes without your file,
or the request that needs it fails; nothing else happens on our side.
Because these bots don’t read robots.txt, blocking them is
the reliable way to keep your files out of other people’s
documents.
Contact
If our bots cause trouble on your site, or a customer uses your content without permission, write to abuse@dynamicdocumentapi.com with the URLs and times from your logs. To report unlawful content made with our service, see Report content.