Case studies
Programs, not pilots
Three representative engagements across freight, health benefits, and retail. These are illustrative, clearly fictional accounts of the kind of work Forgepath does; metrics are presented as reported customer results, not independently verified claims.
Freight logistics · Partner & carrier APIs
Northstar Freight Network
A national freight logistics organization modernizing partner and carrier APIs after a decade of growth by acquisition left eleven disconnected integration paths.
Challenge
- Eleven separate integration paths had grown up around acquisitions, each with its own authentication scheme, error format, and informal owner.
- Carrier onboarding took four to six months, dominated by manual credential setup and integration testing coordinated over email.
- Nobody could answer a basic question: which partners call which services, how often, and what breaks if a route changes.
Approach
- Forgepath ran a four-week discovery to inventory every carrier-facing interface, mapping owners, consumers, protocols, and criticality.
- We standardized the carrier-facing contract set on a single design system: consistent auth, pagination, error models, and versioning headers.
- A governed gateway replaced the bespoke paths progressively, with each carrier migrated behind reversible adapters and dual-running windows.
Implementation
- Partner developer portal launched with sandbox environments, self-serve credential issuance, and generated SDKs for Java, .NET, and Python.
- Per-partner rate limits and deprecation windows enforced at the gateway, with policy changes recorded for audit.
- Consumer-level dashboards gave both Northstar and its carriers shared visibility into latency, error budgets, and release impact.
Representative outcomes
Weeks, not months
carrier onboarding time, down from four to six months (reported customer result)
11 → 1
integration paths consolidated behind a single governed gateway
100%
of carrier-facing endpoints documented and owned within two quarters (reported customer result)
Outcomes reported by Northstar Freight Network following the engagement; not independently verified.
“For the first time we could answer the question every carrier asks — “what happens to my integration when you change a lane?” — with evidence instead of a conference call.”
Health benefits · Governed API access & audit visibility
Cedar & Vale Health Plans
A health benefits organization improving governed API access and audit visibility across broker, provider, and internal application channels.
Challenge
- Broker and provider applications accessed member-facing data through inconsistent OAuth patterns, several with over-broad scopes granted years earlier.
- Audit preparation meant manually reconstructing access decisions from scattered logs — a multi-week effort before every review cycle.
- Retiring legacy endpoints stalled because the organization could not identify all consumers with confidence.
Approach
- We modeled a least-privilege policy framework: scope libraries tied to business purposes, approval workflows with named reviewers, and mandatory expiry on every grant.
- Legacy access was re-papered incrementally — each application migrated to standard scopes behind dual-running adapters, no flag-day cutover.
- Audit evidence was assembled automatically: every access grant, policy change, and approval exported into reviewer-ready records.
Implementation
- Policy enforcement at the gateway: schema validation, scope checks, and rate limits applied consistently across broker, provider, and internal channels.
- Immutable audit trail covering grants, revocations, and policy history, searchable by application, scope, and reviewer.
- Deprecation workflow with consumer impact analysis, letting the platform team announce retirements with a known, notified consumer list.
Representative outcomes
Multi-week → same-day
audit evidence assembly for access reviews (reported customer result)
100%
of application grants on least-privilege scopes with named reviewers and expiry dates
9 legacy endpoints
retired on schedule with all consumers migrated and notified (reported customer result)
Outcomes reported by Cedar & Vale Health Plans following the engagement; not independently verified.
“Our reviewers used to ask us to reconstruct history. Now the history is the product — every decision is recorded where it was made.”
Multi-brand retail · Consolidating commerce integrations
Marlow Commerce Group
A multi-brand retail company consolidating fragmented commerce integrations after each brand had built its own connections to inventory, payments, and fulfillment systems.
Challenge
- Six brands had independently integrated with the same inventory, payment, and fulfillment backends — dozens of near-duplicate connections, each maintained separately.
- A fulfillment outage cascaded differently per brand, and no single team could see the total blast radius in real time.
- Black Friday capacity planning relied on the loudest estimate in the room rather than measured usage patterns.
Approach
- Forgepath mapped the integration mesh across all six brands, identifying duplicated connections and the shared contracts underneath them.
- We consolidated onto a shared commerce API layer with brand-level tenancy: one contract set, per-brand policies, quotas, and observability.
- Migration ran brand by brand through the peak season calendar, with each brand dual-running until its traffic fully shifted.
Implementation
- Shared inventory, pricing, and fulfillment contracts versioned centrally, consumed by all brands through generated SDKs.
- Per-brand rate limits and circuit breakers at the gateway so one brand's traffic spike cannot starve the others.
- Cross-brand dashboards showing dependency health and usage trends, feeding capacity planning with real evidence ahead of peak season.
Representative outcomes
Dozens → 3
contract sets replacing duplicated per-brand connections (reported customer result)
One view
of blast radius during incidents, across all six brands, in real time
Peak season passed
with measured capacity headroom instead of estimates (reported customer result)
Outcomes reported by Marlow Commerce Group following the engagement; not independently verified.
“We stopped maintaining six versions of the same conversation with our own warehouse. That alone paid for the program.”
Next step
See what a program like this looks like for you
Every engagement starts the same way: an honest read of your current API estate and a practical recommendation on where to begin — or whether to begin at all.