Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with api-design
Search options not deleted
user 27308
Application Programming Interface (API) Design discusses best practises for creating libraries intended for general purpose or public use.
16
votes
3
answers
4k
views
Versioning REST APIs. Each API has its own version
It's very common to specify the version of REST APIs in the URL, specifically at the beginning of path, i.e. something like:
POST /api/v1/accounts
GET /api/v1/accounts/details
However, I haven't se …
- 269