AI Prompts for Diagnose API Authentication Failure

Please quote the output of the authentication function from the last run for the API integration issue titled "bolt-api-integration-not-working." Specifically, provide the actual response received from the API during the authentication attempt and compare it with the expected response format. Highlight any discrepancies or issues that may indicate why the integration is not functioning as intended.

Please analyze the following API response error message: [ERROR MESSAGE]. Identify the potential reasons for the authentication failure and suggest specific steps to resolve the issue. Additionally, provide recommendations for preventing similar errors in future API integrations.

Please explain your understanding of the API call and authentication process for the [API NAME]. Include details on the required parameters, headers, and any specific authentication methods that should be used. Additionally, outline any common issues that could arise during the API call and how they might be resolved.

Please compare the expected behavior of the API authentication process with the actual behavior observed in the case of the bolt-api-integration-not-working issue. List the elements that should be included in a successful authentication response, such as status codes, response body, and headers, and then detail what was actually received in each case. Format your response in a table for clarity, with separate columns for 'Expected Response' and 'Actual Response'.

Please identify the specific authentication rule or constraint that was violated during the authentication process for the bolt API integration. Include the exact clause from the API documentation that outlines the expected authentication method. Additionally, provide a brief explanation of how this violation impacts the overall integration and any potential steps to resolve the issue.

Please review the API call in [FILE] at line [LINE] to identify the incorrect parameters being used. The original parameters are: [PASTE]. Compare these with the correct parameters from the API documentation: [PASTE]. Provide a detailed diff of the changes needed before applying the updates, highlighting what needs to be corrected.

Rewrite the authentication function located in [FILE] at line [LINE]. Include the required headers and body as specified in the API documentation. Make sure the function adheres to the expected format and provide a brief explanation of any changes made to improve clarity and functionality.

Identify the incorrect API URL in [FILE] at line [LINE]. The original URL is [PASTE], and it needs to be changed to the correct endpoint: [PASTE]. Ensure that no other part of the function is modified during this update. Provide a brief summary of the changes made and any potential impact on the functionality.

Please review the response handling code in [FILE] at line [LINE]. Ensure that it validates the response structure against the API documentation. Provide a detailed explanation of the changes made, including the rationale for each modification and how it improves the response format validation.

Please verify the API client dependency in [FILE]. Check if it is correctly installed and determine if it is missing or outdated. If it is not installed or needs an update, provide the correct installation command along with the recommended version to ensure proper functionality.

Please run the authentication function for the [API NAME] integration again and confirm whether it returns a successful response. Provide the exact output received and compare it against the expected success response, detailing any discrepancies or issues encountered. Additionally, summarize the steps taken during the test to ensure clarity in the verification process.

Please provide a detailed comparison of the changes made to the authentication function in the context of the bolt API integration. Include a side-by-side view of the previous and updated code, highlighting all modifications. Additionally, explain how each change aligns with the API requirements and any potential impact these changes may have on the overall functionality.

Replay the original authentication call that failed for the bolt API integration. Confirm whether the call now succeeds and provide the output received. Additionally, include any error messages that were generated during the attempt. Format the response clearly, highlighting the success status and any relevant details for troubleshooting.

Test the authentication process for edge cases by simulating scenarios with invalid credentials. Ensure that the system handles these errors gracefully and does not crash. Provide a detailed output of the error messages returned, including any relevant status codes and descriptions, formatted in a clear and organized manner.

Please verify the API response state in [FILE] at line [LINE] to confirm that it indicates successful authentication. Provide the output you observe and ensure it matches the expected structure, detailing any discrepancies if they exist. Additionally, summarize the steps taken to reach this conclusion.

Please provide the exact session-opening constraint for the project titled [PROJECT NAME]. Use the following format: 'Before any API call: verify authentication parameters are correct and the API endpoint is reachable. If authentication fails, log the error and halt further execution.' Ensure the output is formatted as a single line of paste-ready text.

Please create a conversation-starter template for checking the API response structure for [API NAME]. The template should include a checklist that verifies the presence of [EXPECTED FIELDS] in the response. If the expected fields are not present, the template should specify logging an error and stopping further actions. Format the output as a structured checklist with clear instructions.

Draft a project specification message regarding API authentication error handling. The message should state that all API authentication errors must be logged with specific details, including the timestamp, error message, and attempted parameters. Additionally, specify that this log must be reviewed prior to deployment. Format the message clearly and concisely for easy understanding.

Please create a naming convention guideline for API keys. The guideline should state that all API keys must be prefixed with 'API_' and emphasize the importance of storing them securely. Additionally, include a clear instruction to avoid hardcoding keys in the codebase. Format the guideline as a bullet-point list for easy reference.

Please create a self-check request for API authentication. The request should state: 'Before executing any API calls, confirm that the authentication function has been successfully executed and returned a valid token. If not, alert the user and stop execution.' Ensure the output is formatted as a code snippet that can be easily integrated into the existing API workflow.