fix(openapi): correct Create/Apply HTTP response codes#15
Merged
toumorokoshi merged 1 commit intoaep-dev:mainfrom Mar 30, 2026
Merged
Conversation
Create (POST) must return 201 Created per RFC 7231. Apply (PUT) must return 201 when creating a resource and 200 when updating.
3 tasks
rambleraptor
approved these changes
Mar 25, 2026
Member
rambleraptor
left a comment
rambleraptor
left a comment
There was a problem hiding this comment.
Provided we all agree on the spec change, this sounds great.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Create(POST) now returns201 Createdinstead of200 OK, per RFC 7231 §4.3.3Apply(PUT) now returns both200 OK(updated) and201 Created(created)This corrects an oversight from the aep-2026 release. Corresponding guidance changes are in aep-dev/aeps#406.
Test plan
201response200and201responses