FDL Migration / SDK Guide

Migrating from Firebase Dynamic Links

Firebase Dynamic Links (FDL) shut down on August 25, 2025. Crisp is a drop-in resolver with the same link shape, deferred deep-link support, and one SDK call to swap. This guide takes you from a Firebase project to fully migrated in about 15 minutes.

Before you start: export your existing links from the Firebase console (Dynamic Links → ⋯ → Export). You'll upload that CSV in step 2. Your page.link domain keeps working during the cutover.

1. Install the SDK

Add the crisp SDK to your project. React Native and Flutter ship first (thin clients — hashing is server-side); native iOS and Android follow the same surface.

terminalcopy

npm install @crisp-to/react-native @react-native-async-storage/async-storage

pubspec.yamlcopy

dependencies:
  crisp_flutter: ^0.1.0

Package.swiftcopy

.package(url: "https://github.com/crisp-to/crisp-ios", from: "0.1.0")

build.gradle.ktscopy

implementation("to.crisp:crisp-android:0.1.0")

terminalcopy

npm install @crisp-to/web  # web SDK — coming in phase 2

2. Map your domain & import

In the crisp dashboard, open Deep links → Firebase import, add your existing page.link domain, and upload the CSV you exported. Crisp remaps every short suffix, parameter, and fallback automatically.

3. Swap the resolver call

Replace your getDynamicLink / handleUniversalLink handler with the crisp deferred-link handler. One callback covers both live links and post-install deferred matches, so your routing logic stays.

App.tsxTypeScript

// Before — Firebase Dynamic Links
// dynamicLinks().onLink(link => { ... })

import { CrispSDK } from "@crisp-to/react-native";

CrispSDK.initialize({ apiKey: "sdk_live_…", appId: "app_…" });
CrispSDK.onDeferredLink((link) => {
  router.navigate(link.shortCode, link.params);  // fires for live AND deferred
});

main.dartDart

// Before — FirebaseDynamicLinks.instance.onLink.listen(...)

import 'package:crisp_flutter/crisp_flutter.dart';

CrispSDK.initialize(const CrispOptions(apiKey: 'sdk_live_…', appId: 'app_…'));
CrispSDK.onDeferredLink((link) {
  router.go(link.shortCode!, extra: link.params);  // live AND deferred
});

AppDelegate.swiftSwift

// Before — DynamicLinks.dynamicLinks().handleUniversalLink(url) { ... }

import CrispSDK

CrispSDK.shared.initialize(apiKey: "sdk_live_…", appId: "app_…")
CrispSDK.shared.onDeferredLink { link in
  Router.handle(shortCode: link.shortCode, params: link.params)
}

MainActivity.ktKotlin

// Before — FirebaseDynamicLinks.getInstance()...

CrispSDK.initialize(context, "sdk_live_…", "app_…")
CrispSDK.onDeferredLink { link ->
  navController.navigate(link.shortCode, link.params)
}

app.tsTypeScript

// Web SDK ships in phase 2 — same resolver surface.
const link = await crisp.resolve(window.location.href)
router.push(link.params.path)

4. Deferred deep links

When a user taps a link without the app installed, crisp preserves the destination across the App Store / Play Store install. On first launch the SDK matches the install automatically — your onDeferredLink handler fires with link.deferred === true and the original params. No extra call needed.

Parameter reference

Every FDL query parameter maps to a crisp field. The import does this automatically; the table is for links you build by hand.

FDL param

Crisp field

Purpose

REST API

Everything the dashboard does — shorten, restyle, re-point — is available over HTTPS at api.crisp.to. Create a workspace key in Dashboard → API keys (it's shown once) and send it as a Bearer token. Keys work on every plan; plan limits apply to API calls exactly as they do in the dashboard.

authenticationcurl

curl https://api.crisp.to/v1/dashboard/workspaces/me \
  -H "Authorization: Bearer wk_live_…"

Responses use one envelope: {"data": …} on success, {"error": {"code", "message"}} otherwise. Codes you'll see: invalid_key (401), not_found (404), validation_failed (400/409), plan_limit (402), rate_limited (429).

Short links API

Create a link — optional short_code (unique per domain), up to 10 tags, and an expires_at ISO timestamp (the link answers 410 after it):

POST /v1/dashboard/linkscurl

curl -X POST https://api.crisp.to/v1/dashboard/links \
  -H "Authorization: Bearer wk_live_…" -H "Content-Type: application/json" \
  -d '{"type":"short","destination_url":"https://example.com/sale",
       "short_code":"sale","tags":["summer","email"]}'

