Create URL redirect

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

Adds a 301 redirect to the app’s published site.

Use it to keep old links working after you rename or remove a page. The rule takes effect on the published site once this call returns.

Base44 also tries to drop any cached copy of the source path so visitors get the redirect straight away, but that step can fail without failing the call. When it does, the source URL keeps serving its cached page with a 200 instead of the new 301 until the cache refreshes on its own. A prefix rule affects child paths too, and each one has its own cached copy. Base44 drops the copies it knows about, and any it doesn’t keep serving their old page until that cache expires.

A rule is rejected when:

• Its source is a path the redirect layer never sees, which covers /sitemap.xml, /robots.txt, /favicon.ico, /manifest.json, /link_preview.png, /llms.txt, /.well-known/*, and the app’s auth paths
• Its source and target are the same
• It’s a prefix rule starting at /
• It overlaps another rule, so a prefix rule at /docs blocks a single rule at /docs/intro
• It would make a visitor follow two redirects in a row, which happens when an internal target matches another rule’s source

An app can hold up to 50 rules, and the 51st is rejected.

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

The response includes fields beyond the ones documented here. Don’t rely on undocumented response fields, as they can change at any time.

POST /api/apps/{app_id}/url-redirects

Create URL redirect

cURL

curl --request POST \
  --url https://app.base44.com/api/apps/{app_id}/url-redirects \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '
{
  "source_path": "/old-pricing",
  "target_path": "/pricing",
  "match_type": "single"
}
'

200

{
  "id": "68c2d1e5f3b8a4216e9b5583",
  "source_path": "/old-pricing",
  "target_path": "/pricing",
  "match_type": "single"
}

Authorizations

api_key · string · header · required

Personal API key.

Path Parameters

app_id · string · required

ID of the app whose URL redirects you want to work with.

Body

application/json

source_path · string · required

Path visitors request, starting with / and carrying no query string or fragment. Base44 strips a trailing slash and decodes percent-escapes before storing it, so /old/ and /%6Fld are the same rule.

Required string length: 1 - 512

Example:

"/old-pricing"

target_path · string · required

Where to send the visitor. Either an internal path starting with /, normalized the same way as source_path, or an absolute https:// URL on another site, kept as you sent it. Send it without a query string or fragment. The visitor's own query string is carried over to the destination, so /old?utm=x lands on /new?utm=x.

Required string length: 1 - 512

Example:

"/pricing"

match_type · enum<string> · default: single

Use single to redirect that exact path, or prefix to redirect it and everything under it, keeping the remainder of the path. Defaults to single, so omitting it on an update turns an existing prefix rule into a single one and its child paths stop redirecting.

Available options: single, prefix

Example:

"single"

Response

200

application/json

The redirect that was created.

One 301 redirect rule on the app's published site.

id · string · required

ID of the redirect. Pass it as redirect_id to Update URL redirect and Delete URL redirect.

Example:

"68c2d1e5f3b8a4216e9b5583"

source_path · string · required

The path visitors request, normalized with no trailing slash and percent-escapes decoded.

Example:

"/old-pricing"

target_path · string · required

Where the visitor is sent. Either an internal path, normalized the same way as source_path, or an absolute https:// URL on another site, kept exactly as you sent it.

Example:

"/pricing"

match_type · enum<string> · required

How the rule matches. A single rule redirects that exact path, and a prefix rule redirects it and everything under it, keeping the remainder of the path.

Available options: single, prefix

Example:

"single"