POST 1 - UNDERSTANDING WHAT'S INVOLVED IN MAKING API'S
Having had personal experience in having API's made, I thought it would be good for all of us to know what's involved so that our expectations for the relaunching of store.veemost.com match with what we are observing. So, the following is a breakdown of the process.
How long does it take an IT coder to make an API for a new product? The ones that I had experience with took 3 to 5 weeks, but were pretty simple and straight forward. It is good to remember that what VeeMost is doing would be in the 12-week area due to complexity, high security and multi-platform integration with Blockchain recording of all transactions.
Short answer: A typical API for a new product takes up to 12 weeks to build, depending on complexity, planning, design, development, testing, and deployment.
? What actually determines the timeline?
API development isn’t just writing code — it follows a full lifecycle with multiple stages. Across sources like Postman, IBM, and Moesif, the lifecycle consistently includes planning, design, development, testing, deployment, and monitoring.
Below is how long each stage typically takes in real-world teams:
1. Planning (1–2 weeks)
Teams define what the API needs to do, who will use it, and what data it exposes.
This stage is emphasized heavily in API-first approaches.
2. Designing (1–3 weeks)
Developers create the API contract (often Open API/Swagger), define endpoints, authentication, and data models.
Design-first is considered best practice because it accelerates development.
3. Development (2–6 weeks)
This is the coding phase — building endpoints, integrating databases, adding business logic, and implementing security.
Sources highlight that development is only one part of the lifecycle, not the whole timeline.
4. Testing (1–3 weeks)
Includes functional testing, performance testing, and security validation.
Testing is a formal stage in all lifecycle models.
5. Deployment (1 week)
Deploying to cloud or on-prem infrastructure, setting up API gateways, versioning, and monitoring.
Deployment is a distinct lifecycle stage across all sources.
6. Monitoring & Iteration (ongoing)
After launch, teams monitor usage, performance, and errors, then iterate.
Monitoring is a required lifecycle phase in all frameworks.
! Typical Timeline by Complexity
API Type Example Estimated Timeline
Simple API CRUD endpoints, no integrations 2–4 weeks
Moderate API Auth, database, external service integration 4–8 weeks
Complex API Multi-service, high security, real-time, enterprise 8–12+ weeks
These ranges align with the multi-stage lifecycle described by Postman, IBM, Moesif, and Gravitee.
# Why timelines vary so much
Key factors that stretch or shrink the timeline:
API-first vs code-first (API-first is faster overall)
Number of endpoints
Security requirements (OAuth2, JWT, SSO, etc.)
Integrations with other systems
Quality of documentation
Team size and experience
Whether the product is new or extending an existing platform. With VeeMost's store, we have both.
How many endpoints you expect
Whether it needs authentication
Whether it integrates with other systems
Whether it’s part of a larger product launch
jmo
Having had personal experience in having API's made, I thought it would be good for all of us to know what's involved so that our expectations for the relaunching of store.veemost.com match with what we are observing. So, the following is a breakdown of the process.
How long does it take an IT coder to make an API for a new product? The ones that I had experience with took 3 to 5 weeks, but were pretty simple and straight forward. It is good to remember that what VeeMost is doing would be in the 12-week area due to complexity, high security and multi-platform integration with Blockchain recording of all transactions.
Short answer: A typical API for a new product takes up to 12 weeks to build, depending on complexity, planning, design, development, testing, and deployment.
? What actually determines the timeline?
API development isn’t just writing code — it follows a full lifecycle with multiple stages. Across sources like Postman, IBM, and Moesif, the lifecycle consistently includes planning, design, development, testing, deployment, and monitoring.
Below is how long each stage typically takes in real-world teams:
1. Planning (1–2 weeks)
Teams define what the API needs to do, who will use it, and what data it exposes.
This stage is emphasized heavily in API-first approaches.
2. Designing (1–3 weeks)
Developers create the API contract (often Open API/Swagger), define endpoints, authentication, and data models.
Design-first is considered best practice because it accelerates development.
3. Development (2–6 weeks)
This is the coding phase — building endpoints, integrating databases, adding business logic, and implementing security.
Sources highlight that development is only one part of the lifecycle, not the whole timeline.
4. Testing (1–3 weeks)
Includes functional testing, performance testing, and security validation.
Testing is a formal stage in all lifecycle models.
5. Deployment (1 week)
Deploying to cloud or on-prem infrastructure, setting up API gateways, versioning, and monitoring.
Deployment is a distinct lifecycle stage across all sources.
6. Monitoring & Iteration (ongoing)
After launch, teams monitor usage, performance, and errors, then iterate.
Monitoring is a required lifecycle phase in all frameworks.
! Typical Timeline by Complexity
API Type Example Estimated Timeline
Simple API CRUD endpoints, no integrations 2–4 weeks
Moderate API Auth, database, external service integration 4–8 weeks
Complex API Multi-service, high security, real-time, enterprise 8–12+ weeks
These ranges align with the multi-stage lifecycle described by Postman, IBM, Moesif, and Gravitee.
# Why timelines vary so much
Key factors that stretch or shrink the timeline:
API-first vs code-first (API-first is faster overall)
Number of endpoints
Security requirements (OAuth2, JWT, SSO, etc.)
Integrations with other systems
Quality of documentation
Team size and experience
Whether the product is new or extending an existing platform. With VeeMost's store, we have both.
How many endpoints you expect
Whether it needs authentication
Whether it integrates with other systems
Whether it’s part of a larger product launch
jmo
2
