TapScanner (pdf.tap.scanner) Data API
PDF Scanner app - TapScanner is a camera-to-PDF document scanner and editor for Android from Tap AI: the camera screen photographs paper pages and saves them as PDFs, a text-recognition step sends a scanned page to the cloud and brings back its text page by page, and a PDF-to-DOCX converter turns a finished scan into an editable Word document. Premium features sit behind a paid tier that can also be unlocked with a promotional redeem code handed out through bundle partners and checked against the user's device. Listed under utilities, it serves mobile productivity users in the United States, India, Brazil and Indonesia who digitise contracts and other paperwork on their phones, and it competes with Adobe Scan, CamScanner, Genius Scan, Simple Scan, SwiftScan and Clear Scan as well as India's Kaagaz.
Recognition jobs are the core record here: a scanned page enters as a job reserved with an id and a pre-signed uploadURL, carries a status that reads ok when the slot is reserved, started once recognition begins and done when it finishes, and closes stamped with a startTimestamp, the recognized document text and a files list of per-page outputs, each retrievable on its own by fileName. Conversion adds a second document stream, in which a scanned PDF submitted as a file part comes back as an editable DOCX. A separate entitlement slice pairs a promotional redeemCode with a deviceId and answers with a verified flag.
Document-intake automation runs on that job lifecycle: back-office pipelines reserve an upload slot, start recognition and poll until status reads done, then land the text in a document-management system without anyone opening the app. Contract and legal tooling batch-converts scans from PDF to DOCX for redlining and collects the editable documents, and bundle partners check a redeemCode against its deviceId before granting premium features, so every promotional license traces back to one device. openData Studio turns these recognition jobs, PDF-to-DOCX conversions and redeem-code checks into callable open data.
Screenshots
API surface
The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.
OCR upload (reserve an upload slot)
POST
/v1/jobs/prepareopendataReserves a recognition job and returns the pre-signed URL plus job id used to push the scanned image for server-side text recognition.
Auth: integrity_token request header (Google Play Integrity token)
- status
- id
- uploadURL
POST /v1/jobs/prepare?retry=false HTTP/1.1 integrity_token: <play-integrity-token>{ "status": "ok", "id": "8f3c1d2e-7a9b-4c5e-9f0a-1b2c3d4e5f6a", "uploadURL": "https://cdn.example.com/upload/8f3c1d2e..." }OCR start (kick off recognition)
POST
/v1/jobs/{id}/beginopendataStarts text recognition for an uploaded document image and returns the job id to poll for results.
Auth: integrity_token request header
- status
- id
POST /v1/jobs/8f3c1d2e-7a9b-4c5e-9f0a-1b2c3d4e5f6a/begin HTTP/1.1 integrity_token: <play-integrity-token>{ "status": "started", "id": "8f3c1d2e-7a9b-4c5e-9f0a-1b2c3d4e5f6a" }OCR status / result (poll recognized text)
POST
/v1/jobs/{id}/resultopendataPolls a recognition job and returns the recognized text plus the list of per-page output files once recognition completes.
Auth: integrity_token request header
- status
- startTimestamp
- files
- text
POST /v1/jobs/8f3c1d2e-7a9b-4c5e-9f0a-1b2c3d4e5f6a/result HTTP/1.1 integrity_token: <play-integrity-token>{ "status": "done", "startTimestamp": 1737456000000, "files": ["page_1.txt", "page_2.txt"], "text": "Recognized document text..." }OCR result file download
GET
/v1/jobs/{id}/artifacts/{fileName}opendataDownloads a single recognized page/text artifact produced by the recognition pipeline.
Auth: integrity_token request header
- id
- fileName
GET /v1/jobs/8f3c1d2e-7a9b-4c5e-9f0a-1b2c3d4e5f6a/artifacts/page_1.txt HTTP/1.1 integrity_token: <play-integrity-token><raw text/octet-stream body of the recognized page>PDF to DOCX conversion
POST
/v1/convert/officeopendataUploads a scanned PDF as multipart form data and returns the converted DOCX document.
Auth: integrity_token request header
- integrity_token
- file
POST /v1/convert/office HTTP/1.1 integrity_token: <play-integrity-token> Content-Type: multipart/form-data; boundary=----x ------x Content-Disposition: form-data; name="file"; filename="scan.pdf" Content-Type: application/pdf <binary pdf bytes><binary .docx ResponseBody>Promo redeem-code verification (entitlement)
POST
/v1/licenses/redeemosintValidates a promotional redemption code against a device id to unlock the premium entitlement.
Auth: none beyond the redeem code in the JSON body
- redeemCode
- deviceId
- verified
POST /v1/licenses/redeem HTTP/1.1 Content-Type: application/json { "redeemCode": "SUMMER-DEAL-1234", "deviceId": "a1b2c3d4-e5f6-7890" }{ "verified": true }
Data categories
- ocr
- document-conversion
- entitlements
- device-identity
Where teams use this data
Document-intake automation
Back-office pipelines drive the OCR job lifecycle — reserve an upload slot, kick off recognition, poll the result — landing searchable text in the DMS without a human opening the app.
Bulk format conversion
Contract and legal tooling batch-convert scans from PDF to DOCX for redlining, pushing files through the conversion endpoint and collecting editable documents.
Entitlement verification
Bundle partners verify redeem codes against device ids before granting premium features, keeping promotional licenses auditable.
Frequently asked questions
How does TapScanner's server-side text recognition pipeline work?
Recognition runs as a job pipeline over three calls: POST /v1/jobs/prepare reserves an upload slot and returns a job id plus a pre-signed uploadURL, POST /v1/jobs/{id}/begin starts recognition on the uploaded scan, and POST /v1/jobs/{id}/result is polled until the status is done, returning the recognized text and the files list of per-page outputs.
How are TapScanner's API calls authenticated?
Every recognition and conversion call carries an integrity_token request header holding a Google Play Integrity token; there is no session cookie or bearer token in the flow. The one exception is POST /v1/licenses/redeem, which is gated only by the redeemCode and deviceId pair in its JSON body.
What fields does the recognition result return?
The POST /v1/jobs/{id}/result response carries status, startTimestamp, files (a list of per-page output files) and text (the recognized document text). Individual pages are then downloaded via GET /v1/jobs/{id}/artifacts/{fileName}.
How does TapScanner convert a scanned PDF to DOCX?
The app uploads the scanned PDF to POST /v1/convert/office as multipart form data with a single file part, authenticated by the same integrity_token header, and the service streams back the converted DOCX document as a binary response body.
Apps similar to PDF Scanner app - TapScanner
- Adobe Scan — Free scanner app with automatic edge detection and OCR that turns paper documents into searchable, editable PDFs.
- CamScanner — Long-running scanner app offering batch scanning with auto-shutter and multiple export formats; its free tier adds a watermark to scans.
- Genius Scan - PDF Scanner — Scanner app with automatic image optimization and organization through tags and folders, with a free tier that works without an account or watermark.
- Simple Scan - PDF Scanner App — Lightweight scanner focused on fast capture and batch processing of multi-page PDFs, with optional backup to cloud drives.
- PDF Scanner & Editor by Kaagaz — Made-in-India scanner app that works offline, adds no watermark, and bundles PDF tools such as compression, merge, and signatures.
- SwiftScan — Scanner app emphasizing fast capture with batch scanning, automatic edge detection, and integration with cloud storage services.
- Clear Scan — Scanner app with folder organization and OCR text extraction that saves scans as PDFs at a chosen quality level.
Topics
- tapscanner api
- pdf.tap.scanner ocr api
- tapscanner ocr pipeline
- tapscanner pdf to docx api
- tapscanner premium redeem code api
Need this app's data API integrated?
We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.
- NDA + SOW on every engagement
- Delivery in 3–7 days
- Payment only after acceptance
- Work scoped to authorized use