Seamless.ai

Unlike OpenAI or DeepAI, Seamless.AI does not offer a publicly documented self-serve API key that anyone can generate from a settings page. The availability of programmatic API access, the specific REST endpoint base URL, and the request/response schema are all tied to your sales contract and account tier. Before writing a single line of code or creating an API Group in FlutterFlow, take these two steps: Step A — Contact your Seamless.AI account manager or support team (support@seamless.ai or your dedicated CSM) and ask explicitly: 'Does my current plan include REST API access? What is the API base URL and authentication format?' Get this in writing, along with an API key and any documentation they can share. Step B — Ask about credit and rate limits. Seamless.AI charges credits for enrichment lookups. Know how many credits your plan includes per month and whether API calls consume the same pool as manual searches. This shapes how aggressively you cache results in your FlutterFlow app — hitting the API on every page load would drain credits fast. Once you have an API key and confirmed base URL, write them down securely. You will place the API key in your Cloud Function environment — never in FlutterFlow, never in Dart code, never in App Constants. The base URL will vary by account; a typical pattern is something like https://api.seamless.ai or a versioned variant, but do not assume — use the URL your account team provides.

Seamless.AI API requests contain or return PII (personally identifiable information) — real email addresses, phone numbers, and names of actual people. From a security perspective this means two things: the API key must never appear in a client build (it could allow unauthorized access to PII on your billing), and the proxy itself should be gated behind authentication. Create a Firebase Cloud Function (Node.js 18, Blaze plan required for outbound HTTP). The function should: 1. Verify the Firebase ID token from the incoming FlutterFlow request — this ensures only signed-in users of your app can call Seamless.AI through your proxy, not random internet users who discover the URL. 2. Read the SEAMLESS_KEY environment variable (set via firebase functions:config:set or Google Cloud Secret Manager). 3. Forward the enrichment query (company domain, person name, filters) to the Seamless.AI API endpoint with the API key in the appropriate header. 4. Return the JSON response to FlutterFlow. 5. Include CORS headers so web builds can receive the response. The exact authentication header format depends on what your account team provides — common patterns are Authorization: Bearer {key} or a custom header like X-API-Key: {key}. Confirm this from the API documentation your account provides. Deploy the function and note its HTTPS trigger URL. That URL is what goes into FlutterFlow — not the Seamless.AI URL.

1// functions/index.js (Firebase Cloud Functions, Node.js 18)
2// Replace SEAMLESS_BASE_URL and header format with values from your account team
3const functions = require('firebase-functions');
4const admin = require('firebase-admin');
5const axios = require('axios');
6admin.initializeApp();
7
8exports.seamlessProxy = functions.https.onRequest(async (req, res) => {
9  res.set('Access-Control-Allow-Origin', '*');
10  res.set('Access-Control-Allow-Methods', 'POST, OPTIONS');
11  res.set('Access-Control-Allow-Headers', 'Content-Type, Authorization');
12  if (req.method === 'OPTIONS') { res.status(204).send(''); return; }
13
14  // Verify Firebase ID token from FlutterFlow
15  const authHeader = req.headers.authorization || '';
16  const idToken = authHeader.replace('Bearer ', '');
17  try {
18    await admin.auth().verifyIdToken(idToken);
19  } catch (e) {
20    res.status(401).json({ error: 'Unauthorized' });
21    return;
22  }
23
24  const apiKey = functions.config().seamless.key;
25  const baseUrl = 'https://api.seamless.ai'; // Replace with your actual base URL
26
27  try {
28    const response = await axios.post(
29      `${baseUrl}/search`,  // Replace with actual endpoint path
30      req.body,
31      {
32        headers: {
33          'Authorization': `Bearer ${apiKey}`, // Confirm header format with account team
34          'Content-Type': 'application/json',
35        },
36      }
37    );
38    res.json(response.data);
39  } catch (err) {
40    res.status(err.response?.status || 500).json({ error: err.message });
41  }
42});

Open FlutterFlow and navigate to API Calls in the left navigation panel. Click + Add and choose Create API Group. Name it SeamlessAI and set the Base URL to your Cloud Function HTTPS trigger URL — for example https://us-central1-YOUR-PROJECT.cloudfunctions.net/seamlessProxy. Do not put the Seamless.AI base URL here — the Cloud Function is your base URL from FlutterFlow's perspective. Now click + Add inside the group to create an API Call for your primary enrichment query. For a contact search, name it SearchContacts and set the method to POST. Under Headers, add one header: Authorization with the value Bearer {{ authToken }}. Then click the Variables tab and add a variable called authToken (type String) — this will hold the Firebase ID token from the logged-in user, which the proxy uses to verify the request. For the request body, set the type to JSON and add a template that matches the query structure from your Seamless.AI API documentation. A typical contact search might look like: { "company_domain": "{{ domain }}", "job_title": "{{ jobTitle }}" } Add domain and jobTitle as String variables in the Variables tab. Note: the exact request body shape depends entirely on what Seamless.AI's API specification says for your account. Use the documentation your account team provides as the authoritative spec — do not guess field names.

