JobCannon
全部技能

APIs & REST Design

Build scalable, maintainable web APIs that power modern applications

⬢ 層級 2技術
+$25k-
薪資影響
4 個月
學習時長
中等
難度
2
職業
一覽

REST (Representational State Transfer) is the dominant web API architecture: design URLs around resources, use HTTP verbs (GET/POST/PUT/DELETE) correctly, version from day one. Career: Consumer (read docs, use Postman, $85-115k) → Designer (build production APIs, OpenAPI, versioning, $115-165k) → Architect (microservices, API gateways, hypermedia, $150-230k). Pricing: free to build. Lives with HTTP/2, OAuth, JWT, pagination, rate limiting, versioning strategies.

什麼是 APIs & REST Design

APIs (Application Programming Interfaces) are how software talks to software. REST (Representational State Transfer) is the dominant architectural style for web APIs. In 2026, API design is a critical skill for backend engineers, full-stack developers, and technical leaders. - Backend foundation: Every modern app uses APIs (mobile → backend, frontend → backend)

🔧 工具與生態
OpenAPIPostmanInsomniaSwagger UIRedoclyJSON SchemaBrunoStoplightReadMeAPI BlueprintSwagger EditorDredd

💰 各地區薪資

地區初級中級高級
USA$95,000$135,000$185,000
UK£55,000£80,000£115,000
EU€60,000€85,000€125,000
CANADACA$100,000CA$145,000CA$195,000

🎯 使用 APIs & REST Design 的職業

Software Engineer
Technical Writer

❓ 常見問題

REST vs GraphQL, which should I choose?
REST: simpler, stateless, caches well, multiple requests for relations. GraphQL: one request, flexible queries, over-fetching eliminated, complex to implement. For 90% of APIs: REST. For complex data graphs (mobile apps, dashboards): GraphQL. Most teams use both (REST for public APIs, GraphQL for internal/mobile).
What do HTTP status codes really mean?
2xx = success (200 OK, 201 Created, 204 No Content). 3xx = redirect. 4xx = client error (400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found). 5xx = server error (500 Internal, 503 Service Unavailable). Never return 200 for errors, status codes are your error handling.
How do I paginate large datasets?
Offset/limit: ?page=2&limit=20 (simple, breaks with deletes). Cursor-based: ?cursor=abc123&limit=20 (stable, scales). Keyset: ?after_id=123&limit=20 (fastest for huge tables). Return pagination metadata: {data: [], pagination: {page, limit, total, pages}}.
How do I version my API?
URL versioning (/v1/users, /v2/users) is most common. Header versioning (Accept: application/vnd.api.v2+json) is cleaner but harder to test in browsers. Never break without versioning, deprecate old versions 6-12 months before removal. Parallel versions = customers migrate at their own pace.
What's the difference between PUT and PATCH?
PUT: full replacement (idempotent, same request = same result). PATCH: partial update (may not be idempotent). Most APIs use PATCH for convenience, but PUT is cleaner semantically. Both should be idempotent for retries.
Do I need hypermedia (HATEOAS) in my API?
HATEOAS (links in responses) is REST-pure but adds complexity. For public APIs: optional (most skip it). For internal APIs: document relations in docs instead. If client needs to discover endpoints: include links in response. If client knows endpoints: skip hypermedia.
What are REST API naming conventions?
Use nouns, not verbs (/users not /getUsers). Plural resources (/users, /products). Nested for relations (/users/123/posts). Hyphens for multi-word routes (/user-preferences). Query params for filters (/users?status=active). Use HTTP verbs for actions, not URLs.

不確定這項技能適不適合你？

做一下職業匹配，我們會推薦合適的方向。

找到最適合我的技能 →

找到理想的職業方向

在 2,521 個職業中進行技能匹配。免費。

免費做職業匹配 →