Pull freshly-funded startups into Make, route to Sheets, Slack, HubSpot, Instantly, or any of Make's 1,500+ apps. Works with the free plan.
One Make 'HTTP Make a request' module with URL `https://fundedapi.com/v1/startups`. Bearer auth header. Make auto-parses our JSON into mappable fields for every downstream module.
Our outbound webhooks include HMAC SHA-256 signatures in `X-Fundedapi-Signature`. Point Make's built-in 'Custom webhook' trigger at it, add a signature-check HTTP module if you want belt-and-suspenders.
Our list endpoint returns up to 500 startups per call. Pull 500 rows for one Make operation, then iterate — way more efficient than 1-op-per-record vendors that burn your plan.
100 calls/day is 4 daily polls pulling 500 rows each — plenty for alerting + CRM sync scenarios. Pro tier ($49/mo) for hourly polling.
Use Make's 'Create JSON' module → feed to our `/v1/search/ai` endpoint → get structured filters + results. Great for pairing with OpenAI/Claude modules downstream.
We return real HTTP status codes — 429 on rate limit, 403 on quota, 404 on unknown startup. Make's error-handling router branches cleanly. No custom regex on response bodies.
POST /v1/search/ai
{ "query": "Every morning at 8am, pull Seed AI startups hiring ML engineers, push to HubSpot as new companies, post summary to Slack #funding-alerts" }# Make.com scenario (3 modules):
# 1. SCHEDULE trigger: daily 08:00
# 2. HTTP: Make a request
# URL: https://fundedapi.com/v1/startups?niche=AI&round=Seed&hiring=true&limit=100&since={{formatDate(addDays(now;-1);"YYYY-MM-DD")}}
# Method: GET
# Header: Authorization = Bearer {{YOUR_FUNDED_API_KEY}}
# Parse response: YES (Make auto-parses JSON)
# 3. Iterator → for each {{1.startups[]}}:
# a) HubSpot: Create company
# - Name = {{company.name}}, domain = {{company.website}}
# b) Slack: Post message to #funding-alerts
# - "🔔 {{company.name}} raised {{company.fundingAmount}} Seed. Hiring: {{company.hiringSignal}}"Not yet — we use Make's generic HTTP module, which works identically. Native module is on the roadmap once we have >100 active Make users (nudge us via hello@fundedapi.com if you'd find it useful).
Add `Authorization: Bearer $YOUR_KEY` as a header in the HTTP module. Store the key in Make's 'Connections' (or as a scenario variable) so it's not exposed in exports.
One HTTP call = 1 operation. Our list endpoint returns up to 500 startups per call, so 1 op = 500 enriched rows. If you then iterate, each iteration is 1 op per downstream module action.
Yes. Create a Make 'Custom webhook' trigger, copy the URL, subscribe it via our `/v1/webhooks` endpoint (dashboard or curl). We POST signed JSON whenever a matching event fires. Make starts the scenario on receipt.
Add an HTTP module after the webhook trigger that POSTs `{body, signature}` to a tiny Cloudflare Worker running our `verifyWebhookSignature` function. Or trust Make's IP filter — we publish our outbound IP range at /status.
Yes — POST to `/v1/search/ai` with a natural-language query. Map the response into Make's iterator for structured filter use downstream. Great for chaining with OpenAI/Claude/Mistral modules.
We return X-RateLimit-* headers Make can read via HTTP module's 'Get response headers' option. If you hit 429, our response includes a Retry-After — Make can route to a Sleep module before retry.
Fresh funding rounds + key hiring signals in your inbox every Monday.
Free forever. No card. No tricks.