TAGGUN Receipt OCR Scanning API
Expects only running software, real reactions, and beautifully crafted APIs to serve your every desire to transcribe a piece of paper to digital form.
AI & machine learning#openapi#text
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Expects only running software, real reactions, and beautifully crafted APIs to serve your every desire to transcribe a piece of paper to digital form.
Endpoints 13
3. Improve your results
- POSTAdd manually verified receipt data to a given receipt for feedback and training purposes
/api/account/v1/feedback - POSTAdd a keyword to your account's model to predict merchant name. Changes in your account's model are updated daily.
/api/account/v1/merchantname/add
4. Deprecated endpoints
- POSTdetect and match a receipt against keywords and metadata by uploading an image file
/api/receipt/v1/match/fileDeprecated. - POSTtranscribe a receipt in storage
/api/receipt/v1/simple/storageDeprecated. - POSTtranscribe a receipt in storage and return detailed result
/api/receipt/v1/verbose/storageDeprecated.
2. Try other input format endpoints
- POSTtranscribe a receipt using base64 encoded image in json payload
/api/receipt/v1/simple/encoded - POSTtranscribe a receipt from URL
/api/receipt/v1/simple/url - POSTtranscribe a receipt using base64 encoded image in json payload and return detailed result
/api/receipt/v1/verbose/encoded - POSTtranscribe a receipt from URL and return detailed result
/api/receipt/v1/verbose/url
1. Getting started
- POSTtranscribe a receipt by uploading an image file
/api/receipt/v1/simple/file - POSTtranscribe a receipt by uploading an image file and return detailed result
/api/receipt/v1/verbose/file
- POSTvalidate and match a receipt against a campaign validation settings by uploading an image file
/api/validation/v1/campaign/file - POSTvalidate if user-submitted info like serial number are detected an image file
/api/validation/v1/campaign/product-validation/file
API details
- Base URL
https://api.taggun.io- Authentication
- None declared in the description
- Operations
- 13 operations on 13 pathsPOST 13
3 marked deprecated - Main resources
- 2. Try other input format endpoints 44. Deprecated endpoints 31. Getting started 23. Improve your results 2
- Description format
- Swagger 2.0, API version
1.10.9 - Links
- OpenAPI document · Terms of service
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the TAGGUN Receipt OCR Scanning API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the TAGGUN Receipt OCR Scanning API collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “Add manually verified receipt data to a given receipt for feedback and training purposes” (POST /api/account/v1/feedback), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the TAGGUN Receipt OCR Scanning API?
Expects only running software, real reactions, and beautifully crafted APIs to serve your every desire to transcribe a piece of paper to digital form. It is listed under AI & machine learning and has 13 endpoints.
Who publishes the TAGGUN Receipt OCR Scanning API?
It is listed from Taggun's public API description (an OpenAPI document), not published by Taggun on Swastik Codes. Anyone who controls taggun.io can claim the profile by adding a DNS TXT record.
What is the base URL of the TAGGUN Receipt OCR Scanning API?
Requests go to https://api.taggun.io. Endpoint paths are added to this base URL.
How do I authenticate with the TAGGUN Receipt OCR Scanning API?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the TAGGUN Receipt OCR Scanning API have?
13 operations on 13 paths (13 POST). The largest groups are 2. Try other input format endpoints, 4. Deprecated endpoints, 1. Getting started, 3. Improve your results.
Is forking the TAGGUN Receipt OCR Scanning API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.