// 201 → {"data":{"link":{…},"url":"https://crisp.to/sale"}}

List and search with GET /v1/dashboard/links?type=short&q=…&tag=…, edit with PATCH /v1/dashboard/links/{id} (changing destination_url re-points the live short URL immediately), delete with DELETE, and export everything as CSV from GET /v1/dashboard/links/export. Free plans create 50 links per calendar month — a plan_limit error (402) tells you when you've hit it.

QR codes API

A QR code wraps its own short link, so every code is dynamic: re-point the destination any time and existing prints keep working. Scans are the wrapped link's clicks.

POST /v1/dashboard/qrcurl

curl -X POST https://api.crisp.to/v1/dashboard/qr \
  -H "Authorization: Bearer wk_live_…" -H "Content-Type: application/json" \
  -d '{"name":"Menu QR","destination_url":"https://cafe.example/menu",
       "fg_color":"#1A1712","bg_color":"#FBF4E9"}'

// 201 → {"data":{"qr":{…},"url":"https://crisp.to/x7Kq"}}

Colors (fg_color, bg_color, frame_color) work on every plan. The style object — module shapes (dots: square/dots/rounded), corner styles, error-correction level, and logo_url — is Creator and up (402 otherwise). GET /v1/dashboard/qr lists codes with scan counts; PATCH /v1/dashboard/qr/{id} restyles or re-points; DELETE removes the code and its wrapped link.

The machine-readable OpenAPI spec ships in the repo (apps/api-crisp-to/openapi.yaml) and covers the full surface, including bio pages and billing.

← Previous

Parameter reference

Short links API

Last updated — October 26, 2026

Terms of Service

1. Who we are and what you agree to

These Terms are a contract between you and Devspace Hub SRL, a company registered in Romania ("crisp", "we"), covering crisp.to and everything it serves: short links, QR codes, pages, the dashboard and the API. You agree to them by creating an account or by using the service. If you use crisp for an organization, you accept these Terms for that organization.

If you are a consumer in the European Union, nothing in these Terms limits rights you have under consumer law that cannot be limited by contract.

2. Your account

You are responsible for what happens under your account and for keeping your credentials and API keys secure. Handles, custom domains and page content must not impersonate anyone or infringe anyone's rights.

3. Acceptable use

You may not use crisp to shorten, redirect to, or host malware, phishing, fraud, content that is unlawful where you or your visitors are, or content that infringes third-party rights. We may disable a link, code or page that endangers users or breaches these Terms, and we may close an account used mainly for such purposes.

4. Link durability — our promise

4.1 Not because of your plan. We will never deactivate a short link, QR code or page because of your plan status. If a trial ends, a subscription lapses, you downgrade or you stop paying altogether, every existing link and code keeps redirecting and every page stays published at its crisp.to address. Plan limits apply only to creating new things.

4.2 Custom domains. Serving a page on your own domain is a plan feature. If the plan that includes it ends, the custom domain is paused, not deleted, and the page keeps working at its crisp.to address; the domain resumes when the plan is restored.

4.3 What can stop a link. A link, code or page stops working only if: (a) you delete it, or delete your account; (b) you set an expiry date on it yourself; (c) it breaches section 3; (d) we are legally required to disable it — for example by a court order, a lawful authority request, or a data-protection obligation we cannot meet any other way; or (e) something outside our reasonable control makes it impossible, such as the loss of a domain through registry or registrar action, your own domain lapsing, failure of an upstream provider, or an event described in section 10. In cases (d) and (e) we will restore service where and as soon as we lawfully can.

4.4 Durability is not availability. This promise is that we will not switch your links off. It is not a guarantee of uninterrupted service; see section 6.