1// API Call body template (JSON, adjust field names to your Seamless.AI API spec)
2{
3  "company_domain": "{{ domain }}",
4  "job_title": "{{ jobTitle }}"
5}

Click the Response & Test tab inside the SearchContacts API Call. You will need a real Firebase ID token for the authToken field during testing — you can get a short-lived one from the Firebase Auth emulator or from FirebaseAuth.instance.currentUser?.getIdToken() called in a Flutter debug build. Enter a test company domain (for example acme.com) and a job title (CEO) in the Variables section. Click Send Test Request. If the proxy is working and your Seamless.AI account has API access, you will see a JSON response with contact records. The structure varies by account but commonly includes fields like: { "contacts": [ { "first_name": "Jane", "last_name": "Doe", "email": "jane@acme.com", "phone": "+1-555-0100", "title": "CEO", "linkedin_url": "https://linkedin.com/in/janedoe" } ] } Click Generate JSON Paths from Response. For a contacts array, the JSON paths will be things like $.contacts[0].email, $.contacts[0].phone, $.contacts (for the full array). Name the array path contactsList and type it as a list — you can use this in a Dynamic List in FlutterFlow. If the test returns 401, the Firebase ID token is missing or the proxy is not verifying correctly. If it returns a proxy-level 500, check Cloud Function logs in the Firebase Console for the actual Seamless.AI error. If Seamless.AI returns 403, your account may not have API access enabled yet.

With the API Call tested and JSON paths generated, build your lead enrichment screen. Add a Column containing a TextField for the company domain, a second TextField for job title filter, a Search button, and a ListView below for results. Create a Page State variable called contacts (type List of your custom contact Data Type) and another called isLoading (Boolean). Set the ListView's source to the contacts Page State variable and map each item's fields to Text widgets in the list tile. For the Search button's Action Flow: 1. Update Page State: set isLoading to true. 2. Run a Custom Action to fetch the Firebase ID token and store it in a Page State variable authToken. 3. Backend/API Call: SearchContacts with domain = TextField value, jobTitle = job-title TextField value, authToken = authToken Page State. 4. On Success: Update Page State to set contacts to the returned contactsList JSON path result, then set isLoading to false. 5. On Error: show a Snack Bar with the error, reset isLoading. Crucially, add a Firestore write step in the On Success branch: after setting the contacts Page State, also write the results to a Firestore document keyed by the queried domain. On the next load of the same domain, check Firestore first and only call the API if no cached result exists. This prevents re-querying the credit-metered Seamless.AI endpoint every time a user views the same company's contacts. Seamless.AI charges credits per enrichment query — redundant queries on the same contact drain your monthly allowance quickly.

Before publishing a FlutterFlow app that stores and displays contact PII from Seamless.AI, consider your legal obligations. Seamless.AI's terms of service define permitted use cases — typically B2B sales prospecting. Storing personal emails and phone numbers in Firestore requires appropriate Firestore Security Rules so that only the individual rep who created the lead (or their team admin) can read the data. A simple rule might require Firebase Auth and check that the requester's UID matches the creator UID on the document. For error handling in the Action Flow, add branches for these common scenarios: • 401 from the proxy: the Firebase ID token is expired or missing — trigger a re-authentication flow. • 403 from Seamless.AI: API access may be revoked or the endpoint is not permitted on your plan — show a support contact message. • 429 rate limit: you have exceeded Seamless.AI's per-minute or daily request limit — show a try again later message and do not retry automatically. • 500 from the proxy: check Cloud Function logs and surface a generic error to the user. For web builds, confirm your Cloud Function sends the correct CORS headers (Access-Control-Allow-Origin: *). Native iOS and Android builds do not enforce CORS, but the proxy is still required to protect the API key. Test on a real device before submitting to the App Store or Play Store — especially if you are using any custom Dart actions to get the Firebase ID token, since those run on device rather than in FlutterFlow's web preview. If you want help with the proxy setup, the Firestore security rules, or the custom ID-token action, RapidDev builds FlutterFlow integrations like this regularly — book a free scoping call at rapidevelopers.com/contact.