Pin an API version with
@crossdev/sdk/2027-01 or from crosspoint.v2027_01 import Crosspoint. Versions 2026-04, 2026-10 (the default) and 2027-01 are available.
Access tokens
Create an organization access token from your dashboard (Settings > Developers) and keep it in an environment variable,CROSSPOINT_ACCESS_TOKEN. Never put it in code you publish.
Crosspoint tokens start with cxp_ (organization tokens start with cxp_oat_). If one ever leaks, revoke it from the same settings page and create a new one.
Webhooks
Store your endpoint’s signing secret inCROSSPOINT_WEBHOOK_SECRET and check every event with the SDK’s webhooks.validateEvent (TypeScript) or validate_event from crosspoint.webhooks (Python). A forged or changed event raises WebhookVerificationError. See webhook delivery for a full example.
Already using the Polar SDK?
Crosspoint’s API is compatible with the open-source Polar SDKs, and our packages are built on them: same methods, same models. If you already use@polar-sh/sdk or polar-sdk, you can keep it. Pass baseUrl: "https://api.crosspoint.finance" (TypeScript) or base_url="https://api.crosspoint.finance" (Python), and don’t use the environment option.
Frameworks
- Next.js, Express, Hono, SvelteKit and the other framework adapters: their Webhooks handlers work with Crosspoint (they only check signatures). Their Checkout and Customer Portal handlers are wired to Polar’s servers and can’t be pointed at Crosspoint yet, so create checkouts and customer portal sessions with the SDK instead.
Testing
Build and test in the sandbox: a separate copy of Crosspoint with test cards and no real money. Create a sandbox access token and setCROSSPOINT_ENVIRONMENT=sandbox; both SDKs then talk to https://sandbox-api.crosspoint.finance.
