feat: API specs update for version latest

[appwrite-specs]

This PR contains API specification updates for version latest.

[greptile-apps]

Greptile Summary

This PR updates API specs across all six latest spec files to add: bigint attribute/column CRUD endpoints (databases & tablesDB), a new purge boolean parameter for updateCollection/updateTable, a userType field in the audit log schema, and x as a new OAuth2 provider, alongside weight reordering throughout.

• P1: The demo path for every new bigint endpoint uses big-int (e.g. create-big-int-attribute.md) while the sibling edit GitHub URL uses bigint (e.g. create-bigint-attribute.md). All other attribute entries use matching names in both fields; one of these will 404. The mismatch appears in all four non-client spec files for both the create and update variants of the attribute and column endpoints.

Confidence Score: 4/5

Safe to merge after resolving the bigint demo path naming mismatch, which will cause broken links in SDK tooling.

One P1 finding: the demo filename uses big-int (hyphenated) while the edit URL and all sibling attribute entries use bigint (no hyphen). This mismatch affects all four non-client spec files and will result in a broken file reference in SDK generation or documentation tooling. All other changes (weight reordering, new purge param, userType audit field, x OAuth provider) look correct.

specs/latest/open-api3-latest-server.json, specs/latest/open-api3-latest-console.json, specs/latest/swagger2-latest-server.json, specs/latest/swagger2-latest-console.json — specifically the demo field values for the bigint attribute and column endpoints

Vulnerabilities

No security concerns identified.

Important Files Changed

Filename	Overview
specs/latest/open-api3-latest-server.json	Adds bigint attribute/column endpoints, new project management endpoints, purge param, userType audit field, "x" OAuth provider — demo path for bigint uses "big-int" while edit URL uses "bigint"
specs/latest/open-api3-latest-console.json	Same bigint/column endpoints and new organization/migration endpoints; demo path inconsistency (big-int vs bigint) present
specs/latest/swagger2-latest-server.json	Swagger2 counterpart of server spec; same bigint demo path inconsistency present
specs/latest/swagger2-latest-console.json	Swagger2 counterpart of console spec; same bigint demo path inconsistency present
specs/latest/open-api3-latest-client.json	Client spec; adds "x" as a new OAuth2 provider and weight reordering — no issues found
specs/latest/swagger2-latest-client.json	Swagger2 client spec; minor weight reordering — no issues found

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

[greptile-apps]

attributeBigint.default uses int32 format instead of int64

The default field in the attributeBigint response schema declares "format": "int32", while the sibling min and max fields correctly use "format": "int64". A bigint default value must support the full 64-bit range, so SDKs/tools that respect the format hint will truncate any default exceeding 2,147,483,647 when deserializing the response. The same issue exists in the columnBigint schema (line 54761) and is replicated across all six spec files.

Suggested change

	"default": {
	"type": "integer",
	"description": "Default value for attribute when not provided. Cannot be set when attribute is required.",
	"x-example": 10,
	"format": "int32",
	"nullable": true
	}
	"default": {
	"type": "integer",
	"description": "Default value for attribute when not provided. Cannot be set when attribute is required.",
	"x-example": 10,
	"format": "int64",
	"nullable": true
	}

[greptile-apps]

Tip:

Greploop — Automatically fix all review issues by running /greploops in Claude Code. It iterates: fix, push, re-review, repeat until 5/5 confidence.

Use the Greptile plugin for Claude Code to query reviews, search comments, and manage custom context directly from your terminal.