API Management

Overview:

One of the many benefits of the Sift system is that all employee data is centralized for clients. Client side Software Engineers often request to get access to their companies employee data through API to run reports on Skills, Headcount, New Hires etc. The API request involved Sift engineers to handle the task becoming time consuming and costly.

Collaborating with the head of engineering, I led the overall design of the workflow that would allow client-side Software Engineers to request and develop their own API tokens.

Problem to solve:

Client side engineers do not have an efficient way to access their Sift instance employee data through API service.

Sift Opportunity:

1. Ante to play in SaaS, Aligns with our mission of helping organizations collect people's information to bring insight and empower organizations

2. What problem are we trying to solve?

   • Give access to aggregated data back to the organization

3. How does this product benefit the customer?

   • Provide an alternative option for accessing all people's data in one central place

4. What business opportunities does it create?

   • Sales opportunity. Grow our footprint in the organization.

Measures of Success (Google HeartFrameWork)

1. Adoption

   1. Goal - For users to turn on and use the API feature

   2. Signal - For users to turn on and use the API feature

   3. Metric - Number of API tokens created - Active API feature

2. Task Success

   1. Goals - Ensure that engineers are able to request and get access to API, Ensure that engineers know how to manage the API access given

   2. Signal - # of API token applications created ,# of API tokens revoked/updated ,Avg # of engineers that have access per client instance
      
      

Solution:

Engineer filling out API request form & Approval: Engineers must complete a simple form explaining what they intend to use the API for and the type of data access needed. The second screenshot is an approved API token by the engineering manager.

Engineer filling out API request form & Approval
Engineers must complete a simple form explaining what they intend to use the API for and the type of data access needed. The second screenshot is an approved API token by the engineering manager.

Engineering Manager Reviewing API Application
Engineers must complete a simple form explaining what they intend to use the API for and the type of data access needed. The second screenshot is an approved API token by the engineering manager.

API Management - For Software Engineer
After the API Token is approved by the Engineering Manager. The Staff engineer will now have access to their API that also incudes usage data, status and access.

Engineering Manager Reviewing API Application
Engineers must complete a simple form explaining what they intend to use the API for and the type of data access needed. The second screenshot is an approved API token by the engineering manager.

Outcome:

Post-implementation, UrbanRetail observed a 65% reduction in average checkout times. Customer feedback was overwhelmingly positive, with a noted appreciation for the convenience and efficiency of the new system. The dual benefit of enhanced customer experience and efficient inventory management led to a 20% increase in monthly sales.