4.5 If crisp ever closes. If we decide to discontinue the service, we will give at least 12 months' notice by email and on the website, keep every existing link, code and page redirecting throughout that period, and let you export all of your links and destinations so you can move them.

4.6 This section is protected. Any change to this section 4 applies only to links, codes and pages created after the change takes effect. Links, codes and pages created before it keep the version of this section that was in force when they were created.

4.7 If crisp changes hands. If we transfer the service to another company, this section transfers with it and binds the new operator for existing links, codes and pages.

5. Plans and billing

Paid plans renew automatically until cancelled; you can cancel at any time from the Billing tab and the plan stays active until the end of the period you have paid for. Fees are billed in advance and are non-refundable except where the law requires otherwise. If you are a consumer in the EU you may have a 14-day right of withdrawal; by starting a paid plan you ask us to begin providing it immediately, and you acknowledge that you lose the right of withdrawal once the service has been fully performed for the period you paid for. We will tell you before any price change affects you.

6. Availability and support

We run crisp on a global edge network and work to keep it available at all times, but we do not promise any particular uptime and there may be interruptions for maintenance, upgrades or reasons outside our control. Support is by email; paid plans receive priority. We may change, add or remove features, provided we do not break section 4.

7. Your content and data

You own what you put into crisp: your destinations, page content, images and the email addresses your pages collect. You give us the licence needed to store and serve it, including serving pages on your custom domain. Personal data is handled as described in our Privacy Policy; for email addresses your page collects, you are the controller and we process them for you.

8. Warranties

To the extent the law allows, crisp is provided as it is and as available, without warranties of fitness for a particular purpose. In particular, a short link or QR code redirects to the destination you set; we are not responsible for what is at that destination, for the content of your pages, or for the continued existence of websites you link to. Consumers' statutory guarantees are not affected.

9. Limitation of liability

To the extent the law allows: (a) neither party is liable for indirect or consequential loss, including lost profits, lost revenue, lost data, reprinting costs or the cost of replacing printed material; and (b) our total liability for all claims in any 12-month period is limited to the fees you paid us in the 12 months before the event giving rise to the claim, or €50 if you paid none. Nothing in these Terms limits liability for death or personal injury, fraud, gross negligence or wilful misconduct, or any liability that cannot be limited under the law that applies to you.

10. Events outside our control

We are not responsible for failing to do something these Terms require if the failure is caused by an event outside our reasonable control — including failure of internet infrastructure, domain registries or registrars, upstream hosting or network providers, denial-of-service attacks, government action, or natural disaster. We will do what we reasonably can to restore the service.

11. Changes to these Terms

We may update these Terms as the product evolves. We will announce material changes in the dashboard or by email at least 14 days before they take effect; if you do not agree, you can delete your account before then. Section 4.6 limits how changes affect existing links, codes and pages.

12. Ending the agreement

You can delete your account at any time from the dashboard, which deletes your links, codes and pages (see our data deletion page). We may suspend or close an account that breaches section 3, after giving notice where it is reasonable to do so. Sections 4.5 to 4.7, 8, 9, 10 and 13 survive the end of this agreement.

13. Governing law and disputes

These Terms are governed by the law of Romania. Disputes will be heard by the competent courts for our registered seat in Romania. If you are a consumer, you also keep the protection of mandatory rules of the country where you live and may bring a claim in its courts; in Romania you may also contact the National Authority for Consumer Protection (ANPC) or an alternative dispute resolution body.

14. Contact

Devspace Hub SRL · Romania · support@crisp.to

Draft terms, published for transparency ahead of general availability and under review by counsel; the link durability promise in section 4 is in force as written. Static copy: docs.crisp.to/terms/.

Migrating from Firebase Dynamic Links

1. Install the SDK

2. Map your domain & import

3. Swap the resolver call

4. Deferred deep links

Parameter reference

REST API

Short links API

QR codes API

How can we help?

Popular articles

Still stuck?

Terms of Service

1. Who we are and what you agree to

2. Your account

3. Acceptable use

4. Link durability — our promise

5. Plans and billing

6. Availability and support

7. Your content and data

8. Warranties

9. Limitation of liability

10. Events outside our control

11. Changes to these Terms

12. Ending the agreement

13. Governing law and disputes

14. Contact