Overview

The AlgoDocs API v1 is a set of HTTP endpoints that help your app integrate with AlgoDocs. This API Documentation will be helpful for any language of your choice.

On the right panel you will find commands along with their response messages.

To use this API, you need a Secret API key. Please register at https://algodocs.com/register to get your own API key if you haven't done so yet.

Libraries

You can use the following available AlgoDocs API Libraries:

• AlgoDocs API Python Client
• AlgoDocs API PHP Client

Authentication

All requests to AlgoDocs API are made with one of the authentications below. Every authentication method requires the use of an API key that you can obtain at your AlgoDocs account here.

• Basic Auth
• API Key

For testing your authentication method use the endpoint given below by setting appropriate parameters for each type of authentications as explained in the next sections.
GET https://api.algodocs.com/v1/me

In remaining sections we will use Basic Auth for demonstrating requests to the API.

Basic Auth

# CURL Request Example:

curl \
https://api.algodocs.com/v1/me \
--user '<email_address>:<api_key>'

With Basic Auth you can make requests to AlgoDocs API by passing two parameters as shown in the table below. These parameters are encoded in base64:
base64('<email_address>:<api_key>')

A sample response is shown on the right, which contains your full name and email address.

    JSON Response Example:

    {
        "fullName": "John Doe",
        "email": "john@example.com"
    }

HEADER PARAMETERS

API Key

# CURL Request Example:

curl \
https://api.algodocs.com/v1/me \
-H 'x-api-key: <api_key>'

With API Key authentication you can make requests to AlgoDocs API by passing API Key only.

A sample response is shown on the right, which contains your full name and email address.

    JSON Response Example:

    {
        "fullName": "John Doe",
        "email": "john@example.com"
    }

HEADER PARAMETERS

List Document Data Extractors

# CURL Request Example:

curl \
https://api.algodocs.com/v1/extractors \
--user '<email_address>:<api_key>'

    JSON Response Example:

    [
        {
            "id": "6d86215bf9cb4fc6ac1f6967",
            "name": "Invoice Extractor"
        },
        {
            "id": "6a0cdd3949444cf189e62416",
            "name": "Bank Statement Extractor"
        },
        {
            "id": "98b8a0332f39424e883bea24",
            "name": "Medical Reports Extractor"
        },
        ...
    ]

In order to get a list of extarctors from your account you can call an API with the endpoint shown on the right. This returns a list of extractors with id and name fields. The id field will be used in the following API calls.

GET https://api.algodocs.com/v1/extractors

A sample response is shown on the right, which contains a list of extractors you created in your account.

List Folders

# CURL Request Example:

curl \
https://api.algodocs.com/v1/folders \
--user '<email_address>:<api_key>'

    JSON Response Example:

    [
        {
            "id": "1a5e2f9c624b",
            "parentId": null,
            "name": "root"
        },
        {
            "id": "c40daa5550d9",
            "parentId": "1a5e2f9c624b",
            "name": "Invoices"
        },
        {
            "id": "tksa9ndu1p2f",
            "parentId": "1a5e2f9c624b",
            "name": "Bank Statements"
        },
        ...
    ]

AlgoDocs provides a file manager in which you can create folders and subfolders for organizing your documents. This API endpoint returns a list of folders with id, parentId and name fields. Where parentId is the id of the parent folder. The id field will be used in the following API calls when importing documents to AlgoDocs for specifying the folder under which to save the document.

GET https://api.algodocs.com/v1/folders

A sample response is shown on the right, which contains a list of folders you created in your file manager.

Import Documents

Using AlgoDocs API you can import documents to AlgoDocs by either one of the following two options:

• Upload Document From Local Path
• Upload Document From URL
• Upload Document With Base64

Upload Document From Local Path

    
# CURL Request Example:
curl \
"https://api.algodocs.com/v1/document/upload_local/<extractor_id>/<folder_id>" \
-F "file=@path/to/your/file.pdf" \
--user '<email_address>:<api_key>'

    JSON Response Example:

    {
        "id": 182609,
        "fileSize": 136925,
        "fileMD5CheckSum": "955C30272DC75F119F17023683A787D5",
        "uploadedAt": "2017-06-18T14:03:24Z"
    }

With this endpoint you can upload your local file to AlgoDocs.

This endpoint requires extractor_id and folder_id that are obtained when getting a list of extractors and folders from your AlgoDocs account. See Extractors and Folders sections respectively above.
In addition to these, a file parameter is set to the path of your file that is stored in your hard drive or network.

POST "https://api.algodocs.com/v1/document/upload_local/<extractor_id>/<folder_id>"

A sample response is shown on the right, which contains a document id and other related fields. Note that this id will be used in the following sections when extracting data, which is used as document_id.

QUERY PARAMETERS

Upload Document From URL

    
# CURL Request Example:
curl \
"https://api.algodocs.com/v1/document/upload_url/<extractor_id>/<folder_id>" \
-F "url=https://api.algodocs.com/content/SampleInvoice.pdf" \
--user '<email_address>:<api_key>'

    JSON Response Example:

    {
        "id": 182610,
        "fileSize": 136925,
        "fileMD5CheckSum": "955C30272DC75F119F17023683A787D5",
        "uploadedAt": "2017-06-18T14:44:11Z"
    }

