How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Supabase Functions API

Deploy and manage Edge Functions for serverless compute at the edge.

Supabase Functions API is one of 21 APIs that Supabase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Functions. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.supabase.com/v1.

5 operations 2 paths 3 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://api.supabase.com/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Supabase Functions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Personal access token or OAuth2 token for authentication. Generate tokens from the Supabase Dashboard under Account Access Tokens.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Functions 5

Deploy and manage Edge Functions for serverless compute at the edge.

GET
/projects/{ref}/functions
List Edge Functions
listFunctions 1 param → 200401404
POST
/projects/{ref}/functions
Create an Edge Function
createFunction 1 param body → 201400401
GET
/projects/{ref}/functions/{function_slug}
Get an Edge Function
getFunction 2 params → 200401404
PATCH
/projects/{ref}/functions/{function_slug}
Update an Edge Function
updateFunction 2 params body → 200401404
DELETE
/projects/{ref}/functions/{function_slug}
Delete an Edge Function
deleteFunction 2 params → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are EdgeFunction (8 properties), CreateFunctionRequest (4 properties), UpdateFunctionRequest (2 properties). Each schema is shown below with its type and property counts.

EdgeFunction
object
8 properties
CreateFunctionRequest
object
4 properties 3 required
UpdateFunctionRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

supabase-functions-api-openapi.yml Raw ↑

Other APIs Supabase publishes across the network.

Supabase Realtime API
Supabase Admin API
Supabase Authentication API
Supabase Buckets API
Supabase Configuration API
Supabase Database API
Supabase Domains API
Supabase Invocation API
Supabase MFA API
Supabase Network API
Supabase OAuth API
Supabase Objects API
Where this information came from

This is an independent, third-party profile of Supabase Functions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.