Secure your Supabase functions with Unkey

Supabase offers edge functions built upon Deno. They have a variety of uses for applications like OpenAI or working with their storage product. In this post, we will show you how to use Unkey to secure your function in just a few lines of code.

What is Unkey?

Unkey is an open source API management platform that helps developers secure, manage, and scale their APIs. Unkey has built-in features that can make it easier than ever to provide an API to your end users, including:

• Per key rate limiting
• Limited usage keys
• Time-based keys
• Per key analytics

Prerequisites

1. Create a Supabase account
2. Create a Unkey account and follow our Quickstart guide. So you have an API key to verify.
3. Setup Supabase CLI for local development.

Create our project

Create a project folder

First, we need to create a folder. Let's call that unkey-supabase. This will be where our supabase functions exist going forward.

1mkdir unkey-supabase && cd unkey-supabase

Start Supabase services

Now, we have a folder for our project. We can initialize and start Supabase for local development.

1supabase init

Make sure Docker is running. The start command uses Docker to start the Supabase services. This command may take a while to run if this is the first time using the CLI.

1supabase start

Create a Supabase function

Now that Supabase is setup, we can create a Supabase function. This function will be where we secure it using Unkey.

1supabase functions new hello-world

This command creates a function stub in your Supabase folder at ./functions/hello-world/index.ts. This stub will have a function that returns the name passed in as data for the request.

1import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
2
3console.log("Hello from Functions!");
4
5serve(async (req) => {
6  const { name } = await req.json();
7  const data = {
8    message: `Hello ${name}!`,
9  };
10
11  return new Response(JSON.stringify(data), {
12    headers: { "Content-Type": "application/json" },
13  });
14});

Test your Supabase function

Before making any changes, let's ensure your Supabase function runs. Inside the function, you should see a cURL command similar to the following:

1curl -i --location --request POST 'http://localhost:54321/functions/v1/' \
2--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0' \
3--header 'Content-Type: application/json' \
4--data '{"name":"hello-world"}'

After invoking your Edge Function, you should see the response { "message":"Hello Functions!" }.

Add Unkey to secure our Supabase function

Add verifyKey to our function

Now that we have a function, we must add Unkey to secure the endpoint. Supabase uses Deno, so instead of installing our npm package, we will use ESM CDN to provide the verifyKey function we need.

1import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
2import { verifyKey } from "https://esm.sh/@unkey/api";

What does verifyKey do?

Unkey's verifykey lets you verify a key from your end users. We will return a result and you can decide whether to give the user access to a resource or not based upon that result. For example, a response could be:

1{
2  "result": {
3    "valid": true,
4    "ownerId": "james",
5    "meta": {
6      "hello": "world"
7    }
8  }
9}

Updating our Supabase function

First, let's remove the boilerplate code from the function so we can work on adding Unkey.

1import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
2import { verifyKey } from "https://esm.sh/@unkey/api";
3
4serve(async (req) => {});

Next, we will wrap the serve function inside a try-catch. Just in case something goes wrong, we can handle that.

1import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
2import { verifyKey } from "https://esm.sh/@unkey/api";
3
4serve(async (req) => {
5  try {
6    // handle our functions here.
7  } catch (error) {
8    // return a 500 error if there is an error with a message.
9    return new Response(JSON.stringify({ error: error.message }), {
10      status: 500,
11    });
12  }
13});

Check headers for API Key

Inside our try, we can look for a header containing the user's API Key. In this example we will use x-unkey-api-key but you could call the header whatever you want. If there is no header will immediately return 401.

1import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
2import { verifyKey } from "https://esm.sh/@unkey/api";
3
4serve(async (req) => {
5  try {
6    const token = req.headers.get("x-unkey-api-key");
7    if (!token) {
8      return new Response("Unauthorized", { status: 401 });
9    }
10  } catch (error) {
11    // return a 500 error if there is an error with a message.
12    return new Response(JSON.stringify({ error: error.message }), {
13      status: 500,
14    });
15  }
16});

Verifying the key

The verifyKey function returns a result and error, making the logic easy to handle. Below is a simplified example of the verification flow.

1const { result, error } = await verifyKey("key_123");
2if (error) {
3  // handle potential network or bad request error
4  // a link to our docs will be in the `error.docs` field
5  console.error(error.message);
6  return;
7}
8if (!result.valid) {
9  // do not grant access
10  return;
11}
12// process request
13console.log(result);

Now you have a basic understanding of verification, let's add this to our Supabase function.

1serve(async (req) => {
2  try {
3    const token = req.headers.get("x-unkey-api-key");
4    if (!token) {
5      return new Response("No API Key provided", { status: 401 });
6    }
7    const { result, error } = await verifyKey(token);
8    if (error) {
9      // handle potential network or bad request error
10      // a link to our docs will be in the `error.docs` field
11      console.error(error.message);
12      return new Response(JSON.stringify({ error: error.message }), {
13        status: 400,
14      });
15    }
16    if (!result.valid) {
17      // do not grant access
18      return new Response(JSON.stringify({ error: "API Key is not valid for this request" }), {
19        status: 401,
20      });
21    }
22    return new Response(JSON.stringify({ result }), { status: 200 });
23  }

Testing our Supabase function

We can send a curl request to our endpoint to test this functionality. Below is an example of the curl to send. Remember, we now need to include our API key.

1curl -XPOST -H 'Authorization: Bearer <SUPBASE_BEARER_TOKEN>' \
2-H 'x-unkey-api-key: <UNKEY_API_KEY>' \
3-H "Content-type: application/json" 'http://localhost:54321/functions/v1/hello-world'

Adding CORS for added security

Adding CORS allows us to call our function from the frontend and decide what headers can be passed to our function. Inside your functions folder, add a file called cors.ts. Inside this cors file, we will tell the Supabase function which headers and origins are allowed.

1export const corsHeaders = {
2  "Access-Control-Allow-Origin": "*",
3  "Access-Control-Allow-Headers":
4    "authorization, x-client-info, x-unkey-api-key, content-type",
5};

Conclusion

In this post, we have covered how to use Unkey with Supabase functions to secure them. You can check out the code for this project in our Examples folder