Struggling to migrate from HTTP to fetch in Meteor for Mailgun API integration

Other Questions Mailgun
1

Hey folks, I’m having a tough time switching from the old HTTP package to fetch in my Meteor app. I’ve been using HTTP to send emails via Mailgun for ages, but now that it’s deprecated, I’m trying to use fetch instead.

Here’s what I’ve got so far:

const sendEmail = async (params) => {
  const mailgunUrl = process.env.MAILGUN_ENDPOINT + '/messages';
  const authToken = Buffer.from('api:' + process.env.MAILGUN_KEY).toString('base64');

  try {
    const response = await fetch(mailgunUrl, {
      method: 'POST',
      headers: {
        'Authorization': 'Basic ' + authToken,
        'Content-Type': 'application/json'
      },
      body: JSON.stringify(params)
    });
    return response;
  } catch (error) {
    console.error('Email send failed:', error);
  }
}

But it’s not working. I’m getting a 400 Bad Request error. The weird thing is, the old HTTP version still works fine with the same params. Any ideas what I’m doing wrong here? Do I need to format the data differently for fetch?

2

I encountered a similar challenge when migrating from HTTP to fetch in my Meteor app. One crucial aspect you might be overlooking is error handling. With fetch, you need to manually check the response status and parse the JSON.

Here’s a refined version of your code that addresses this:

const sendEmail = async (params) => {
  const mailgunUrl = process.env.MAILGUN_ENDPOINT + '/messages';
  const authToken = Buffer.from('api:' + process.env.MAILGUN_KEY).toString('base64');

  try {
    const response = await fetch(mailgunUrl, {
      method: 'POST',
      headers: {
        'Authorization': 'Basic ' + authToken,
        'Content-Type': 'application/x-www-form-urlencoded'
      },
      body: new URLSearchParams(params)
    });

    if (!response.ok) {
      throw new Error(`HTTP error! status: ${response.status}`);
    }

    const result = await response.json();
    return result;
  } catch (error) {
    console.error('Email send failed:', error);
    throw error;
  }
}

This approach ensures you’re sending form-encoded data and properly handling responses. It’s been reliable in my projects, so give it a try and see if it resolves your issues.

3

hey there, i ran into this too. emma’s right about the form data, but i found another trick. try using the ‘node-fetch’ package instead of the built-in fetch. it handles things a bit differently and might solve ur problem without changing too much code. worth a shot!

4

I’ve recently tackled a similar migration in my Meteor project. The issue you’re facing likely stems from how fetch handles form data compared to HTTP. With Mailgun’s API, you need to send the data as form-encoded, not JSON.

Try modifying your code like this:

const sendEmail = async (params) => {
  const mailgunUrl = process.env.MAILGUN_ENDPOINT + '/messages';
  const authToken = Buffer.from('api:' + process.env.MAILGUN_KEY).toString('base64');

  const formData = new URLSearchParams();
  for (const key in params) {
    formData.append(key, params[key]);
  }

  try {
    const response = await fetch(mailgunUrl, {
      method: 'POST',
      headers: {
        'Authorization': 'Basic ' + authToken,
        'Content-Type': 'application/x-www-form-urlencoded'
      },
      body: formData
    });
    return response;
  } catch (error) {
    console.error('Email send failed:', error);
  }
}

This should resolve the 400 error. Remember to handle the response appropriately, as fetch doesn’t throw on HTTP error statuses like the old HTTP package did.