Skip to content

docs(dev): fix OCS Share API success statuscodes for v2 (200) - #15718

Open
whoalin1 wants to merge 1 commit into
nextcloud:masterfrom
whoalin1:docs-ocs-share-api-v2-statuscodes
Open

whoalin1 wants to merge 1 commit into
nextcloud:masterfrom
whoalin1:docs-ocs-share-api-v2-statuscodes

Conversation

@whoalin1

@whoalin1 whoalin1 commented Oct 6, 2026 •

Copy link
Copy Markdown

Summary

Correct OCS Share API success statuscodes for the documented /ocs/v2.php base URL.

  • Document that OCS v2 returns meta <statuscode> 200 on success (v1 used 100).
  • Replace outdated 100 - successful bullets with 200 - successful so they match the v2 base URL and the already-correct send-email endpoint.
  • Error codes left unchanged.

Closes #10899

Test plan

  • Sphinx build of the developer manual succeeds for ocs-share-api.rst
  • Intro note explains v2 → 200 vs v1 → 100
  • Every local + federated endpoint success bullet is 200 - successful (including Create)
  • send-email still lists 200 - successful (no duplicate/regression)
  • No unrelated edits (hideDownload / shared_with_me live in a separate prep if needed)

AI disclosure

This PR was drafted with the help of AI coding assistants (Cursor agents / LLM-based tools), including the description. I am responsible for it and happy to rework anything that doesn't fit.

All commits carry an Assisted-by: Cursor:grok-4.7 trailer.

Assisted-by: Cursor:grok-4.7
Signed-off-by: whoalin1 <[email protected]>
@whoalin1
whoalin1 force-pushed the docs-ocs-share-api-v2-statuscodes branch from 3e55bad to fdf20f9 Compare October 9, 2026 14:11

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.

Possible statuscodes from the OCS share API

1 participant