1. GET Annotations:
2. • New Query Parameter:
     • fileId: A required parameter that specifies the file for which annotations are to be fetched.
   • Response Update:
     • 200 Success: Includes more structured data
     • 404 Error: A new error description has been added, indicating issues while fetching annotations.
3. POST Annotations:
   • Updated Payload Structure:
     • _id: Now described as the ID of the annotation to update.
     • descriptor: Updated as an optional array of annotation descriptors.
     • pageUrl: Now includes a description specifying the URL of the page associated with the annotation.
     • fileId: Added description to clarify it’s the ID of the file related to the annotation.
     • type: Describes the type of annotation, such as signature, text, or image.
     • Additional Fields:
       • devicePixelRatio, imageUrl, text, richText, userId, annotationD, and scale now all have corresponding descriptions for clarity.
     • New Fields Added:
       • strokeWidth: Specifies the stroke width of the annotation.
       • annotationColor: Describes the color of the annotation.
       • isTask: Indicates whether the annotation is associated with a task.
       • commentText: Captures comment text for the annotation.
   • Response Update:
     • 200 Success: Clarifies the response message for a successful annotation creation.
4. DELETE Annotations:
   • Removed: The organizationId parameter was removed from the path, as it is no longer required.
   • Response Updates:
     • 200 Success: Returns a message confirming successful annotation deletion.
     • 404 Error: Added error response for when the annotation cannot be found or deleted.
     • 401 Unauthorized: New error response indicating unauthorized access or errors during the deletion process.

1.   GET Tasks:

• Response Schema Update:
  • New Property Added:
    • id: A new optional parameter has been added to retrieve a specific task by its ID.
    • projectid: The description for this property has been updated to specify that it retrieves all tasks within a project.
  • Response Status Code Changes:
    • 400 Error: A new status code has been introduced to indicate that either the project or file must be defined in the request.

1. POST File:
   • Summary and Description Updates:
     • A detailed request body schema has been added, including:
       • projectid: ID of the project to which the file/URL will be uploaded.
       • name: The name of the file or URL.
       • description: An optional description for the file or URL.
       • url: The URL to be uploaded (if applicable).
       • file: The actual file to be uploaded (if applicable).
       • phaseId: The optional phase ID to assign the file within the project.
   • Responses:
     • 201 Success: A new success response schema details the uploaded file, including fields for _id, name, and reviewurl.
     • 400 Error: Expanded to specify missing or invalid data and includes a structured error response.
     • 403 Error: Now includes a structured error response detailing storage limits and permissions.
     • 404 Error: Now includes a structured error response for when the project is not found.
     • 507 Error: Added to indicate storage limits reached, with a structured error response.
2. PUT File:
   • Summary and Description Updates:
     • Updated to specify that this endpoint updates a file’s data, with a new request body schema that includes fields for name, description, url, annotateDisable, status, and userId.
3. DELETE File:
   • Description Update: Specifies that this endpoint deletes a file permanently.

1. GET Comments:
   • Summary and Description Updates:
     • The summary now indicates that this endpoint retrieves a list of comments related to a specific project or file.
     • A detailed description has been added to clarify the functionality of the endpoint.
   • Request Body Enhancements:
     • New Fields Added:
       • id: The ID of the comment or task to retrieve.
       • fileid: The ID of the file to filter the comments.
       • replies: A boolean that, when set, retrieves replies for the comments.
       • plainText: A boolean to return the comment text without HTML tags if set to true.
     • Example Values:
       • Each new field includes example values for better understanding.
2. Responses:
   • 200 Success: Confirmed that comments are retrieved successfully.
   • 404 Error: Description updated to specify that no comment was found.
   • 500 Error: Added to indicate an internal server error.
3. POST Comments:
   • The request body and related parameters have been confirmed as unchanged from the previous version.

POST Responses

1. Request Body Enhancements:
   • Required Fields Updated:
     • The route field has been added as a required parameter in addition to the existing taskid and reply.
   • New Properties Added:
     • user_id:
       • Type: string
       • Description: The ID of the user making the reply (optional).
     • reply_id:
       • Type: string
       • Description: The ID of the reply being edited (optional).