Skip to main content
POST
Open the team's Admin Portal
Owners only: whoever sets up the directory decides everyone’s role.
  • intent: domain_verification proves your team owns its email domain, sso connects your identity provider (SAML or OIDC, such as Okta), and dsync syncs your directory’s people (SCIM). Set them up in that order: SSO needs a verified domain.
  • Only the Dashboard returns the portal’s link, since anyone holding it can change your team’s sign-in. Elsewhere this returns a dashboard_url to the Single sign-on page, where an Owner opens it. To have your IT admin do it, send them a setup email with POST /v1/team/sso/it-admin-invitations.
  • On the Dashboard each call makes a new link, which stops working five minutes after it was made, at expires_at; Pomerado keeps none.
  • Callers: an API key, an MCP OAuth token or a Dashboard session.
  • Permission: team:manage; an API key also needs team:manage.
  • Effect: Creates or changes something.
  • Errors: team_unavailable, role_permission_missing, owner_required, and the errors any request can get.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
intent
enum<string>
required
Available options:
domain_verification,
sso,
dsync

Response

Elsewhere: the page that opens it

dashboard_url
string
required

A signed-in Dashboard page where the person finishes this and sees the secret once