Integrating Document Processing into Existing Systems with Astera Server APIs
Astera Server APIs provide a powerful way to integrate automated workflows into existing enterprise systems, enabling businesses to streamline various data processing tasks. Users can schedule, execute and monitor data processing jobs on Astera’s Server programmatically as an alternative to using Astera’s Client application. By leveraging API-driven workflow execution, businesses can introduce automation without disrupting existing systems, ensuring a smooth transition to a more scalable and efficient system.
One critical application of this integration is document processing. Businesses often handle vast amounts of documents daily, ranging from invoices and reports to contracts and compliance forms. Manual document handling is time-consuming and prone to errors. To address these challenges, organizations can leverage Astera Server APIs to integrate automated document processing seamlessly into their existing systems while monitoring the file exchanges.
This document provides a technical guide for integrating document processing tasks into an enterprise system using Astera Server APIs. The use case focuses on calling an Astera flow from an external application, monitoring job execution, and tracking processed and failed files.
Use Case
A customer wants to automate document processing by integrating their system with Astera Server. The goal is to:
Trigger a report model (RM) processing flow from an external application.
Pass necessary parameters, such as file location, dynamically.
Monitor job execution status and retrieve processing results.
Track successfully processed files and capture details of failed jobs.
Solution Architecture
Authentication: Obtain an access token via the Astera Server authentication API.
Trigger Workflow Execution: Call the API endpoint to initiate the document processing workflow.
Monitor Job Execution: Query job status using the returned jobID.
Retrieve Processed Files: Fetch job logs to track successfully processed files.
Handle Errors: Capture details of failed files for further investigation.
Integration Steps
Note: In this document, we will use Postman to demonstrate the API requests for authentication, triggering workflows, and monitoring job execution. However, in a real-world scenario, customers may integrate these API calls directly into their own applications.
We have the following Document Processing flow designed in Astera:

This dataflow takes the following inputs:
A pdf bank statement that you want to extract data from
An excel destination file path, where you want to save the extracted data.
When the flow is run, structured data will be extracted from the unstructured pdf, passed through some custom data quality checks, and written to an excel file.
We can execute and monitor the execution status of this flow programmatically from an external system using the following steps:
Authentication
To interact with Astera Server APIs, first obtain an access token:
Request:
Response:
Trigger Document Processing Flow
Once authenticated, initiate the document processing flow by sending a request with the necessary parameters in the request body.
Request:
Response:

Monitor Job Execution
To check the job status, use the jobID returned from the previous step.
Request:
Response:

If the job fails, the response will notify us.

Handle Failures
If a job fails, such as in the above screenshot, capture the error details.
Request:
Response:

Conclusion
By leveraging Astera Server APIs, organizations can establish a structured and automated approach to data processing, ensuring compatibility with their existing system. External applications can trigger flows, monitor execution, and track job progress efficiently. This use case serves as an example of how Astera’s functionalities, such as document processing, can be integrated into existing data-driven workflows, enabling organizations to maximize their technological investments.
Last updated
Was this helpful?