-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathapis.yml
More file actions
170 lines (170 loc) · 6.48 KB
/
Copy pathapis.yml
File metadata and controls
170 lines (170 loc) · 6.48 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
aid: api-first
name: API-First
kind: topic
description: >-
API-First is a software development methodology where APIs are treated as
first-class citizens and designed before implementation begins. In an
API-first approach, teams establish API contracts as the foundation of
architecture, enabling parallel development, reusable services, consistent
interfaces, and faster time-to-market. Organizations adopting API-first
report 30-40% faster product releases (Gartner 2025) and significantly
improved developer experience. The approach is foundational for
microservices, headless architectures, and AI agent integrations.
type: Index
accessModel:
pricing: freemium
onboarding: unknown
trial: false
try_now: false
public: false
label: Freemium
confidence: medium
source:
- plans
generated: '2026-07-22'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/api-first.png
tags:
- API Design
- Development Methodology
- Software Architecture
- API Governance
- Microservices
url: >-
https://raw.githubusercontent.com/api-evangelist/api-first/refs/heads/main/apis.yml
created: '2025-01-01'
modified: '2026-04-19'
specificationVersion: '0.19'
apis:
- aid: api-first:swagger-io
name: SwaggerHub - API-First Platform
description: >-
SmartBear's SwaggerHub provides an API-first collaborative design
platform with OpenAPI support, auto-generated documentation, mock
servers, SDKs, and governance tooling for enterprise teams.
humanURL: https://swagger.io/resources/articles/adopting-an-api-first-approach/
tags:
- API Design
- OpenAPI
- API-First
properties:
- type: Documentation
url: https://swagger.io/resources/articles/adopting-an-api-first-approach/
- aid: api-first:stoplight
name: Stoplight - API Design Platform
description: >-
Stoplight provides a collaborative API design platform with visual
OpenAPI editing, style guides, governance, mock servers, and developer
portals supporting API-first workflows.
humanURL: https://stoplight.io
tags:
- API Design
- API Governance
- OpenAPI
properties:
- type: Documentation
url: https://stoplight.io/api-design-guide/basics
- aid: api-first:postman
name: Postman - API Platform
description: >-
Postman provides an API platform supporting API-first design with
collaborative workspace, design-first features, mock servers,
testing, and documentation generation.
humanURL: https://www.postman.com
tags:
- API Design
- API Testing
- API-First
properties:
- type: Documentation
url: https://www.postman.com/api-first/
- aid: api-first:nordic-apis
name: Nordic APIs
description: >-
Nordic APIs is a leading API education and conference organization
providing resources, guides, and community for API-first practitioners.
humanURL: https://nordicapis.com
tags:
- API Education
- API Community
- API-First
properties:
- type: Documentation
url: https://nordicapis.com/a-software-architects-guide-to-api-first-strategy/
common:
- type: DomainSecurity
url: security/api-first-domain-security.yml
- type: Website
url: https://swagger.io/resources/articles/adopting-an-api-first-approach/
- type: Documentation
url: https://nordicapis.com/a-software-architects-guide-to-api-first-strategy/
- type: Features
data:
- name: API Contracts
description: >-
Establish agreed-upon API contracts before coding begins, ensuring
all teams align on endpoint names, request/response schemas,
error codes, and versioning conventions.
- name: Parallel Development
description: >-
Teams can develop front-end, back-end, and third-party integrations
simultaneously using API contracts as the shared reference point.
- name: Reusability
description: >-
APIs designed first become autonomous, reusable services that can
be leveraged across multiple products and teams.
- name: API Governance
description: >-
Centralized governance processes including style guides, peer
reviews, and validation tooling ensure consistency across the API
portfolio.
- name: Developer Portal
description: >-
Internal developer portals provide API inventories, documentation,
dashboards, and self-service access enabling developer productivity.
- type: UseCases
data:
- name: Microservices Architecture
description: >-
Design independent microservices with well-defined API contracts
enabling loose coupling and independent deployment.
- name: Headless Commerce and CMS
description: >-
Build headless platforms like Shopify where third-party apps and
extensions integrate through well-designed APIs.
- name: Fintech Integration
description: >-
Enable payment integrations and financial service APIs following
Stripe's model of simple, well-documented API design.
- name: Healthcare Interoperability
description: >-
Design EHR systems and healthcare APIs API-first for compliance
with HL7 FHIR and other interoperability standards.
- name: AI Agent Integration
description: >-
Provide clean, discoverable, semantically-rich APIs that AI agents
can autonomously discover and consume without human intervention.
- type: Integrations
data:
- name: OpenAPI
description: >-
OpenAPI 3.x is the dominant standard for documenting REST APIs
in an API-first workflow, with broad tool support for generation,
validation, and mocking.
- name: AsyncAPI
description: >-
AsyncAPI 3.0 provides the standard for documenting event-driven
APIs, WebSockets, and message-driven architectures in API-first
workflows.
- name: CI/CD Pipelines
description: >-
API contracts are integrated into CI/CD pipelines for automated
linting, validation, mock server generation, and contract testing.
- name: Developer Portals
description: >-
Internal developer portals aggregate API inventory, documentation,
and governance dashboards as the operational home for API-first
organizations.
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com