docs(api-reference): add attachment API endpoints - #131
Draft
Yash1hi wants to merge 1 commit into
Draft
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
🖼️ Image Usage Check ✅All 247 images in the repository are being used! No unused images found. Great job keeping the repository clean! 🎉 |
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
1 participant
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.
Adds the Attachments API to the reference — session-attachment upload and management endpoints, matching the current
mainschemas.openapi.yaml: +4 paths (POST /attachments,POST /attachments/{attachmentId}/commit,GET/DELETE /attachments/{attachmentId},GET /sessions/{sessionId}/attachments) and theAttachmentschema. Spliced into the existing spec so all 35 existing SDK code samples are preserved (the diff is purely additive).docs.json: new Attachments nav group.api-reference/*.mdxpages, one per operation.Note: the attachment endpoints don't carry JS/Python code samples yet — those are generated by Stainless when the SDK ships these endpoints. Everything else keeps its samples.
Test plan
openapi.yamlparses and every$refresolves (validated locally)Attachmentschema are present; existing endpoints'x-codeSamplesunchanged.mdxrenders its endpoint (frontmatteropenapi:matches a spec operation)