Skip to content

Conversation

@ArchitectedDev
Copy link
Contributor

Removing statements that incorrectly refer to PUT requests in the OrderCloud API as being idempotent as this will typically cause the resource IDs to be regenerated by the platform.

Removing statements that incorrectly refer to PUT requests in the OrderCloud API as being idempotent as this will typically cause the resource IDs to be regenerated by the platform.
@robertsoniv
Copy link
Contributor

@ajsuth in order to do a PUT you have to have the ID (for the route param) so wouldn't you include that in your request body as well - avoiding the API generating a new ID?

@ArchitectedDev
Copy link
Contributor Author

@robertsoniv, thanks for the note. The primary goal was to remove the misinformation regarding idempotency for PUT requests. I see now that the removing the incorrect statements does not necessarily resolve the definition for PUT usage, so have updated it to be explicit that the ID is required for both the URI and request body.

@ArchitectedDev
Copy link
Contributor Author

@robertsoniv, are there any more changes that you would like to see here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants