---
title: "Register a new SSO provider."
method: POST
path: "/admin/sso/providers"
tags: ["admin"]
---

# Register a new SSO provider.

`POST /admin/sso/providers`

## Request body

- object
  - `type` 'saml', required
  - `metadata_url` string, uri
  - `metadata_xml` string
  - `domains` string[]
  - `attribute_mapping` SAMLAttributeMappingSchema
    - `keys` object

## Response `200`

SSO provider was created.

- SSOProviderSchema
  - `id` string, uuid
  - `sso_domains` object[]
    - `domain` string, hostname
  - `saml` object
    - `entity_id` string
    - `metadata_xml` string
    - `metadata_url` string
    - `attribute_mapping` SAMLAttributeMappingSchema
      - `keys` object

## Other responses

- `400` — HTTP Bad Request response. Can occur if the passed in JSON cannot be unmarshalled properly or when CAPTCHA verification was not successful. In certain cases can also occur when features are disabled on the server (e.g. sign ups). It may also mean that the operation failed due to some constraint not being met (such a user already exists for example).
- `401` — HTTP Unauthorized response.
- `403` — HTTP Forbidden response.

---

[API](https://skmtc.net/supabase/apis/supabase-auth-rest-api.md) · [All operations](https://skmtc.net/supabase/apis/supabase-auth-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/supabase/supabase-auth-rest-api/versions/2664b89bee49/schema)