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 Softwarea year 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 Biotecha year 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)a year 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 Educationa year 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 Biotecha year 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

Yes, we have some significant issues running Kubernetes15%

Somewhat, but we’ve only run into minor problems67%

No, Kubernetes has always run well for our org17%

N/A — not using Kubernetes2%

View Results

Yes, I am looking at consolidating multiple vendor solutions81%

No, I am fine with managing multiple vendors18%