Node.js开发Alexa函数：API调用报错问题求助

Hey there! Since your skill works perfectly with hardcoded plain text but throws errors when making API calls, let’s break down the most common culprits and fixes:

1. You’re not handling asynchronous API calls correctly #

Node.js API calls (using tools like axios, fetch, or the native http module) are asynchronous by default. If you kick off an API call but immediately send a response back to Alexa without waiting for the API to return data, your skill will finish execution before the API call completes—leading to missing data or unhandled errors.

Example of incorrect code: #

// Fails because the response is sent before the API call finishes
else {
  http.get('https://your-api-endpoint.com/data', (res) => {
    // This logic runs later, after the response is already sent
  });
  // Returns incomplete response to Alexa right away
  return handlerInput.responseBuilder.speak('Loading...').getResponse();
}

Fix with async/await: #

First, mark your handler function as async, then use await to wait for the API call to resolve. Wrap everything in a try/catch block to handle failures gracefully:

const axios = require('axios'); // Simplifies async/await handling

exports.handler = async (handlerInput) => {
  // Your existing skill logic here...

  else {
    try {
      // Wait for the API call to complete
      const apiResponse = await axios.get('https://your-api-endpoint.com/data', {
        // Add required headers/params (e.g., API keys) here
        headers: {
          'Authorization': 'Bearer YOUR_API_KEY',
          'Content-Type': 'application/json'
        }
      });

      // Extract the data you need from the API response
      const responseText = apiResponse.data;

      // Build and return the Alexa response with the API data
      return handlerInput.responseBuilder
        .speak(`Here's the info you asked for: ${responseText}`)
        .getResponse();
    } catch (error) {
      // Log the error for debugging (check CloudWatch logs!)
      console.error('API call failed:', error);
      // Return a user-friendly error message
      return handlerInput.responseBuilder
        .speak('Sorry, I couldn\'t retrieve that information right now. Please try again later.')
        .getResponse();
    }
  }
};

2. Missing required API authentication or headers #

Many APIs require API keys, tokens, or specific request headers to return valid data. If you’re not including these, the API might return a 4xx (Unauthorized/Forbidden) or 5xx error, which breaks your skill.

Fix: #

Double-check the API’s documentation for required headers (like Authorization) or query parameters, then add them to your API call as shown in the example above.

3. No error handling for failed API calls #

If the API times out, returns an unexpected response format, or goes down, your skill will throw an unhandled exception without proper error catching. This causes Alexa to return a generic "something went wrong" message.

Fix: #

Always wrap your API calls in a try/catch block (as shown earlier) to log the error and return a user-friendly fallback message.

Pro Tip: Check Lambda CloudWatch Logs #

The fastest way to pinpoint the exact error is to look at your Lambda function’s CloudWatch logs. You’ll see detailed error messages (like network timeouts, invalid API responses, or syntax errors) that will tell you exactly what’s breaking.

内容的提问来源于stack exchange，提问作者user3872094