With this endpoint you can upload your file to AlgoDocs by fetching it from publicly available url.

This endpoint requires extractor_id and folder_id that are obtained when getting a list of extractors and folders from your AlgoDocs account. See Extractors and Folders sections respectively above.
In addition to these, a url parameter is set to the publicly available url of your file.

POST "https://api.algodocs.com/v1/document/upload_url/<extractor_id>/<folder_id>"

A sample response is shown on the right, which contains a document id and other related fields. Note that this id will be used in the following sections when extracting data, which is used as document_id.

QUERY PARAMETERS

Upload Document With Base64

    # CURL Request Example:
    curl \
    "https://api.algodocs.com/v1/document/upload_base64/<extractor_id>/<folder_id>" \
    -F "file_base64=<base64string>" \
    "filename=<SampleDocument.pdf>" \
    --user '<email_address>:<api_key>'

    JSON Response Example:

    {
        "id": 182610,
        "fileSize": 136925,
        "fileMD5CheckSum": "955C30272DC75F119F17023683A787D5",
        "uploadedAt": "2017-06-18T14:44:11Z"
    }

With this endpoint you can upload your file to AlgoDocs in base64 string format.

This endpoint requires extractor_id and folder_id that are obtained when getting a list of extractors and folders from your AlgoDocs account. See Extractors and Folders sections respectively above.
In addition to these, a file_base64 parameter is set to the base64 string of your file and a filename parameter is set to the file name.

POST "https://api.algodocs.com/v1/document/upload_base64/<extractor_id>/<folder_id>"

A sample response is shown on the right, which contains a document id and other related fields. Note that this id will be used in the following sections when extracting data, which is used as document_id.

QUERY PARAMETERS

Extracted Data

Using AlgoDocs API you can get extracted data of a single or multiple documents.

Get Extracted Data of a Single Document

# CURL Request Example:
curl \
"https://api.algodocs.com/v1/extracted_data/<document_id>" \
--user '<email_address>:<api_key>'

    JSON Response Example:

    [
        {
            "id": "5fe7608abd59783e98438b3e",
            "documentId": 182608,
            "uploadedAt": "2017-06-20T16:10:21Z",
            "processedAt": "2017-06-20T16:10:50Z",
            "fileName": "Invoice.pdf",
            "folderId": "078f5vn8ocoy",
            "mediaOriginal": "https://api.algodocs.com/v1/media/niGNFZgpj655iThANTDhIgE3lQoSagCbsBkw0PRhzAo7DeanCToefGYGdd1pbYOC4udg8l9xBWiHr70HgAQQsXwmceSnn2FammDJAtOQjqdSXROGMUIaIxKGxrDu2mJ8/1/original",
            "mediaExcel": "https://api.algodocs.com/v1/media/niGNFZgpj655iThANTDhIgE3lQoSagCbsBkw0PRhzAo7DeanCToefGYGdd1pbYOC4udg8l9xBWiHr70HgAQQsXwmceSnn2FammDJAtOQjqdSXROGMUIaIxKGxrDu2mJ8/1/excel",
            "mediaJson": "https://api.algodocs.com/v1/media/niGNFZgpj655iThANTDhIgE3lQoSagCbsBkw0PRhzAo7DeanCToefGYGdd1pbYOC4udg8l9xBWiHr70HgAQQsXwmceSnn2FammDJAtOQjqdSXROGMUIaIxKGxrDu2mJ8/1/json",
            "mediaXml": "https://api.algodocs.com/v1/media/niGNFZgpj655iThANTDhIgE3lQoSagCbsBkw0PRhzAo7DeanCToefGYGdd1pbYOC4udg8l9xBWiHr70HgAQQsXwmceSnn2FammDJAtOQjqdSXROGMUIaIxKGxrDu2mJ8/1/xml",
            "totalPages": 1,
            "pageNumber": 1,
            "data":
                {
                    "InvoiceNumber": "11223344",
                    "Date": "2017-04-15",
                    "Amount": 1250.0,
                    ...
                }
        },
        ...
    ]

This API endpoint returns the extracted data of a single document. However, in cases when a document is split by AlgoDocs into multiple documents, i.e. when, for example, 'Apply to pages' option in extracting rules is set to 'Apply to each remaining page independently', then the returned data will have multiple records. Therefore, the returned data is always a list, not an object.

This endpoint requires document_id parameter that is obtained when uploading a document to AlgoDocs. See Documents section above.

GET "https://api.algodocs.com/v1/extracted_data/<document_id>"

A sample response is shown on the right, which contains a list of extracted data records. Each record in a list contains system generated fields from id to pageNumber. Remaining fields are user defined ones that come from the extractor for which user defines the rules to extract certain fields/data. So, in this response example we have InvoiceNumber, Date and Amount fields that are user defined.