Portfolio

API Solution for SaaS Provider

Streamlining processes with a custom API solution for SaaS

The client is a SaaS provider with a mission to make legal expertise more accessible to the general public. With their data- powered technology platform, users can effectively manage claims at a lower cost and better business outcomes. After reaching out to egforit Software, we created an automated API solution for developmental projects. Meaning any advancements in their tech capabilities could be transferred from one solution to the next with ease.

 

As part of that solution, we also launched a sitemap to help the business find clarity on security and user permissions.

Executive brief

Supplying the skillset to API solution

Considering the clients business model, it was clear they already had a substantial tech skillset. But there was a deficit in this specific area, they had an in-house team capable of delivering the solution themselves, but not enough knowledge needed to architect it in the required way to achieve their goals. 

 

So, they reached out to us, confident we had the expertise needed to help them architect the solution and get it initially into place so that they could then build on it.  

The Solution

The API solution had three goals

By the end of the project, the client expected three key deliverables from our API solution. Here’s what we delivered: 

  • A selection of Azure environments that were connected to host API suite 
  • A fully automated deployment pipeline – allowing them to manage configurations etc 
  • Wiki/developer focused documentation – an interactive wiki that could also be updated in real time

The Results

An enhanced SharePoint information hub with more to come

The implementation of Azure environments enabled the client to get the following results:

 

Speed of service

Visitors to the site didn’t need to worry about downtime, they were able to find a fast and efficient solution. There was also ongoing reliability improvements which ensured the solution kept running.

Enhanced flexibility

No more dealing with clunky systems. Their new solution was completely flexible to their needs.

Disaster recovery

To further comply with their data protection needs, their new solution had an undefeatable disaster recovery system in place.

Wiki/developer focused documentation  

Developing interactive wiki allows staff and decision makers access documentation to better build upon the solution. They can easily access what’s been built, why it was build, and the benefits of the build. 

Other benefits of the new API solution include:

  • Integrated delivery pipeline 
  • versioning capabilities  
  • reliability improvements 
  • Deployment pipeline 

This allowed the client to set numerous stages in the development and testing phase to ensure the quality of your project as you progress. 

Need help building a custom solution?

Need help building a custom API solution? Our team is skilled in custom development, meaning you get exactly what you want, and when you want it.

Contact us today

Info

24th October 2022

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by egforit.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress,
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
-id-[app_id],-session-[add-id]

×