> ## Documentation Index > Fetch the complete documentation index at: https://docs.recurso.dev/llms.txt > Use this file to discover all available pages before exploring further. # Delete SSO Connection > Remove the tenant's SAML SSO connection so the public SP endpoints stop answering. Removes the tenant's SAML SSO connection entirely. The public [metadata](/api-reference/auth/saml-metadata), [login](/api-reference/auth/saml-login) and [ACS](/api-reference/auth/saml-acs) endpoints return `404` for the tenant from this point on, and a subsequent [`GET /v1/sso/connection`](/api-reference/sso/get) returns `404` until a new connection is created with [`PUT /v1/sso/connection`](/api-reference/sso/update). Existing dashboard sessions opened through SSO are not revoked by this call; users can still sign in with their password afterwards. To pause SSO without discarding the IdP configuration, update the connection with `enabled: false` instead. Only owners and admins can call this endpoint from a dashboard session; members receive `403`. API-key callers act with full tenant access. ## Example Request ```bash theme={null} curl -X DELETE https://api.recurso.dev/v1/sso/connection \ -H "Authorization: Bearer $API_KEY" ``` ## Response ```json theme={null} { "status": "removed" } ``` ## Errors | Status | Code | When | Fix | | ------ | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | `401` | `unauthorized` | No API key or session cookie was sent. An invalid API key returns `invalid_api_key`; a key for the wrong mode (live vs test) returns `key_mode_mismatch`. | Send `Authorization: Bearer ` with a key for the right mode, or sign in to the dashboard. | | `403` | `forbidden` | The dashboard session belongs to a member, not an owner or admin. | Ask an owner or admin to remove the connection, or use an API key. | | `404` | `not_found` | The tenant has no SSO connection to remove. | Nothing to do — the tenant is already without SSO. | | `500` | `internal_error` | The connection could not be deleted. | Retry; if it persists, contact support. | Errors use the standard envelope — see [Errors](/api-reference/errors). ## OpenAPI ````yaml DELETE /v1/sso/connection openapi: 3.1.0 info: title: Recurso API version: 1.0.0 description: | The Recurso billing engine REST API. Authenticate by passing your API key as a bearer token: Authorization: Bearer Obtain an API key by registering a tenant via `POST /auth/register`. All authenticated endpoints live under the `/v1` prefix. Mutating endpoints support idempotency via the `Idempotency-Key` header. license: name: MIT identifier: MIT servers: - url: https://billing.example.com description: >- Example deployment — substitute the base URL of your own Recurso deployment. security: - bearerAuth: [] tags: - name: System description: Health, version, and API metadata - name: Auth description: Tenant registration - name: Plans description: Product catalog plans - name: Customers description: Customer management - name: Subscriptions description: Subscription lifecycle - name: Invoices description: Invoices, PDFs, and Indian GST e-invoicing - name: Coupons description: Discounts - name: Usage description: Metered usage events - name: Credit Notes description: Customer credits - name: Quotes description: Quote-to-invoice lifecycle - name: Webhooks description: Webhook endpoint management and event feed - name: Analytics description: Revenue analytics - name: Checkout description: Public hosted checkout for invoices - name: Payments description: Payment order creation - name: Inbound Webhooks description: Receivers for payment-gateway callbacks (Razorpay, Stripe) - name: Customer Portal description: Customer-facing portal — magic-link auth and session-scoped data - name: Developer description: API key management - name: Account description: Tenant account settings - name: Finance description: Ledger accounts, entries, reconciliation, and revenue recognition - name: Settings description: Tax (GST) and e-invoicing (IRP) configuration - name: Consents description: Consent records for RBI-compliant recurring billing - name: Referrals description: Customer referral program - name: Gifts description: Gift subscriptions - name: Mandates description: UPI Autopay mandates - name: Offline Payments description: Virtual accounts and manually recorded payments - name: Organizations description: Multi-entity organizations grouping several tenants - name: Accounting description: QuickBooks / Xero accounting integrations - name: Churn description: Churn risk scoring and alerts - name: Cancel Flows description: Configurable retention flows shown at cancellation time - name: Dunning description: Dunning analytics and multi-channel dunning campaigns paths: /v1/sso/connection: delete: tags: - Auth summary: Delete the tenant's SAML SSO connection (owner/admin only) operationId: deleteSSOConnection responses: '200': description: >- Connection removed. Action-shape `{status}` object, not wrapped in data. content: application/json: schema: type: object properties: status: type: string enum: - removed '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' security: - sessionCookie: [] - bearerAuth: [] components: responses: Unauthorized: description: Missing or invalid credentials (API key or session cookie). content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: Authenticated but not permitted (insufficient role). content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: The requested resource does not exist. content: application/json: schema: $ref: '#/components/schemas/Error' schemas: Error: type: object required: - error properties: error: type: object description: Structured error detail. required: - code - message properties: code: type: string description: Stable machine-readable error code. examples: - validation_failed - unauthorized - forbidden - not_found - conflict - rate_limited - internal_error - invalid_api_key - key_mode_mismatch - over_refund - invoice_not_paid - invoice_already_paid message: type: string description: Human-readable explanation. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API key description: >- Tenant API key obtained from `POST /auth/register` or `POST /v1/developer/keys`. sessionCookie: type: apiKey in: cookie name: recurso_session description: > Dashboard user session cookie (httpOnly) issued by `POST /auth/register` and `POST /auth/login`. v1 endpoints accept EITHER this cookie or the tenant API key (`bearerAuth`). ````