Skip to content

Align the 2.17 custom object instance endpoints with what the API does - #754

Open
markdennis22 wants to merge 2 commits into
mainfrom
markdennis/2-17-custom-object-instance
Open

markdennis22 wants to merge 2 commits into
mainfrom
markdennis/2-17-custom-object-instance

Conversation

@markdennis22

Copy link
Copy Markdown
Contributor

Why?

The 2.17 spec for the custom object instance endpoints didn't match the API. The two delete operations had each other's operationIds, the create request typed every custom attribute as a string, and several error responses were missing. Only the 2.17 spec changes, and the SDKs aren't generated from 2.17, so they are unaffected.

How?

Corrects the custom object instance endpoints and their request schema to match the API's current behaviour, and adds the OAuth scopes each endpoint accepts to its description.

Generated with Claude Code

markdennis22 and others added 2 commits October 22, 2026 09:50
Swaps the two delete operationIds so each matches its path, types custom_attributes values in the create request, documents the 400s and the delete 404s the API returns, explains the external_id lookup, and adds the accepted OAuth scopes to each operation.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A list body also matches the single-instance schema, which requires no properties, so oneOf would reject an ordinary list response.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant