Integrations

An API key — ideally sending_access, restricted to the one domain this project sends from — or, for an integration, a registered OAuth client.

In the project's settings, under environment variables, add RASKET_API_KEY as a sensitive variable for the environments that send. Redeploy: variables are read when a deployment is built.

export async function sendEmail(message) {
  const response = await fetch("https://api.rasket.com/emails", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.RASKET_API_KEY}`,
      "User-Agent": "acme-billing/1.0",
      "Content-Type": "application/json",
    },
    body: JSON.stringify(message),
  });
  return response.json();
}

Send the User-Agent yourself — a request with no User-Agent is refused.

Coming soon: the rasket package is not published yet.

As for Vercel: a narrowly scoped API key, or a registered OAuth client.

In the site's configuration, under environment variables, add RASKET_API_KEY and mark it secret. Scope it to Functions so it never reaches a build log or the client bundle, then trigger a new deploy.

In a Netlify Function, process.env.RASKET_API_KEY holds the key, and the code above works unchanged.

As above: a narrowly scoped API key, or a registered OAuth client.

npx wrangler secret put RASKET_API_KEY

On Pages, add it as an encrypted environment variable in the project's settings instead.

A Worker reads secrets from env, not process.env. Plain fetch is the simplest client there — send the User-Agent yourself:

export default {
  async fetch(request, env) {
    const response = await fetch("https://api.rasket.com/emails", {
      method: "POST",
      headers: {
        Authorization: `Bearer ${env.RASKET_API_KEY}`,
        "User-Agent": "acme-billing/1.0",
        "Content-Type": "application/json",
      },
      body: JSON.stringify(message),
    });
    // …
  },
};