Executive staff · VP Engineering and VP Product

Target June 30 for API v1 sunset

Recommend a Q2 target to accommodate contractual notice and the largest partner’s migration constraint.

Will the VPs approve June 30, 2027 as the target before notice goes out, with shutdown conditional on partner readiness?

Assumes October 2026 notice and calendar Q2 2027. Six months ends in April 2027.

Customer obligations should govern the sunset decision

214 integrations still use v1.

37 enterprise integrations represent $1.9M ARR.

First
Honor contractual notice.
Second
Protect migration continuity.
Third
Recover engineering capacity.

This order puts customer obligations ahead of savings from an earlier shutdown.

Falling usage still requires dedicated engineering and support

API v1 share of API calls declined from 31% in January to 18% at the October syncJanuary31% of API callsOctober sync18% of API calls

Maintaining v1 consumes about one engineer full time. Both security patches last quarter were v1 only.

Support handles about 90 v1 tickets monthly, mostly migration questions.

June best accommodates notice and the partner constraint

Criterion3 months6 monthsEnd of Q2
Target¹Jan 2027Apr 2027Jun 30, 2027
Notice²Too shortMeets minimumExceeds minimum
Largest partnerToo earlyToo earlyEarliest stated window³
Upkeep effort⁴≈3 engineer-months≈6 engineer-months≈8 engineer-months

¹ Assumes October 2026 notice. ² Six enterprise contracts require six months. ³ Completion by June is not assured. ⁴ Assumes current staffing through sunset.

Notice starts the clock, while readiness determines shutdown

With October notice, the six-month minimum ends in April and the largest partner cannot finish before the end of JuneSix-month contractual noticeContinue v1OctoberAprilJune 30Illustrative timing from October 2026 notice

Send notice before counting six months. The largest partner cannot finish before Q2 ends because of its release freeze. Require evidence of readiness before disabling v1.

Migration work is short, but scheduling remains the risk

Migrated customers report 2–5 developer days.

This measures implementation effort, not elapsed scheduling time.

Available
The guide is complete. v2 has parity except bulk webhooks.
Dependency
Bulk webhooks ship five weeks after October 14.
Risk response
Track affected integrations through webhook release and partner scheduling.

June costs more capacity and prolongs security exposure

Estimated upkeep at current staffing is three, six or approximately eight engineer-months3 months≈3 engineer-months6 months≈6End of Q2≈8

June adds about two engineer-months versus six months, or five versus three. Faster retirement is Platform’s strongest case. Keep patching through migration. Revisit earlier retirement only with contractual clearance and partner readiness.

Will both VPs approve June 30 before notice goes out?

Decision
Approve the target and continued upkeep at roughly one engineer.
Shutdown gate
Require elapsed notice and partner readiness. Escalate failures to both VPs.
Reversibility
The target can move before shutdown. Reversal after shutdown risks customer disruption.
Accountability
Who will own migration readiness across teams so the shutdown gate has one accountable lead?

This decision adds no staffing commitment. Source: Platform sync, Oct 14.