---
title: "Invoke a function (GET)"
method: GET
path: "/functions/v1/{name}"
tags: ["Functions"]
---

# Invoke a function (GET)

`GET /functions/v1/{name}`

## Request

- Base URL: `https://api.run402.com`
- URL: `https://api.run402.com/functions/v1/{name}`
- Auth: API key in header `apikey`

Invokes a deployed function. Supports any HTTP method. Subroutes are forwarded. Requires the apikey header (anon_key or service_key); a raw request without it returns 401 Missing apikey header. Add Authorization: Bearer <access_token> for authenticated calls so the function can identify the user via getUser(req). Paid functions require Idempotency-Key and may return a pollable 202 run handle. The body reaches the function as sent, whatever its content-type (up to 1 MB); only authorization, content-type and apikey headers are forwarded (plus x-run402-user-id / x-run402-user-role when a role gate ran).

## Path parameters

- `name` string, required

## Response `200`

Function response. Schema and content type are controlled by the deployed function.

- unknown

## Other responses

- `401`: Missing or invalid authentication. Run402-originated JSON bodies use the canonical ErrorEnvelope.

---

[API](https://skmtc.dev/run402/apis/run402-api.md) · [All operations](https://skmtc.dev/run402/apis/run402-api/llms.txt) · [OpenAPI document](https://skmtc.dev/run402/apis/run402-api/revisions/893607557f50?raw)