API Lifecycle
Apiway manages your API from first upload to production runtime — and keeps managing it as your API evolves.
This section covers the specification-to-production path. That is one part of a wider chain: see What Product Delivery Means for the whole of it, from design through marketplace, consumer onboarding and billing, and Governed Context for the principles and decisions the work is done under.
The Journey
Section titled “The Journey”Every API follows the same path through the platform:
| Stage | What Happens |
|---|---|
| Design | Author or upload an OpenAPI 3.x specification. Recommendations service analyses your spec and suggests improvements. |
| Validate | Compliance service scores your spec against the OpenAPI standard and your custom rules. |
| Govern | API enters your organisation’s approval workflow. Reviewers assess design, security, and compliance. |
| Deploy | Gateway worker translates your API into proxy and policy documents. Deployed as a staging revision, then promoted. |
| Runtime | Gateway enforces security, rate limits, and policies. Resource usage is metered. Operational risks are tracked. |
| Evolve | Upload a new spec version. The cycle repeats — governance ensures every change is reviewed. |
In This Section
Section titled “In This Section”- Creating an API — Uploading specs and managing API metadata
- Quick Deploy — The automated 8-step deployment pipeline
- Versioning & Revisions — Major versions, SemVer, and blue-green deploys
- Environments — Managing dev, staging, and production targets