> ## Documentation Index
> Fetch the complete documentation index at: https://connect-oauth.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to FMG Connect

> Build integrations with FMG Connect.

FMG Connect lets third-party applications securely access FMG products on behalf of a subscriber. Each product exposes its own OAuth-protected API surface. Authenticate with OAuth 2.1 (Authorization Code + PKCE), then call that product's APIs with a Bearer access token.

## Products

<Columns cols={2}>
  <Card title="FMG APIs" icon="address-book" href="/fmg/oauth/client-integration">
    Contacts, groups, and marketing content for an FMG subscriber. Start with the **OAuth** guide, then the **API Reference**.
  </Card>

  <Card title="MRC APIs" icon="comment-sms" href="/mrc/oauth/client-integration">
    Compliance-grade texting through MyRepChat — vendor-triggered outbound SMS, consent, and delivery status. Start with the **OAuth** guide.
  </Card>
</Columns>

## How integration works

<Steps>
  <Step title="FMG provisions your app">
    Per product, FMG issues a **Client ID**, **Client Secret**, and **API base URL** — first for **sandbox**, then for **production**.
  </Step>

  <Step title="You provide a redirect URI">
    You give FMG the **redirect URI(s)** your app will use. FMG registers them in its OAuth service (Stytch) as the only callbacks authorization codes may be returned to.
  </Step>

  <Step title="Authenticate, then call APIs">
    Run the OAuth flow to obtain an access token, then call the product's endpoints. Tokens are scoped per product (`fmg.*` vs `mrc.*`).
  </Step>
</Steps>

<Note>
  FMG and MRC are **separate integrations**: each has its own Client ID/Secret, redirect-URI registration, scopes, and consent. A subscriber authorizes each product independently.
</Note>