1. Endpoint & Parameter Mapping Table
You can either use our canonical /v1/* routes or keep your existing Proxycurl path strings during migration.
| Use Case | Legacy Proxycurl Route | B2BProfile API Canonical / Alias | B2BProfile API Cost |
|---|---|---|---|
| Person Profile Lookup | GET / proxycurl/api/v2/linkedin?url=... | GET /v1/profile or GET /api/v2/linkedin | 10 Credits ($0.0004–$0.001) |
| Company Lookup | GET / proxycurl/api/linkedin/company?url=... | GET /v1/company or GET /api/linkedin/company | 10 Credits ($0.0004–$0.001) |
| Employee Listing | GET / proxycurl/api/linkedin/company/employees | GET /v1/people/search or GET /v1/company/employees | 2 Credits / person returned |
| Job Search | GET / proxycurl/api/v2/linkedin/company/job | GET /v1/jobs/search or GET /v1/company/jobs | 2 Credits / job returned |
2. Side-by-Side Code Migration
Swap the base URL and API key environment variable—your Bearer token header continues to work unchanged.
Drop-In `/api/v2/linkedin` Compatibility Call
Call `/api/v2/linkedin` or `/v1/profile` with a full profile URL or username:
curl "https://api.b2bprofileapi.com/api/v2/linkedin?url=https://www.linkedin.com/in/satyanadella" \
-H "Authorization: Bearer b2b_live_your_api_key"Interactive Engineering Workbench · GET /v1/profile
Verify real-time latency, enrichment unit math & JSON schema
Frequently Asked Questions
- Does B2BProfile API support Bearer token authentication like Proxycurl?
- Yes. You can pass either `Authorization: Bearer b2b_live_...` or `x-api-key: b2b_live_...` on all endpoints.