Skip to main content
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

FMG APIs

Contacts, groups, and marketing content for an FMG subscriber. Start with the OAuth guide, then the API Reference.

MRC APIs

Compliance-grade texting through MyRepChat — vendor-triggered outbound SMS, consent, and delivery status. Start with the OAuth guide.

​
How integration works

1

FMG provisions your app

Per product, FMG issues a Client ID, Client Secret, and API base URL — first for sandbox, then for production.
2

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.
3

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.*).
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.