Referencia de la API

Todos los endpoints de la API REST pública, generados a partir de los mismos esquemas que valida el servidor. Autentícate con una clave de API desde tus ajustes o con un token de acceso OAuth.

Las peticiones autenticadas a la API están limitadas a 300 peticiones por cada 60 segundos y credencial. Cada respuesta incluye RateLimit-Limit, RateLimit-Remaining y RateLimit-Reset (segundos hasta que se reinicia la ventana); una respuesta 429 incluye además retry-after.

URL basehttps://nextjs-saas-template.lubomirgeorgiev.com
v1.0.0
Abrir el documento OpenAPICómo funciona la autenticaciónCódigos de errorConectar un agente de IA por MCP
19 de 19 endpoints

Account

GET/api/v1/me

Get the authenticated account

Returns the profile of the account the credential belongs to: id, email, name, role, avatar, preferred locale, and verification/creation timestamps. Account-level: a team-scoped API key is refused with 403.

Permisoprofile:readHerramienta MCPgetMeOperacióngetMe

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/me" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The authenticated account.object
idstringObligatorio
emailstringObligatorioacepta null
firstNamestringObligatorioacepta null
lastNamestringObligatorioacepta null
rolestringObligatorio
avatarstringObligatorioacepta null
preferredLocalestringObligatorioacepta null
emailVerifiedstringObligatorioacepta nullformat: date-time
createdAtstringObligatorioformat: date-time
updatedAtstringObligatorioformat: date-time
Ejemplo
{
  "id": "string",
  "email": "string",
  "firstName": "string",
  "lastName": "string",
  "role": "string",
  "avatar": "string",
  "preferredLocale": "string",
  "emailVerified": "2026-01-01T00:00:00.000Z",
  "createdAt": "2026-01-01T00:00:00.000Z",
  "updatedAt": "2026-01-01T00:00:00.000Z"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
PATCH/api/v1/me

Update the authenticated account

Updates the first and last name of the authenticated account. Both fields are required; the response is the account as it stands after the update. Account-level: a team-scoped API key is refused with 403.

Permisoprofile:writeHerramienta MCPupdateMeOperaciónupdateMe

Cuerpo de la petición

firstNamestringObligatoriominLength 2maxLength 255
lastNamestringObligatoriominLength 2maxLength 255

Petición

curl
curl -X PATCH "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/me" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "firstName": "string",
  "lastName": "string"
}'

Respuesta

