Iris by Roots Automation – API Documentation
Introduction
The Iris platform provides users access to state-of-the-art intelligent document processing and our patented human in the loop QA system. The Platform is designed to best operate integrated into an automated document management process. However, we do provide a manual upload option through the user interface for testing and small-batch purposes.
Incoming APIs
The following APIs are currently available for all customers:
Description
Upload Document – Any image file containing documents per the project requirements file type (pdf, png, jpg, jpeg, and tif). Images are uploaded to a specific project, which can be configured on send.
Example Call: Upload Document
Headers:
Content-Type : application/json
Body:
upload – your image file
details – JSON formatted string
api_key – string – project-level authentication code
project_id – integer – project-level identification
Package_name – string – (optional) – user defined field for tracking documents; typically using either a Unique Document ID or File Name
example JSON: {"api_key":"YOURAPIKEY", "project_id":21, "package_name":"YourFileName"}
Postman Example: Below is a screenshot from an example API call using the Postman API tool. Note this embedded URL in the below screenshot:
https://upload.iris.rootsautomation.com{
"intake_session_id": "4ee215f1-76e1-493d-8f0d-f16b3dd5dff6",
"package_name": "postmen_sample_file",
"status": "processing",
"package_id": "2811"
}
{
"intake_session_id": "6f9049fe-c05a-407c-8631-ffeaceb1aeb8",
"package_name": "",
"status": "failure",
"error": "Could not process a file with 0 bytes"
}
Authentication:
Incoming APIs are authenticated using a combination of appropriate api_key, along with corresponding project_id. Information for all keys can be found under the Project page and is accessible only by account administrators.
Outgoing APIs:
Overview:
There are 2 types of outgoing APIs. We provide both a webhook and an API. The webhook can be configured to route completed data to an external endpoint. The API is an API that works the same as the upload but will show the status of the requested data and will provide the extracted data upon finalization of the extraction.
API
Collector
Description
Collector – Upon finalization of a form extraction (inclusive of optional Scoring and QA phases), documents extracted data will be available to pull in from Iris via the ‘collector’ API. The collector will return the status of documents when called and upon finalization will gather the final extracted data and return it in a JSON format.
Example Call: Upload Document
{ "package_id": "34261",
"status": "complete",
"extracted_data": [
{
"file": "CMS-1500default",
"field_name": "1 - All",
"comment": null,
"error": null,
"field_value": "7"
}
],
"additional_info": [],
"comments": ""
}
{
"package_id": "34474",
"status": "processing",
"extracted_data": [],
"additional_info": [],
"comments": ""
}
{
"package_id": "34474",
"status": "unauthorized",
"extracted_data": [],
"additional_info": [],
"comments": "api_key does not match"
}
{
"package_id": "None",
"status": "failed",
"extracted_data": [],
"additional_info": null,
"comments": "'package_id' required inquery params, check query params of request"
}
Authentication:
Outgoing APIs are authenticated using a combination of appropriate api_key, along with corresponding package_id. The package_id is returned by the Upload Document API and can be found appended to the document ID in Iris. Information for the api_key can be found under the Project page and is accessible only by account administrators.
Webhook
Get Data
Description
Upon finalization of a form extraction (inclusive ofoptional Scoring and QA phases), documents can be exported programmatically viaAPI to an endpoint defined by an account administrator.
*Note: Endpoints are hosted not by Roots Automation, but bycustomers themselves and therefore the definition of those endpoints isentirely up to the owner/developer. Roots Automation does not provide technicalsupport for systems outside of the Iris platform.
Opening Document Export configuration menu:
Click "Document export" to open.
Screens:
URL– https URL where JSON definition of your form data will be sent
sample JSON payload:
<add payload>
Parameters – enter any additional URL parameters to be sent with request
Test – manually send a sample call to test configuration
Headers – enter any headers required by the receiving endpoint
Not finding an answer?
For additional support and documentation requests, please contact our team for more information.
Contact Support