Practice essential collocations for API design in IT and software development.
0 / 5 completed
1 / 5
The backend team met with consumers to ___ endpoints for the new payment service before writing a single line of code.
Define endpoints is the standard API design collocation for specifying the URLs, methods, and parameters of a REST or GraphQL API. 'Design along' and 'create around' are informal. 'Plan out' is too generic for the precise act of endpoint definition.
2 / 5
The team decided to ___ APIs using URL path prefixes such as /v1/ to maintain backward compatibility.
Version APIs is the standard API design collocation for introducing versioning schemes that allow breaking changes without disrupting existing consumers. 'Label along' and 'tag around' are informal. 'Mark out' does not convey the structured versioning strategy.
3 / 5
The API gateway was configured to ___ errors consistently and return standardised problem detail objects.
Handle errors is the standard API design collocation for processing failure conditions gracefully and returning meaningful error responses to clients. 'Manage along' and 'process around' are informal. 'Catch out' implies trapping errors in code rather than the API-level handling pattern.
4 / 5
The API contract required all endpoints to ___ responses in JSON format with consistent field naming.
Return responses is the standard API and REST design collocation for delivering data back to the caller from an API endpoint. 'Send along' and 'give around' are informal. 'Output out' is redundant and not a standard phrase.
5 / 5
The team used an OpenAPI specification to ___ contracts and share them with front-end and mobile consumers.
Document contracts is the standard API design collocation for formally recording the interface agreement between an API provider and its consumers. 'Write along' and 'describe around' are informal. 'Publish out' is too generic for API contract documentation.