This repository contains the API specification for an Apigee proxy layer sitting between a FinTech platform's unauthenticated website and the Marketo REST API.
The proxy abstracts Marketo credentials from consuming applications, enforces SSO authentication, manages OAuth 2.0 token lifecycle, transforms inbound form field payloads into Marketo's required schema, and normalizes errors and rate limiting centrally — so no consuming application needs to handle any of that directly.
This proxy was the critical integration layer enabling the "Get Started" lead capture form on the Lending landing page to securely route submissions into Marketo and onward to Salesforce CRM — connecting inbound web activity to marketing automation and sales engagement for the first time.
Technical Depth — Understanding and shaping request/response schemas, field mapping tables, auth flows, error codes, rate limit headers demonstrates the technical fluency to own the full definition of an integration, not just the business requirements around it.
Proxy architecture as a PM decision — The choice to introduce an Apigee proxy rather than calling Marketo directly was a product and architecture decision with meaningful implications: credential abstraction, centralized auth enforcement, and a single field mapping layer that decouples CMS form schema from Marketo's internal schema. The spec documents the rationale for this decision explicitly, not just the implementation.
Security and credential design — The auth section covers two distinct layers: SSO enforcement at the consumer-to-proxy boundary, and OAuth 2.0 Client Credentials management at the proxy-to-Marketo boundary — including transparent token refresh so consuming applications never handle Marketo credentials. This reflects the kind of security-first thinking that matters in regulated FinTech environments.
Field mapping as a product decision — The field mapping table isn't just a translation reference — it surfaces decisions about naming conventions, deduplication key selection (email as the primary lookup field), and how custom Marketo fields map to CMS form schema. These choices have downstream implications for data quality, campaign attribution, and lead deduplication that a PM needs to own.
Scope discipline — The Out of Scope section explicitly excludes Salesforce CRM integration, Marketo campaign configuration, lead scoring, and form versions beyond Lending — keeping the MVP tight and referencing where those concerns live.
| Product | Marketing Automation Integration — Lending Lead Capture |
| Document Type | API Specification |
| Status | Completed |
| Date | Q4 2022 |
| Stack | Apigee · Marketo REST API · Salesforce CRM · AEM |
| Artifact | Description |
|---|---|
| PRD: Enterprise CMS Platform Migration | Platform PRD for the AEM platform this integration was built on |