Developer preview

Automate PDF work with TapScanner

TapScanner’s public PDF API is not self-serve yet. This preview page defines the boundary honestly while we validate authenticated jobs, usage, deletion, and support.

Use TapScanner today

Start with the supported browser product while API access is reviewed. Every workflow keeps its current limits and account requirements visible.

  • Browse focused PDF tools with a file action, limits, and result guidance.
  • Use Ask PDF in the browser with an active Premium web entitlement.
  • Keep explicitly saved PDFs in account-bound Documents when that feature is enabled.

What a preview would validate

Private preview access is a product and support review, not an invitation to guess at undocumented endpoints.

  • Authenticated job submission with idempotency and a typed usage decision.
  • Signed status and result delivery that keeps document contents out of analytics.
  • Entitlement, deletion, retry, and support boundaries that are documented before access.

Not available yet

Do not put production files or secrets into undocumented routes. These capabilities stay off until the owner evidence and runtime contract exist.

  • Self-serve API keys, SDKs, or a public endpoint catalog.
  • Webhook delivery guarantees, customer-selected processing regions, or a public SLA.
  • API billing, quota, or team-seat activation from this page.

Developer API questions

Can I create a TapScanner API key today?

No. TapScanner does not currently issue self-serve public API keys. Use the browser tools or request a private preview conversation for a specific use case.

Can I send files to an undocumented TapScanner endpoint?

No. Undocumented routes are not a supported integration and may change or be disabled. A preview request must define the authenticated job, limits, result handling, and deletion behaviour first.

What should I include in a preview request?

Describe the PDF operations, expected volume, identity model, result destination, retry needs, and support requirements. Do not include document contents, passwords, or credentials in the email.