200The updated account.object
idstringObligatorio
emailstringObligatorioacepta null
firstNamestringObligatorioacepta null
lastNamestringObligatorioacepta null
rolestringObligatorio
avatarstringObligatorioacepta null
preferredLocalestringObligatorioacepta null
emailVerifiedstringObligatorioacepta nullformat: date-time
createdAtstringObligatorioformat: date-time
updatedAtstringObligatorioformat: date-time
Ejemplo
{
  "id": "string",
  "email": "string",
  "firstName": "string",
  "lastName": "string",
  "role": "string",
  "avatar": "string",
  "preferredLocale": "string",
  "emailVerified": "2026-01-01T00:00:00.000Z",
  "createdAt": "2026-01-01T00:00:00.000Z",
  "updatedAt": "2026-01-01T00:00:00.000Z"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
GET/api/v1/me/sessions

List sign-in sessions

Lists the account's active browser/app sign-in sessions, newest first, with the device and location recorded at sign-in. `isCurrentSession` is false for every bearer credential. Account-level: a team-scoped API key is refused with 403.

Permisoprofile:readHerramienta MCPlistMySessionsOperaciónlistMySessions

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/me/sessions" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The account's sessions.object[]
idstringObligatorio
createdAtstringObligatorioformat: date-time
expiresAtstringObligatorioformat: date-time
isCurrentSessionbooleanObligatorio
authenticationTypestringObligatorioacepta null
countrystringObligatorioacepta null
citystringObligatorioacepta null
browserstringObligatorioacepta null
osstringObligatorioacepta null
deviceTypestringObligatorioacepta null
Ejemplo
[
  {
    "id": "string",
    "createdAt": "2026-01-01T00:00:00.000Z",
    "expiresAt": "2026-01-01T00:00:00.000Z",
    "isCurrentSession": true,
    "authenticationType": "string",
    "country": "string",
    "city": "string",
    "browser": "string",
    "os": "string",
    "deviceType": "string"
  }
]
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
DELETE/api/v1/me/sessions/{sessionId}

Revoke a sign-in session

Signs the account out of one session. Revocation is scoped to the caller's own sessions, so an unknown session id is a no-op rather than an error. Account-level: a team-scoped API key is refused with 403.

Permisoprofile:writeHerramienta MCPrevokeMySessionOperaciónrevokeMySession

Parámetros

sessionIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl -X DELETE "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/me/sessions/{sessionId}" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The session was revoked.object
successunknownObligatorio
Ejemplo
{
  "success": "string"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}

Teams

GET/api/v1/teams

List the caller's teams

Lists every team the authenticated account is an active member of, with the account's role in each. Teams whose membership is inactive or expired are omitted. A team-scoped API key lists only the single team it is scoped to.

Permisoteams:readHerramienta MCPlistTeamsOperaciónlistTeams

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The caller's teams.object[]
idstringObligatorio
namestringObligatorio
slugstringObligatorio
descriptionstringObligatorioacepta null
avatarUrlstringObligatorioacepta null
roleobjectObligatorio
idstringObligatorio
namestringObligatorio
Ejemplo
[
  {
    "id": "string",
    "name": "string",
    "slug": "string",
    "description": "string",
    "avatarUrl": "string",
    "role": {
      "id": "string",
      "name": "string"
    }
  }
]
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
POST/api/v1/teams

Create a team

Creates a team owned by the authenticated account, which also becomes its first member. The slug is derived from the name. Fails with 403 when the account is at its team limit. Account-level: a team-scoped API key is refused with 403.

Permisoteams:writeHerramienta MCPcreateTeamOperacióncreateTeam

Cuerpo de la petición

namestringObligatoriominLength 1maxLength 100
descriptionstringOpcionalmaxLength 1000

Petición

curl
curl -X POST "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "string",
  "description": "string"
}'

Respuesta

