Skip to main content
Coming from Proxycurl (or a Proxycurl-style API)? The resource layout will feel familiar — that’s deliberate. Here’s the whole migration.

Auth

Endpoint mapping

Request shape

Proxycurl is GET-with-query-params; Up2Data is POST-with-JSON-body:

Response shape

  • Payload is under data (Proxycurl returns fields at the top level).
  • Field names are close but not identical — e.g. experiences[]positions[], city/state/countrylocation.{city,region,country}. Full glossary on each endpoint page.
  • Every response includes meta.creditsUsed / creditsRemaining — no separate balance endpoint calls needed (though GET /v1/account exists and is free).

Billing differences that matter

Migration checklist

1

Swap auth header and base URL

Authorization: BearerX-API-Key, nubela.co/proxycurlapi.up2data.ai.
2

Convert GETs to POSTs

Query params become JSON body fields.
3

Remap response fields

Read from data.*; rename per the field glossaries.
4

Delete your cache-freshness logic

use_cache=if-recent workarounds are obsolete — everything is live.
5

Replace polling loops with Signals

If you re-scrape profiles on a schedule to detect changes, a Signal does it server-side and webhooks you the diff.