Wasp•3w ago

call api from action

Can you call an api from an action?

4 Replies

Hi @cmilazzo. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Yes, you can call an API from a Wasp action. Actions in Wasp run on the server side, which means they have full access to make HTTP requests to external APIs. When implementing an action, you can use standard Node.js HTTP clients like fetch, axios, or any other HTTP client library to make API calls to external services. Here's a pattern you might follow when implementing an action that calls an external API:

export const myAction = async (args, context) => {
  // Validate user is authenticated if needed
  if (!context.user) {
    throw new HttpError(401);
  }
  
  // Call external API
  const response = await fetch('<https://external-api.com/endpoint',> {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify(args),
  });
  
  // Process the response
  const data = await response.json();
  
  // Do something with the data, perhaps save to database
  return data;
}

export const myAction = async (args, context) => {
  // Validate user is authenticated if needed
  if (!context.user) {
    throw new HttpError(401);
  }
  
  // Call external API
  const response = await fetch('<https://external-api.com/endpoint',> {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify(args),
  });
  
  // Process the response
  const data = await response.json();
  
  // Do something with the data, perhaps save to database
  return data;
}

This approach is useful when you need to integrate with third-party services or when you have an existing API that you want to use alongside your Wasp application. As mentioned in one of the Discord support threads, you can even use this pattern to integrate with Python applications by exposing them as APIs and then calling them from your Wasp actions Discord support thread. Remember that when calling APIs from actions, you're doing so from the server side, which means you can safely include API keys and other sensitive information that shouldn't be exposed to the client. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @cmilazzo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

cmilazzoOP•3w ago

can this be done with an internal api without making use of http? @kapa.ai can this be done with an internal api without making use of http?

kapa.ai•3w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Yes, you can call another action or query from within an action without making HTTP requests. Wasp allows you to directly import and call other operations from your server-side code. There are two main approaches to calling one action from another: 1. Import from wasp/server/operations You can import the action you want to call from wasp/server/operations:

import { createFile } from 'wasp/server/operations'

export const myAction = async (args, context) => {
  // Your action logic
  
  // Call another action
  const result = await createFile(fileArgs, context)
  
  return result
}

import { createFile } from 'wasp/server/operations'

export const myAction = async (args, context) => {
  // Your action logic
  
  // Call another action
  const result = await createFile(fileArgs, context)
  
  return result
}

As mentioned in the Discord support thread, the type support for this approach is limited, but it works functionally Discord support thread. 2. Extract shared logic into helper functions Another approach is to extract the shared business logic into separate helper functions that can be called from multiple actions:

export const businessLogic = async (...) => {
  // Shared logic here
}

export const apiFunction = async (...) => {
  // API-specific logic
  return businessLogic(...)
}

export const actionFunction = async (...) => {
  // Action-specific logic
  return businessLogic(...)
}

export const businessLogic = async (...) => {
  // Shared logic here
}

export const apiFunction = async (...) => {
  // API-specific logic
  return businessLogic(...)
}

export const actionFunction = async (...) => {
  // Action-specific logic
  return businessLogic(...)
}

This pattern was suggested in a Discord thread as a way to avoid duplicating logic between API endpoints and actions Discord support thread. By using these approaches, you can maintain a clean separation of concerns while reusing logic across different parts of your server-side code without making HTTP requests. Remember that when calling one action from another, you need to properly handle the context object to maintain authentication and other contextual information. Let me know if you need more specific examples for your use case! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @cmilazzo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

cmilazzoOP•3w ago

Thank you. That helped.

Gaming

Programming

call api from action

Did you find this page helpful?