201The created team.object
idstringObligatorio
namestringObligatorio
slugstringObligatorio
descriptionstringObligatorioacepta null
avatarUrlstringObligatorioacepta null
roleobjectObligatorio
idstringObligatorio
namestringObligatorio
Ejemplo
{
  "id": "string",
  "name": "string",
  "slug": "string",
  "description": "string",
  "avatarUrl": "string",
  "role": {
    "id": "string",
    "name": "string"
  }
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
GET/api/v1/teams/{teamId}

Get a team

Returns one team the authenticated account belongs to. Teams the account is not an active member of answer 404, never 403, so team ids cannot be probed.

Permisoteams:readHerramienta MCPgetTeamOperacióngetTeam

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The team.object
idstringObligatorio
namestringObligatorio
slugstringObligatorio
descriptionstringObligatorioacepta null
avatarUrlstringObligatorioacepta null
roleobjectObligatorio
idstringObligatorio
namestringObligatorio
Ejemplo
{
  "id": "string",
  "name": "string",
  "slug": "string",
  "description": "string",
  "avatarUrl": "string",
  "role": {
    "id": "string",
    "name": "string"
  }
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
PATCH/api/v1/teams/{teamId}

Rename a team

Changes a team's display name. Requires the `edit_team_settings` permission on that team. The slug is deliberately left alone so existing links and invitations keep working.

Permisoteams:writeHerramienta MCPupdateTeamOperaciónupdateTeam

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Cuerpo de la petición

namestringObligatoriominLength 1maxLength 100

Petición

curl
curl -X PATCH "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "string"
}'

Respuesta

200The renamed team.object
idstringObligatorio
namestringObligatorio
slugstringObligatorio
descriptionstringObligatorioacepta null
avatarUrlstringObligatorioacepta null
roleobjectObligatorio
idstringObligatorio
namestringObligatorio
Ejemplo
{
  "id": "string",
  "name": "string",
  "slug": "string",
  "description": "string",
  "avatarUrl": "string",
  "role": {
    "id": "string",
    "name": "string"
  }
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}

Members

GET/api/v1/teams/{teamId}/members

List team members

Lists every membership of a team with the member's identity, role, and join date. Requires the `access_dashboard` permission on that team.

Permisomembers:readHerramienta MCPlistTeamMembersOperaciónlistTeamMembers

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/members" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The team's members.object[]
membershipIdstringObligatorio
userIdstringObligatorio
emailstringObligatorioacepta null
firstNamestringObligatorioacepta null
lastNamestringObligatorioacepta null
avatarstringObligatorioacepta null
roleIdstringObligatorio
roleNamestringObligatorioacepta null
isSystemRolebooleanObligatorio
isActivebooleanObligatorio
joinedAtstringObligatorioacepta nullformat: date-time
Ejemplo
[
  {
    "membershipId": "string",
    "userId": "string",
    "email": "string",
    "firstName": "string",
    "lastName": "string",
    "avatar": "string",
    "roleId": "string",
    "roleName": "string",
    "isSystemRole": true,
    "isActive": true,
    "joinedAt": "2026-01-01T00:00:00.000Z"
  }
]
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
DELETE/api/v1/teams/{teamId}/members/{userId}

Remove a team member

Removes a member from a team. Requires the `remove_members` permission on that team; the team owner can never be removed this way.

Permisomembers:writeHerramienta MCPremoveTeamMemberOperaciónremoveTeamMember

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255
userIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl -X DELETE "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/members/{userId}" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The member was removed.object
successunknownObligatorio
Ejemplo
{
  "success": "string"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}

Invitations

GET/api/v1/teams/{teamId}/roles

List the roles a team can assign

Lists every role id accepted by createTeamInvitation, with the permissions each one grants. System roles (`owner`, `member`, `guest`) exist on every team and are passed with `isSystemRole: true`; roles the team defined itself are passed with `isSystemRole: false`. `isAssignable` is false for roles an invitation cannot grant, such as `owner`. Requires the `access_dashboard` permission.

Permisomembers:readHerramienta MCPlistTeamRolesOperaciónlistTeamRoles

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/roles" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The roles this team can assign.object[]
roleIdstringObligatorio
namestringObligatorioacepta null
isSystemRolebooleanObligatorio
isAssignablebooleanObligatorio
permissionsstring[]Obligatorio
Ejemplo
[
  {
    "roleId": "string",
    "name": "string",
    "isSystemRole": true,
    "isAssignable": true,
    "permissions": [
      "string"
    ]
  }
]
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
GET/api/v1/teams/{teamId}/invitations

List pending team invitations

Lists invitations that have not been accepted and have not expired. Requires the `invite_members` permission; callers without it receive an empty list, never invitee emails.

Permisomembers:readHerramienta MCPlistTeamInvitationsOperaciónlistTeamInvitations

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/invitations" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The team's pending invitations.object[]
idstringObligatorio
emailstringObligatorio
roleIdstringObligatorio
roleNamestringObligatorioacepta null
isSystemRolebooleanObligatorio
createdAtstringObligatorioformat: date-time
expiresAtstringObligatorioformat: date-time
Ejemplo
[
  {
    "id": "string",
    "email": "string",
    "roleId": "string",
    "roleName": "string",
    "isSystemRole": true,
    "createdAt": "2026-01-01T00:00:00.000Z",
    "expiresAt": "2026-01-01T00:00:00.000Z"
  }
]
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
POST/api/v1/teams/{teamId}/invitations

Invite someone to a team

Sends an invitation email for a team seat. `roleId` is optional and defaults to `member`; call listTeamRoles for the other ids this team accepts, and pass `isSystemRole: false` alongside a role the team defined itself. Requires the `invite_members` permission and a free seat on the team's plan — inviting past the seat limit answers 403, and the response detail names the limit. The response never reveals whether the address already has an account or is already a member.

Permisoinvites:writeHerramienta MCPcreateTeamInvitationOperacióncreateTeamInvitation

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Cuerpo de la petición

emailstringObligatorioformat: emailminLength 1maxLength 255
roleIdstringOpcionalminLength 1maxLength 255default: "member"
isSystemRolebooleanOpcionaldefault: true

Petición

curl
curl -X POST "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/invitations" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "email": "user@example.com",
  "roleId": "member",
  "isSystemRole": true
}'

