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 Invocation API

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

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

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

This API exposes 2 operations across 1 path. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://{project_ref}.supabase.co/functions/v1.

2 operations 1 paths 0 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://{project_ref}.supabase.co/functions/v1
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Supabase Invocation API declares 2 security schemes for authenticating requests. An API key is passed in the header as apikey (apiKeyAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • apiKeyAuth — Supabase project anon API key. Required for all Edge Function invocations.
  • bearerAuth — JWT access token. Required by default unless the function has JWT verification disabled.

Paths & Operations 2

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

Invocation 2

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

GET
/{function_slug}
Invoke an Edge Function via GET
invokeEdgeFunctionGet 1 param → 200401404500
POST
/{function_slug}
Invoke an Edge Function via POST
invokeEdgeFunctionPost 1 param body → 200400401404500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

supabase-invocation-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 Functions 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 Invocation 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.