Prokuria is a cloud-based, Software-as-a-Service Platform designed from the start to be easy and fast integrated with other systems.
In terms of technical implementation, Prokuria is based on an API model and is written in Microsoft .Net, Angular 7, and SQL Server.
Key points regarding Prokuria’s infrastructure:
- Cloud-based infrastructure, deployed in the Microsoft Azure Cloud
- Fully scalable infrastructure with automatic scaling
- Database redundancy, and geo-replication with automatic backups
- Service-oriented architecture
- Powerful API for seamless integrations
More details about our tech infrastructure can be found here: https://support.prokuria.com/kb/en/article/prokuria-tech-infrastructure-and-security
Ways of integrations
1. Through API
API integration is the connection between two or more applications, via their APIs, that lets those systems exchange data.
Prokuria is built on REST API infrastructure. REST API is the most popular and prevalent API for web-based services (that businesses use for ERPs, CRM, marketing platforms, etc.)
Our API is publicly available and documented on https://www.postman.com/
Please connect with our Sales team in order to get more details.
If you want to see it in action we can showcase :
- DocuSign (https://www.docusign.com/) – #1 platform for eSignature and Contract Management
- Microsft Power BI (https://powerbi.microsoft.com/en-us/) – data visualization tool, that allows you to unify data from many sources to create interactive, immersive dashboards and reports that provide actionable insights and drive business results.
For building and ad-hoc integration, we will need to understand:
- the business requirements for determining the data that needs to be exchanged and the workflow.
- the tech details and specs of the other system(s). Usually through a specific discussion with the technical team in charge of the other system.
2. Through the exchange of files (csv, xls, xml, or your specific format)
This method is simpler and much faster to implement but not as sophisticated as the first one. It will not create a real-time connection but in most cases having the information updated in the system every couple of hours is usually frequent enough.
The result in both cases will be the same – data exchange between the two systems so the data can be found in both applications.
Are you stuck somewhere? Don’t worry, we’re here for you. Drop us a mail at email@example.com and we’ll get back to you.