Skip to content
deploybase

Add or remove a team from the HTTP functions closed beta

POST
/api/v1/admin/teams/{id}/functions-beta
 
curl --request POST \
  --url https://api.deploybase.eu/api/v1/api/v1/admin/teams/example/functions-beta \
  --header 'Authorization: <Authorization>' \
  --header 'Content-Type: application/json' \
  --data '{ "enabled": true }'

Grants or revokes one team’s place in the HTTP functions closed beta (DEP-375/DEP-378). The flag is a GRANT, not an allowlist entry: while the beta is closed it overrides the plan gate entirely, so an enrolled team serves HTTP functions at the beta profile’s sizing even on a plan that excludes them. A false->true flip emails the team (the applicant and the team’s notification address); enabling an already-enrolled team is a no-op and sends nothing. Revoking leaves the granted-at stamp alone. Once FN_HTTP_BETA_OPEN is true the beta is open to every eligible plan and this flag no longer has any effect.

Authorizations

Section titled “ Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “ Path Parameters ”
id
required
string

Team ID (UUID)

Request Body

Section titled “ Request Body ”

Beta enrolment flag

Media type application/json
object
enabled
required
boolean
Example generated 
{
  "enabled": true
}

Responses

Section titled “ Responses ”

200

Section titled “ 200 ”

OK

Media type application/json
object
data
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "data": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}

400

Section titled “ 400 ”

Bad Request

Media type application/json
object
code
string
details
error
string
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "code": "example",
  "details": "example",
  "error": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}

401

Section titled “ 401 ”

Unauthorized

Media type application/json
object
code
string
details
error
string
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "code": "example",
  "details": "example",
  "error": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}

403

Section titled “ 403 ”

Forbidden

Media type application/json
object
code
string
details
error
string
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "code": "example",
  "details": "example",
  "error": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}

404

Section titled “ 404 ”

Not Found

Media type application/json
object
code
string
details
error
string
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "code": "example",
  "details": "example",
  "error": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}

500

Section titled “ 500 ”

Internal Server Error

Media type application/json
object
code
string
details
error
string
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "code": "example",
  "details": "example",
  "error": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}

503

Section titled “ 503 ”

Service Unavailable

Media type application/json
object
code
string
details
error
string
meta
object
request_id
string
timestamp
string
trace_id
string
Example generated 
{
  "code": "example",
  "details": "example",
  "error": "example",
  "meta": {
    "request_id": "example",
    "timestamp": "example",
    "trace_id": "example"
  }
}