Integration overview

A concise map of the public GoldShore surfaces. Start here, then use the existing API, authentication, webhook, and MCP pages when you know which path you need.

Private by design: client secrets, API tokens, signing secrets, private keys, Access service-token values, internal IDs, SAML metadata, and exact operator callbacks are not published here. Request access through the protected operator workspace.

Start with the overview

Choose the public surface that matches your goal. Production access, credentials, and operator configuration stay behind the authenticated admin workspace.

Public sitehttps://goldshore.ai

Developer hubhttps://goldshore.ai/developer/

API referencehttps://goldshore.ai/developer/api/

Request accesshttps://goldshore.ai/contact/?intent=integration-access

Operator workspacehttps://admin.goldshore.ai/app/dashboard

Public application URLs

Use these public origins for documentation, health checks, and approved client setup. Private tools and administrative operations require an approved identity.

API originhttps://api.goldshore.ai

API healthhttps://api.goldshore.ai/health

API readinesshttps://api.goldshore.ai/ready

Documentationhttps://goldshore.ai/developer/docs/

Webhook concepts

Providers receive event-specific callback URLs from the API. Configure only the callback required by the integration and use its matching signature secret in the provider console.

GitHub eventshttps://api.goldshore.ai/webhooks/github/{event}

Stripe eventshttps://api.goldshore.ai/webhooks/stripe

Google eventshttps://api.goldshore.ai/webhooks/google

Cloudflare eventshttps://api.goldshore.ai/webhooks/cloudflare

Next step

Need a protected integration?

Use the existing authentication and MCP guidance, or request an approved operator path. No new page is required to begin.

Review authentication Review MCP access Request access