Supabase Invocation API

Invoke deployed Edge Functions via HTTP requests. Each function is accessible at its own URL path based on its slug.

Operations 2

GET /{function_slug} Invoke an Edge Function via GET #
POST /{function_slug} Invoke an Edge Function via POST #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/supabase-invocation-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

supabase-invocation-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Supabase Edge Functions Invocation API
  description: Supabase Edge Functions are globally distributed, server-side TypeScript functions powered by the Deno runtime. They are invoked via HTTP requests to a project-specific URL. Edge Functions can access the Supabase client libraries for interacting with the database, auth, and storage services. By default, they require a valid JWT in the authorization header, but this can be disabled per function. This specification documents the HTTP invocation interface for deployed Edge Functions.
  version: 1.0.0
  contact:
    name: Supabase Support
    url: https://supabase.com/support
  termsOfService: https://supabase.com/terms
servers:
- url: https://{project_ref}.supabase.co/functions/v1
  description: Supabase Project Edge Functions Server
  variables:
    project_ref:
      description: Your Supabase project reference ID
      default: your-project-ref
security:
- apiKeyAuth: []
  bearerAuth: []
tags:
- name: Invocation
  description: Invoke deployed Edge Functions via HTTP requests. Each function is accessible at its own URL path based on its slug.
paths:
  /{function_slug}:
    get:
      operationId: invokeEdgeFunctionGet
      summary: Invoke an Edge Function via GET
      description: Invokes a deployed Edge Function using an HTTP GET request. The function can read query parameters and headers from the request. Authorization is required by default unless JWT verification is disabled for the function.
      tags:
      - Invocation
      parameters:
      - $ref: '#/components/parameters/FunctionSlug'
      responses:
        '200':
          description: Function executed successfully
          content:
            application/json:
              schema:
                type: object
                description: Response from the Edge Function
            text/plain:
              schema:
                type: string
                description: Text response from the Edge Function
        '401':
          description: Unauthorized - missing or invalid JWT
        '404':
          description: Function not found
        '500':
          description: Internal function error
    post:
      operationId: invokeEdgeFunctionPost
      summary: Invoke an Edge Function via POST
      description: Invokes a deployed Edge Function using an HTTP POST request. The function can read the request body, query parameters, and headers. This is the most common invocation method for Edge Functions that process data or trigger actions.
      tags:
      - Invocation
      parameters:
      - $ref: '#/components/parameters/FunctionSlug'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              description: JSON payload to pass to the Edge Function. Structure depends on the specific function implementation.
          text/plain:
            schema:
              type: string
              description: Plain text payload
          multipart/form-data:
            schema:
              type: object
              description: Form data payload
      responses:
        '200':
          description: Function executed successfully
          content:
            application/json:
              schema:
                type: object
                description: Response from the Edge Function
            text/plain:
              schema:
                type: string
        '400':
          description: Bad request - invalid input
        '401':
          description: Unauthorized - missing or invalid JWT
        '404':
          description: Function not found
        '500':
          description: Internal function error
components:
  parameters:
    FunctionSlug:
      name: function_slug
      in: path
      required: true
      description: The URL-friendly slug of the deployed Edge Function to invoke.
      schema:
        type: string
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: apikey
      description: Supabase project anon API key. Required for all Edge Function invocations.
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT access token. Required by default unless the function has JWT verification disabled.
externalDocs:
  description: Supabase Edge Functions Documentation
  url: https://supabase.com/docs/guides/functions