Respuesta

201The invitation was sent.object
successunknownObligatorio
Ejemplo
{
  "success": "string"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
DELETE/api/v1/teams/{teamId}/invitations/{invitationId}

Revoke a pending invitation

Deletes a pending invitation so its link stops working. Requires the `invite_members` permission. An already accepted or unknown invitation answers 404.

Permisoinvites:writeHerramienta MCPrevokeTeamInvitationOperaciónrevokeTeamInvitation

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255
invitationIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl -X DELETE "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/invitations/{invitationId}" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The invitation was revoked.object
successunknownObligatorio
Ejemplo
{
  "success": "string"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}

Billing

GET/api/v1/teams/{teamId}/billing

Get a team's subscription

Read-only summary of a team's plan, subscription status, billing interval, add-on units, and renewal date. Requires the `access_billing` permission. Checkout and plan changes are not exposed over the API.

Permisobilling:readHerramienta MCPgetTeamBillingOperacióngetTeamBilling

Parámetros

teamIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/teams/{teamId}/billing" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The team's subscription.object
planIdstringObligatorio
planNamestringObligatorio
statusstringObligatorioacepta null
intervalstringObligatorioacepta null
addonsobjectObligatorio
planExpiresAtstringObligatorioacepta nullformat: date-time
cancelAtPeriodEndbooleanObligatorio
needsPaymentActionbooleanObligatorio
Ejemplo
{
  "planId": "string",
  "planName": "string",
  "status": "string",
  "interval": "string",
  "addons": {},
  "planExpiresAt": "2026-01-01T00:00:00.000Z",
  "cancelAtPeriodEnd": true,
  "needsPaymentAction": true
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}

API keys

GET/api/v1/api-keys

List API keys

Lists the caller's personal API keys, or a team's keys when `teamId` is given (which requires the `manage_api_keys` permission on that team). Revoked keys are never listed, and no response can ever contain a key's secret. Account-level: a team-scoped API key is refused with 403.

Permisoapi-keys:readHerramienta MCPlistApiKeysOperaciónlistApiKeys

Parámetros

teamIdstringOpcionalin: queryminLength 1maxLength 255

Petición

curl
curl "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/api-keys" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The matching API keys.object[]
idstringObligatorio
namestringObligatorio
keyPrefixstringObligatorio
last4stringObligatorio
scopesstring[]Obligatorio
teamIdstringObligatorioacepta null
createdAtstringObligatorioformat: date-time
lastUsedAtstringObligatorioacepta nullformat: date-time
expiresAtstringObligatorioacepta nullformat: date-time
Ejemplo
[
  {
    "id": "string",
    "name": "string",
    "keyPrefix": "string",
    "last4": "string",
    "scopes": [
      "string"
    ],
    "teamId": "string",
    "createdAt": "2026-01-01T00:00:00.000Z",
    "lastUsedAt": "2026-01-01T00:00:00.000Z",
    "expiresAt": "2026-01-01T00:00:00.000Z"
  }
]
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
POST/api/v1/api-keys

Create an API key

Creates an API key for the caller, or for a team when `teamId` is given. The scopes requested must be a subset of the calling credential's own scopes. The `secret` in the response is returned exactly once and is not recoverable afterwards. Account-level: a team-scoped API key is refused with 403.

Permisoapi-keys:writeHerramienta MCPcreateApiKeyOperacióncreateApiKey

Cuerpo de la petición

namestringObligatoriominLength 1maxLength 100
scopesstring[]ObligatoriominItems 1maxItems 10
profile:readprofile:writeteams:readteams:writemembers:readmembers:writeinvites:writebilling:readapi-keys:readapi-keys:write
teamIdstringOpcionalminLength 1maxLength 255
expiresInDaysintegerOpcionalminimum 1maximum 365

Petición

curl
curl -X POST "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/api-keys" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "string",
  "scopes": [
    "profile:read"
  ],
  "teamId": "string",
  "expiresInDays": 0
}'

Respuesta

