EOL.WikiEOL.Wiki
← ← Back to all products

API PlatformEnd of Life (EOL) Dates & Support Status

Active
FrameworksLatest Version: 5.0.1Latest Release: Sep 25, 2026

API Platform is a PHP framework for building modern web APIs with Symfony components.

Support summary

API Platform has cycles in security-only maintenance. Production workloads should move toward actively supported releases.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

3

0 lts

Versions

19

Latest Version

5.0.1

Active Support

1

EOL

16

Lifecycle Timeline

Jan 23, 2023As of Sep 27, 2026
5.0Active · Date not announced
4.4Security · Date not announced
4.3Security · Date not announced
4.2EOL · Sep 16, 2026
4.1EOL · Mar 13, 2026
4.0EOL · Sep 18, 2025
3.4EOL · Feb 28, 2025
3.3EOL · Feb 28, 2025
3.2EOL · Sep 18, 2024
3.1EOL · Apr 29, 2024
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.0Sep 16, 2026MaintainedDate not announced5.0.1No
Active
4.4Sep 16, 2026Sep 16, 2026Date not announced4.4.2No
Security
4.3Mar 13, 2026Sep 16, 2026Date not announced4.3.20No
Security
4.2Sep 18, 2025Mar 13, 2026Sep 16, 20264.2.26No
EOL
4.1Feb 28, 2025Sep 18, 2025Mar 13, 20264.1.30No
EOL
4.0Sep 18, 2024Feb 28, 2025Sep 18, 20254.0.22No
EOL
3.4Sep 18, 2024Sep 18, 2024Feb 28, 20253.4.17No
EOL
3.3Apr 29, 2024Sep 18, 2024Feb 28, 20253.3.15No
EOL
3.2Oct 12, 2023Apr 29, 2024Sep 18, 20243.2.26No
EOL
3.1Jan 23, 2023Oct 12, 2023Apr 29, 20243.1.29No
EOL
3.0Sep 15, 2022Jan 23, 2023Oct 12, 20233.0.12No
EOL
2.7Sep 15, 2022Jan 27, 2023Jan 27, 20232.7.18No
EOL
2.6Jan 22, 2021Sep 15, 2022Sep 15, 20222.6.8No
EOL
2.5Sep 30, 2019Jan 22, 2021Sep 15, 20222.5.10No
EOL
2.4Mar 22, 2019Sep 30, 2019Jan 22, 20212.4.7No
EOL
2.3Jul 6, 2018Mar 22, 2019Sep 30, 20192.3.6No
EOL
2.2Feb 16, 2018Jul 6, 2018Mar 22, 20192.2.10No
EOL
2.1Sep 8, 2017Feb 16, 2018Jul 6, 20182.1.6No
EOL
2.0Nov 24, 2016Sep 8, 2017Feb 16, 20182.0.11No
EOL

Data sources

Embed this badge

API Platform end-of-life support status badge

Show API Platform's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![API Platform end-of-life status](https://eol.wiki/badge/api-platform.svg)](https://eol.wiki/api-platform/)

HTML

<a href="https://eol.wiki/api-platform/"><img src="https://eol.wiki/badge/api-platform.svg" alt="API Platform end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of API Platform have reached end of life?
The following API Platform versions have reached end of life and no longer receive security updates: 4.2, 4.1, 4.0, 3.4, 3.3, 3.2, 3.1, 3.0 (and 8 more). It is recommended to upgrade to a supported version.
Is it safe to continue using API Platform 4.2?
API Platform 4.2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of API Platform?
The latest version of API Platform is 5.0.1, released in the 5.0 release cycle.
How many versions of API Platform are currently supported?
API Platform currently has 3 actively supported version(s): 5.0, 4.4, 4.3.
When does API Platform 5.0 reach end of life?
API Platform 5.0 does not have a specific end-of-life date announced yet.
What should I do when API Platform reaches end of life?
When a API Platform version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.