API release notes

• Optional priority (P0 to P4) on POST /api/v1/cases/{caseUuid}/files to set the files' SLA priority instead of your workspace's default. Once Wisedocs has counted a file's pages, a file past the priority's page limit is moved to the next lower priority that fits.

October 22, 2026

• Optional case.createdBy (email) on POST /api/v1/cases to set the Wisedocs user shown as the case's "Created by". The user must be active in your workspace and, when team visibility is enabled, a member of one of case.teams; otherwise the request returns 400. It is create-only: PATCH /api/v1/cases/{caseUuid} does not accept it and responses do not return it.

• getFile moved to GET /api/v1/cases/{caseUuid}/files/{fileUuid} (scope files:read) and returns the file's status, pageCount, dates, and getUrl. GET /api/v1/files/{fileUuid} has been removed.

October 22, 2026 · Generally available

API v1 is available for production integrations. API v0 remains available and unchanged.

• OAuth scopes (cases:read, cases:write, files:read, files:write, teams:read) enforced per operation.
• GET /api/v1/teams to look up teams by name, username, or email, and case.teams on POST /api/v1/cases to assign teams when creating a case.
• GET /api/v1/cases filtering by caseUuid, internalCaseNumber, and claimNumber with limit and offset pagination.
• PATCH /api/v1/cases/{caseUuid} support for updating claimantsAddress, referringorganization, and referrercontactprofile.

• POST /api/v1/cases creates the case and its related records atomically and returns field-level validation errors in error.details.
• GET /api/v1/cases/{caseUuid} returns case, claim, claimant, claimantsAddress, referringorganization, and referrercontactprofile.
• PATCH /api/v1/cases/{caseUuid} applies updates atomically and returns the updated case.
• POST /api/v1/cases/{caseUuid}/files accepts 1 to 100 unique file names (fileNames) and returns presigned upload URLs in request order.
• File upload completion is reported with PATCH /api/v1/cases/{caseUuid}/files/{fileUuid} and {"status": "UPLOADED"}.
• Upload PUT requests to a presigned putUrl require both x-amz-server-side-encryption: AES256 and the file's Content-Type header.
• GET /api/v1/cases/{caseUuid}/doclists/{doclistUuid} has been removed from API v1 (still available in API v0).
• Missing OAuth scopes return 403 Forbidden with error.code: "insufficient_scope".

• Invalid or expired tokens return 401 Unauthorized with a WWW-Authenticate header.

October 13, 2026 · In development

API v1 is currently in development. These release notes are published for informational purposes only, and documented availability and behavior may change.

• OAuth 2.0 client credentials authentication.
• Standard Bearer token authorization for protected operations.
• Versioned case, file, file-upload, and doclist operations under /api/v1.
• Token discovery, creation, introspection, and revocation documentation.
• A version selector for switching between API v1 and the legacy API v0 reference.

• Public request fields, response fields, path parameters, and query parameters use camelCase.
• Authentication responses follow the OAuth 2.0 token response format.
• API v1 uses its own versioned paths while API v0 remains available as the legacy interface.

• API v1 remains under active development and is not yet intended for production integrations.
• Documented availability and behavior may change before the production release.