201The created key and its one-time secret.object
keyobjectObligatorio
idstringObligatorio
namestringObligatorio
keyPrefixstringObligatorio
last4stringObligatorio
scopesstring[]Obligatorio
teamIdstringObligatorioacepta null
createdAtstringObligatorioformat: date-time
lastUsedAtstringObligatorioacepta nullformat: date-time
expiresAtstringObligatorioacepta nullformat: date-time
secretstringObligatorio
Ejemplo
{
  "key": {
    "id": "string",
    "name": "string",
    "keyPrefix": "string",
    "last4": "string",
    "scopes": [
      "string"
    ],
    "teamId": "string",
    "createdAt": "2026-01-01T00:00:00.000Z",
    "lastUsedAt": "2026-01-01T00:00:00.000Z",
    "expiresAt": "2026-01-01T00:00:00.000Z"
  },
  "secret": "string"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
PATCH/api/v1/api-keys/{keyId}

Update an API key's scopes

Replaces the scopes granted to an API key; the list is not merged with the key's current scopes, so send the full set you want it to end up with. The new scopes must be a subset of the calling credential's own scopes. The change takes effect immediately, including for the key making the call. Keys belonging to another account, and revoked keys, answer 404 so key ids cannot be probed. Account-level: a team-scoped API key is refused with 403.

Permisoapi-keys:writeHerramienta MCPupdateApiKeyOperaciónupdateApiKey

Parámetros

keyIdstringObligatorioin: pathminLength 1maxLength 255

Cuerpo de la petición

scopesstring[]ObligatoriominItems 1maxItems 10
profile:readprofile:writeteams:readteams:writemembers:readmembers:writeinvites:writebilling:readapi-keys:readapi-keys:write

Petición

curl
curl -X PATCH "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/api-keys/{keyId}" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "scopes": [
    "profile:read"
  ]
}'

Respuesta

200The updated key.object
idstringObligatorio
namestringObligatorio
keyPrefixstringObligatorio
last4stringObligatorio
scopesstring[]Obligatorio
teamIdstringObligatorioacepta null
createdAtstringObligatorioformat: date-time
lastUsedAtstringObligatorioacepta nullformat: date-time
expiresAtstringObligatorioacepta nullformat: date-time
Ejemplo
{
  "id": "string",
  "name": "string",
  "keyPrefix": "string",
  "last4": "string",
  "scopes": [
    "string"
  ],
  "teamId": "string",
  "createdAt": "2026-01-01T00:00:00.000Z",
  "lastUsedAt": "2026-01-01T00:00:00.000Z",
  "expiresAt": "2026-01-01T00:00:00.000Z"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}
DELETE/api/v1/api-keys/{keyId}

Revoke an API key

Revokes an API key immediately, including the key making the call. Keys belonging to another account answer 404 so key ids cannot be probed. Account-level: a team-scoped API key is refused with 403.

Permisoapi-keys:writeHerramienta MCPrevokeApiKeyOperaciónrevokeApiKey

Parámetros

keyIdstringObligatorioin: pathminLength 1maxLength 255

Petición

curl
curl -X DELETE "https://nextjs-saas-template.lubomirgeorgiev.com/api/v1/api-keys/{keyId}" \
  -H "Authorization: Bearer $API_KEY"

Respuesta

200The key was revoked.object
successunknownObligatorio
Ejemplo
{
  "success": "string"
}
Respuestas de error400401403404429Ampliar

Todo fallo es un documento problem de RFC 9457 cuyo code es estable y sin traducir.

400
The request body, query, or path failed validation.
401
The credential is missing, malformed, expired, or revoked.
403
The credential lacks the required scope or the caller lacks the team permission.
404
The addressed resource does not exist or is not visible to this credential.
429
Rate limit exceeded; retry after the number of seconds in `retry-after`. The `RateLimit-*` headers describe the exhausted bucket.
Ejemplo
{
  "type": "string",
  "title": "string",
  "status": 0,
  "code": "string",
  "detail": "string",
  "requestId": "string",
  "retryAfter": 0,
  "errors": [
    {
      "in": "body",
      "pointer": "string",
      "code": "required",
      "params": {}
    }
  ]
}