crossbeam-api-guide

Use the Crossbeam REST API with OAuth 2.0 for scheduled programmatic pulls into systems like Snowflake or a CRM. Request the offline_access scope for a refresh token since access tokens expire after 24 hours, and send both the Authorization and Xbeam-Organization headers.

Use the MCP server when an AI agent needs to read and reason over partner data, since it avoids building an OAuth integration. Use the REST API when your own code must pull data into internal systems or write activity to Crossbeam's timeline.

Create a webhook under Data → Integrations in the Crossbeam app, provide an unguessable endpoint URL, test it, then add partner and population filters. Verify each request with the HMAC-SHA256 signature and a 300-second timestamp window, and note webhooks are Enterprise-only.

The most common cause is omitting the Xbeam-Organization header, which tells the API which org's data to return. Get the organization uuid from GET /v0.1/users/me and include it alongside the Authorization: Bearer token header.

No. The Crossbeam MCP Server is in Limited Availability for Supernode and Enterprise customers, with access approved by company domain. Request access through your Crossbeam contact or [email protected].

Use webhooks when you need to know the moment a partner event happens, such as a partner deal opened or closed won. Polling the REST API for events burns Record Export limits, while webhooks push signals to your endpoint in near-real-time.