Skip to content

feat: API specs update for version latest#72

Merged
ChiragAgg5k merged 1 commit into
mainfrom
feat-latest-specs
Jun 9, 2026
Merged

feat: API specs update for version latest#72
ChiragAgg5k merged 1 commit into
mainfrom
feat-latest-specs

Conversation

@appwrite-specs

Copy link
Copy Markdown

This PR contains API specification updates for version latest.

@greptile-apps

greptile-apps Bot commented May 28, 2026

Copy link
Copy Markdown

Greptile Summary

This PR introduces a new apps API surface (11 CRUD + secrets/team/token endpoints for OAuth2 client applications) across all six spec files, alongside new oauth2, healthGetAuditsDB, Amazon SES messaging, and project endpoints. It also adds x-appwrite.idGenerator annotations to user ID fields and format: \"password\" to password parameters.

  • New apps/* endpoints (appsList, appsCreate, appsGet, appsUpdate, appsDelete, appsListSecrets, appsCreateSecret, appsGetSecret, appsDeleteSecret, appsUpdateTeam, appsDeleteTokens) are added in all six specs representing a full OAuth2 application management surface.
  • New OAuth2 authorization-server endpoints (oauth2Approve, oauth2Authorize, oauth2CreateGrant, oauth2GetGrant, oauth2Reject) and a new healthGetAuditsDB health check are introduced in the server and console specs.
  • Inconsistency between OpenAPI3 and Swagger2 specs: all 11 apps* operations carry a duplicate \"server\" entry in their platforms arrays in every OpenAPI3 file ([\"console\",\"client\",\"server\",\"server\"]) while the Swagger2 equivalents correctly list it once — this could cause duplicate SDK method emission in generators that iterate rather than deduplicate.

Confidence Score: 4/5

Safe to merge if the duplicate platform entry in the OpenAPI3 specs is confirmed to be harmless to the SDK generators in use, or is fixed first.

All three OpenAPI3 spec files list "server" twice in the platforms array for every new apps* endpoint, while the Swagger2 counterparts list it only once. If the SDK generation pipeline iterates over the array without deduplication, it will attempt to emit the server binding twice for each of the 11 affected endpoints, producing compile errors or duplicate method registrations in generated clients.

All three OpenAPI3 spec files — open-api3-latest-client.json, open-api3-latest-server.json, and open-api3-latest-console.json — need the duplicate "server" entry removed from the platforms arrays of the new apps* operations.

Important Files Changed

Filename Overview
specs/latest/open-api3-latest-client.json Adds 11 new apps/* endpoints and various annotations; all apps* operations contain a duplicate "server" entry in their platforms arrays (["console","client","server","server"]) that is absent in the swagger2 counterpart.
specs/latest/open-api3-latest-server.json Adds apps/, oauth2, healthGetAuditsDB, SES messaging, and project endpoints; all new apps operations carry the duplicate "server" platform entry consistent with the client spec bug.
specs/latest/open-api3-latest-console.json Adds apps/* endpoints alongside compute and other new operations; duplicate "server" platform entry present in all apps* operations matching the other OpenAPI3 spec files.
specs/latest/swagger2-latest-client.json Adds apps/* and related endpoints; platforms arrays correctly list "server" only once — no duplicate issue seen here.
specs/latest/swagger2-latest-server.json Adds apps/*, oauth2, healthGetAuditsDB, SES messaging, and other new endpoints; platforms arrays appear correct with no duplication.
specs/latest/swagger2-latest-console.json Adds apps/* and related endpoints; platforms arrays are consistent and correctly formed.

Reviews (4): Last reviewed commit: "chore: update API specs and SDK examples" | Re-trigger Greptile

Comment thread specs/latest/open-api3-latest-console.json
Comment thread specs/latest/open-api3-latest-server.json
Comment thread specs/latest/open-api3-latest-console.json
@appwrite-specs appwrite-specs Bot force-pushed the feat-latest-specs branch 2 times, most recently from ed6f02e to dfa4f2c Compare June 4, 2026 08:50
@appwrite-specs appwrite-specs Bot force-pushed the feat-latest-specs branch from dfa4f2c to c7a37ba Compare June 9, 2026 05:19
@ChiragAgg5k ChiragAgg5k merged commit b3ae6f2 into main Jun 9, 2026
2 of 3 checks passed
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