# For developers

Integrate with the actual HeyCrust credentials, app identity and event contracts.

## Pick the interface

Shopify history and financial reporting use the connected Partner source. The optional identify hook, browser tracking and backend custom events enrich app usage and contact information. Affiliate install matching has its own signed claim interface. The public affiliate API manages program-related records. MCP exposes the tools permitted by its credential.

## Keep credentials distinct

The workspace credential authenticates identification, backend events and owner MCP access. The browser token identifies browser activity. App-scoped affiliate API credentials carry selected permissions. Affiliate install bridge credentials distinguish production from test receipts. Use each credential only on the interface that accepts it.

## Use the app-specific setup guide

Open Developers in your workspace for configured snippets, or request the setup guide through [MCP](/docs/mcp). The existing recipes cover the Shopify Remix template, Node/Express and Rails/shopify_app. Verify the selected HeyCrust app before adding a snippet.

## Verify without confusing signals

Observe the received channel for the app you integrated, then inspect Shopify source coverage independently. Browser receipt recency describes requests seen by HeyCrust; it does not prove merchant activation or a successful commission attribution.

## References

[API reference](/docs/api) describes the HTTP interfaces. [MCP](/docs/mcp) describes coding-assistant access. [Help](/docs/help) covers invalid identities, missing observations and incomplete sources.