Tomba email finder vs Trello

Tomba's Email Finder API discovers and verifies professional email addresses from a company domain or a person's name, and doubles as a B2B prospecting and lead-enrichment tool via linked domain-search and phone-finder endpoints. It authenticates with a paired `X-Tomba-Key`/`X-Tomba-Secret` header set rather than a single token, and a live Origin-header probe confirms it explicitly supports browser CORS, echoing the request Origin with credentials enabled on both a GET and an OPTIONS preflight.

Trello turns Kanban-style boards, lists, and cards into a scriptable project-management primitive, letting integrations create, move, and archive cards or attach webhooks that fire on board activity. Every account gets a free API key, and requests carry that key plus a short-lived member token as query parameters rather than a full OAuth redirect — a live unauthenticated call to `/1/members/me` confirms this by returning 401 'invalid key' rather than a bearer-token challenge (auth corrected OAuth -> API Key; OAuth1.0a exists only as an alternate authorization flow for third-party apps). Trello's Power-Ups marketplace and countless third-party integrations run on this same public API, available on every pricing tier including the free plan, and CORS is wide open — both the GET and an OPTIONS preflight echo `access-control-allow-origin: *`, resolving the stored 'unknown' value to yes.