Is Funding Signals API down?
Current status, daily uptime history and troubleshooting for the Funding Signals API (Business).
Possibly: Funding Signals's last check failed
Our latest daily check of Funding Signals (Oct 24, 2026, 12:25 UTC) failed: its TLS certificate chain is incomplete. One failure can be a blip; the live check below tells you whether it's still failing.
Checking Funding Signals now…
Sending a request from our server.
Funding Signals API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- Its TLS certificate chain is incomplete
- Last up
- Not seen up yet
We check Funding Signals's listed URL (https://fundingsignals.net/docs) once a day. History started when Funding Signals was first checked, so new entries show fewer than 30 days.
Funding Signals API not working for you?
- Funding Signals needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- Funding Signals doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Business APIs up at their last check
- 1
Legal Sandbox Georgia API
Online · 563 msFind verified legal specialists in Georgia from natural-language queries.
- No API key needed
- Returns JSON at its URL
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
Verif Entreprise FR API
Online · 699 msFrench company checks by SIREN: status, insolvency (BODACC), VAT (VIES); free preview.
- No API key needed
- Returns JSON at its URL
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
KontragentPro API
Online · 719 msRussian company data from state registers by INN or OGRN: profile, finances, timeline.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
TradeDataHub API
Online · 1008 msU.S. contractor datasets with a free discovery API for coverage, pricing and masked previews.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Tomba email finder API
Online · 532 msEmail Finder for B2B sales and email marketing and email verifier.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS
Compare all Funding Signals alternatives · APIs down right now
Funding Signals API status FAQ
Is Funding Signals API down right now?
Our latest daily check of Funding Signals (Oct 24, 2026, 12:25 UTC) failed: its TLS certificate chain is incomplete. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether Funding Signals is responding at this moment.
How do you check whether Funding Signals API is up?
Once a day our checker requests Funding Signals's listed URL (https://fundingsignals.net/docs) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if Funding Signals API is down?
Free Business APIs that were up at their last check include Legal Sandbox Georgia, Verif Entreprise FR, KontragentPro. See the full list of Funding Signals alternatives for a comparison.
Why does Funding Signals API work for others but not for me?
Funding Signals needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. Funding Signals doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.