REST API design patterns — response envelopes, pagination, filtering, status codes, and resource naming
87
83%
Does it follow best practices?
Impact
98%
1.78xAverage score across 4 eval scenarios
Passed
No known issues
success-response-envelope
0%
100%
error-response-envelope
25%
100%
list-endpoint-paginated
0%
100%
filtering-support
100%
100%
plural-noun-resource-paths
50%
100%
201-for-creation
62%
100%
bulk-receiving-endpoint
100%
100%
bulk-max-size
0%
100%
bulk-per-item-results
66%
100%
transfer-validation
50%
100%
404-for-not-found
66%
100%
pagination-metadata
0%
100%
safe-defaults
0%
100%
validation-error-status
66%
100%
success-response-envelope
0%
100%
error-response-envelope
25%
100%
nested-resource-for-customer-orders
0%
100%
plural-noun-resource-paths
50%
66%
list-endpoint-paginated
0%
100%
filtering-by-status
100%
100%
201-for-order-creation
100%
100%
order-includes-line-items
100%
100%
patch-shipping-address
100%
100%
cancel-status-validation
100%
100%
batch-status-update
100%
100%
batch-max-size
0%
100%
404-for-not-found
100%
100%
204-for-delete-or-cancel
100%
100%
success-response-envelope
0%
100%
error-response-envelope
30%
100%
list-endpoint-paginated
0%
100%
pagination-metadata
0%
100%
default-and-max-limit
0%
100%
filtering-support
100%
100%
201-for-post
100%
100%
204-for-delete
100%
100%
404-for-not-found
100%
100%
plural-noun-resource-path
100%
100%
patch-partial-update
100%
100%
patch-returns-full-resource
100%
100%
validation-error-status
80%
100%
success-response-envelope
0%
100%
error-response-envelope
0%
100%
list-endpoint-paginated
0%
100%
filtering-by-role-and-status
100%
100%
sorting-support
100%
100%
search-support
100%
100%
201-for-post
100%
100%
409-for-duplicate-email
100%
100%
patch-partial-update
100%
100%
plural-noun-resource-path
100%
100%
deactivate-not-delete
33%
50%
404-for-not-found
100%
100%
safe-defaults
16%
100%