# Update Product Answer ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /v1/products/{product_id}/questions/{question_id}/answers/{answer_id}: patch: summary: Update Product Answer deprecated: false description: |- Update details of a specific answer to a question. `products.read_write` - Products Read & Write operationId: patch-products-product_id-questions-question_id-answers-answer_id tags: - Default module/Apps/Merchant APIs/Products/Product Questions & Answers - Questions & Answers parameters: - name: product_id in: path description: '' required: true example: 399e381e-7c58-4148-aa26-7f959f4bf22b schema: type: string - name: question_id in: path description: '' required: true example: 1ef1cc35-79e7-40b7-a9b2-989fd5895859 schema: type: string - name: answer_id in: path description: '' required: true example: a4f54aa9-7d50-4c49-a114-709643d1d175 schema: type: string - name: Access-Token in: header description: >- An Access Token is a unique string that represents the authorization granted to a client (Partner application) by a user (Merchant or Store Manager) to access their protected resources. It is part of the OAuth 2.0 standard and is used to authenticate API requests on behalf of the user. Access Tokens have a limited lifespan and must be used within their validity period. Once expired, a new Access Token can be obtained using a Refresh Token. Access Tokens should be treated as sensitive information and must be kept secure to prevent unauthorized access to the user's data. If you do not have an `Access-Token`, but have the older alternative instead, i.e., the `X-Manager-Token`, then see the instructions [here](docs/Migrate-to-OAUTH-2.0.md) on how to obtain the `Access-Token`. required: true example: '{{Access-Token}}' schema: type: string - name: Store-Id in: header description: '' required: true example: '{{StoreId}}' schema: type: number examples: - 37213 - name: Role in: header description: Role of the user. required: true example: Manager schema: type: string enum: - Manager - Customer examples: - Manager - name: Accept-Language in: header description: '' required: false example: en schema: type: string enum: - ar - en x-apidog-enum: - value: ar name: '' description: '' - value: en name: '' description: '' requestBody: content: application/json: schema: type: object x-examples: Example 1: answer: New answer properties: answer: type: string description: The content of the answer. examples: - '"New answer"' x-apidog-orders: - answer x-apidog-ignore-properties: [] example: answer: '"New answer"' responses: '200': description: '' content: application/json: schema: type: object x-examples: Example 1: id: b5e1cdea-1e9f-4bcd-ae33-21c70b5d715e question_id: cf2fc926-d179-4330-8fff-330853416aea answer: Updated answer content. created_at: '2024-07-12T07:00:00.000000Z' properties: id: type: string description: The unique identifier of the answer. examples: - '"b5e1cdea-1e9f-4bcd-ae33-21c70b5d715e"' question_id: type: string description: The unique identifier of the question. examples: - '"cf2fc926-d179-4330-8fff-330853416aea"' answer: type: string description: The updated content of the answer. examples: - '"Updated answer content."' created_at: type: string description: The timestamp of when the answer was created. examples: - '"2024-07-12T07:00:00.000000Z"' x-apidog-orders: - id - question_id - answer - created_at x-apidog-ignore-properties: [] headers: {} x-apidog-name: Answer updated successfully. '401': description: '' content: application/json: schema: type: object description: >- Response returned when the request cannot be authenticated because the required credentials are missing, invalid, or expired. properties: status: type: string description: Indicates the overall status of the API response. examples: - error message: type: object description: >- Contains structured details explaining why the request could not be authenticated. properties: type: type: string description: Indicates the category of the response message. examples: - error code: type: string description: >- A machine-readable code identifying the authentication error. Returns null when no specific code is available. examples: - UNAUTHORIZED nullable: true name: type: string description: >- A short, human-readable title describing the authentication error. Returns null when no title is available. examples: - Unauthorized nullable: true description: type: string description: >- A human-readable explanation of why the request could not be authenticated. Returns null when no detailed explanation is available. examples: - >- Authentication credentials are missing, invalid, or expired. nullable: true required: - type - code - name - description x-apidog-orders: - type - code - name - description x-apidog-ignore-properties: [] required: - status - message x-apidog-orders: - status - message examples: - status: error message: type: error code: UNAUTHORIZED name: Unauthorized description: >- Authentication credentials are missing, invalid, or expired. x-apidog-ignore-properties: [] examples: '1': summary: Example 1 value: status: error message: type: error code: ERROR_SESSION_MISSING name: Sorry description: Please login first. '2': summary: Example 2 value: status: error message: type: error code: ERROR_SESSION_INVALID name: Sorry description: Login session expired. Please login again. '3': summary: Example 3 value: status: error message: type: error code: ERROR_SESSION_INVALID name: Sorry description: Invalid authentication headers: {} x-apidog-name: Unauthorized '500': description: '' content: application/json: schema: type: object properties: status: type: string description: Status of the error. message: $ref: '#/components/schemas/ResponseEnvelopMessage' required: - status - message x-apidog-orders: - status - message x-apidog-ignore-properties: [] example: status: error message: type: error code: MSG_HIDDEN name: Error description: Internal Server Error headers: {} x-apidog-name: Internal Server error security: [] x-apidog-folder: Default module/Apps/Merchant APIs/Products/Product Questions & Answers x-apidog-status: released x-run-in-apidog: https://app.apidog.com/web/project/613905/apis/api-9148664-run components: schemas: ResponseEnvelopMessage: type: object properties: type: type: string description: Type of response message returned by the API. examples: - success code: type: string description: Response code returned by the API, if available. examples: - MSG_POPUP_OK nullable: true name: type: string description: Name or title of the response message, if available. examples: - Coupons nullable: true description: type: string description: Detailed description of the response message, if available. examples: - Coupons created successfully nullable: true required: - type - code - name - description description: Additional response metadata. x-apidog-orders: - type - code - name - description x-apidog-ignore-properties: [] x-apidog-folder: '' securitySchemes: {} servers: - url: https://api.zid.sa/ description: Prod Env security: [] ```