> ## Documentation Index
> Fetch the complete documentation index at: https://docs.base44.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete URL redirect

> <Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Removes a redirect from the app's published site.

The source path goes back to serving whatever the app has at it, or a 404 when it has nothing.

Base44 tries to clear the cached copy so the change takes effect right away, but that can fail without failing the call. When it does, the old path keeps serving the target's cached page instead of redirecting to it, until the cache refreshes. That looks like the redirect still works, so check the status code rather than the page.

The response body is empty, so read the status code.

URL redirects are part of custom domains, so creating, updating and deleting one needs a workspace whose plan includes them. Listing them doesn't.



## OpenAPI

````yaml /developers/references/app-management/app-management-openapi.json delete /api/apps/{app_id}/url-redirects/{redirect_id}
openapi: 3.1.0
info:
  title: Base44 App Management API
  version: 1.0.0
servers:
  - url: https://app.base44.com
security:
  - ApiKeyAuth: []
paths:
  /api/apps/{app_id}/url-redirects/{redirect_id}:
    delete:
      summary: Delete URL redirect
      description: >-
        <Info>This API is in beta. Endpoints, fields, and behavior may still
        change, so avoid depending on it in production.</Info>


        Removes a redirect from the app's published site.


        The source path goes back to serving whatever the app has at it, or a
        404 when it has nothing.


        Base44 tries to clear the cached copy so the change takes effect right
        away, but that can fail without failing the call. When it does, the old
        path keeps serving the target's cached page instead of redirecting to
        it, until the cache refreshes. That looks like the redirect still works,
        so check the status code rather than the page.


        The response body is empty, so read the status code.


        URL redirects are part of custom domains, so creating, updating and
        deleting one needs a workspace whose plan includes them. Listing them
        doesn't.
      operationId: delete_url_redirect_api_apps__app_id__url_redirects__redirect_id__delete
      parameters:
        - name: app_id
          in: path
          required: true
          schema:
            type: string
            description: ID of the app whose URL redirects you want to work with.
            title: App Id
          description: ID of the app whose URL redirects you want to work with.
          example: 6820f3a4e7b91d003c45a1f2
        - name: redirect_id
          in: path
          required: true
          schema:
            type: string
            description: >-
              ID of the redirect. Get this from [List URL
              redirects](/api-reference/list-url-redirects).
            title: Redirect Id
          description: >-
            ID of the redirect. Get this from [List URL
            redirects](/api-reference/list-url-redirects).
          example: 68c2d1e5f3b8a4216e9b5583
      responses:
        '204':
          description: The redirect was removed.
        '401':
          description: Missing or invalid credentials.
        '402':
          description: This workspace's plan doesn't include custom domains.
        '403':
          description: >-
            You don't have access to this app, or you used a workspace API key.
            These endpoints take a personal API key.
        '404':
          description: The app has no URL redirect with this ID, or the app doesn't exist.
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: api_key
      description: Personal API key.

````