About the doqs.dev | PDF filling API API
doqs.dev | PDF filling API API on Apizie: 14 endpoints (List Templates, Create Template, Preview, List Templates, …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://zieapi.vercel.app/v1/open-data:doqs/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | open-data:doqs |
|---|---|
| Status | Your key |
| Endpoints | 14 |
| Category | Open Data |
| Source | doqs.dev |
| Base URL | https://zieapi.vercel.app/v1/open-data:doqs/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
doqs.dev | PDF filling API API FAQ
How do I call the doqs.dev | PDF filling API API?
Create a free Apizie key, then send GET https://zieapi.vercel.app/v1/open-data:doqs/list-templates-designer-templates-get with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the doqs.dev | PDF filling API API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. doqs.dev | PDF filling API itself also needs your own key from doqs.dev.
Can AI agents use the doqs.dev | PDF filling API API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key open-data:doqs.
What is the status of the doqs.dev | PDF filling API API?
Needs your own provider key (bring your own key)