Can I fill an existing PDF template with the doqs.dev API?

Yes. POST /pdf-filling/templates/{id}/fill accepts a structured payload of field values for a template you have uploaded to doqs.dev and returns the filled PDF. List available templates via GET /pdf-filling/templates first to discover their ids.

Can I generate a PDF from arbitrary input rather than a saved template?

Yes. POST /pdf-generator/render accepts a render payload and returns the produced PDF. Use GET /pdf-generator/submissions afterwards to retrieve previously rendered outputs.

How do I fill a PDF template with doqs.dev through Jentic?

Run pip install jentic, search for 'fill a PDF template with doqs', load the /pdf-filling/templates/{id}/fill operation, and execute it with your template id and field values. Jentic returns the input schema so the agent assembles a valid payload without reading the docs.

What are the rate limits for the doqs.dev API?

The published spec does not declare explicit per-endpoint limits. Implement client-side backoff and treat 429 responses as the signal to slow down. Contact doqs.dev directly for high-volume rendering quotas.

Can I retrieve a list of previously generated PDFs?

Yes. GET /pdf-generator/submissions returns the history of renders associated with your account, useful for audit, compliance, or re-downloading a previously produced document.

Can I limit what my agent is allowed to do with the doqs.dev API?

Yes. Because you run Jentic One yourself, your own rules decide which doqs.dev operations the agent may call, so you can allow it to list templates and fill or render only the templates you permit and nothing else. Since the template id sits in the URL path at /pdf-filling/templates/{id}/fill, a rule can pin the agent to a single template rather than every template in your account. Your doqs.dev API key is held by your own instance and injected as the x-api-key header at execution time, so the agent never sees the credential.