How long does it take to develop an API in your org? Any plans to compress that timeline and speed up API development?

5.8k viewscircle icon1 Upvotecircle icon7 Comments
Sort by:
Senior Director Of Technology in Software10 months ago

CRUD API - 1 day per API

API with business logics - 3 - 10 days depending on complexity

Service to Service API integrations - 3-5 days

We start with HLD for the project that takes 3-4 days for a bigger 2-3 sprints project and then proceed with LLD. For smaller features, its just LLD and that takes 1-2 days. 

Once LLD is in place, we share schema and mock APIs with UI team. 

We keep a buffer of 15% in timelines and 20% for integration testing and fixing QA bugs.

GTM takes another 10%-15% if its a customer facing feature.

CTO in Healthcare and Biotech10 months ago

It depends on the complexity, but usually it takes between 7 to 10 days to achieve it.

We use Python with FastAPI, these allows us to be this fast without decreasing quality.

All our SCRUM cards are managed in ClickUp.

Vice President, Software Engineering in Finance (non-banking)10 months ago

Depends on your organization’s maturity with infrastructure setup and skills. For simple CRUD operations using Stratum gateways give or take 2 weeks development followed by test and prod promotion. If you have a matured CI/CD pipeline and test automation in place that will compress your cycle time immensely.

If you want to streamline speed of delivery, focus on CI/CD pipeline and test automations.

Lightbulb on2
VP of IT in Education10 months ago

As others have said,  the real answer is it depends.  But, in my experience, it's weeks, not months to deploy integration using an API and move data across. 

Lightbulb on1
Global Chief Cybersecurity Strategist & CISO in Healthcare and Biotech10 months ago

In my experience with medium-sized companies, developing and deploying API connectors typically takes about 4-8 weeks, which includes requirements definition, development, testing, and deployment. I've found that the timeline can vary based on the complexity of the connectors and the number of systems being integrated.

Lightbulb on1

Content you might like

Return on Investment (ROI)44%

Total Cost of Ownership (TCO)41%

Net Present Value (NPV)23%

Internal Rate of Return (IRR)11%

Payback Period22%

Business Process Improvements (e.g., increased efficiency, reduced cycle times, or enhanced productivity)44%

Customer Satisfaction and Retention30%

Competitive Advantage18%

Risk Mitigation27%

Ability to Foster Innovation and Agility14%

Employee Satisfaction19%

Something Else (share in a comment!)3%

View Results

Exploring – We are aware of SAP Joule but have not yet started any formal evaluation or planning.15%

Evaluating – We are actively assessing SAP Joule’s capabilities and fit for our business needs.55%

Piloting – We have initiated a limited rollout or proof of concept in selected areas.10%

Scaling – We are expanding SAP Joule adoption across multiple business units, processes or systems.10%

Operationalized – SAP Joule is fully integrated into our operations and delivering measurable value.10%

View Results