POS AM post-effective amendments
Every POS AM post-effective amendment to a Securities Act registration statement on EDGAR since 1994.
curl -H "Authorization: Bearer $SECFEED_KEY" \ "https://secfeedapi.com/v1/filings?query=formType:%22POS%20AM%22&size=2"
import os, requests
r = requests.get(
"https://secfeedapi.com/v1/filings",
params={'query': 'formType:"POS AM"', 'size': '2'},
headers={"Authorization": f"Bearer {os.environ['SECFEED_KEY']}"},
)
print(r.json())What is POS AM?
POS AM is the EDGAR submission type for a post-effective amendment to a registration statement that is not immediately effective upon filing. Companies use it to update a registration statement that is already effective: refreshing financial statements in a shelf, adding information required by Section 10(a)(3), or deregistering unsold securities when an offering ends.
Many POS AM filings are housekeeping, but a large share are deregistration amendments filed after mergers and going private deals, which makes them a useful signal that a registration statement has been closed out.
Issuers with an effective Securities Act registration statement (S-1, S-3, S-4, S-8, F-1 and others).
Whenever the registration statement must be updated after effectiveness, or when the issuer removes unsold securities from registration.
Filings per year
Every POS AM filing on EDGAR, counted from the SecFeed index. Updated daily.
What is inside
| Section | Contents |
|---|---|
| Facing page | The original registration statement number and the amendment number. |
| Explanatory note | Why the amendment is filed, for example deregistration of unsold securities. |
| Updated prospectus | Revised disclosure or financial statements when the offering continues. |
| Exhibits and signatures | New consents, opinions and signatures. |
Get POS AM data with SecFeed
Search the filings with formType:"POS AM", read any document as text or PDF, and use these APIs for structured data:
Search every SEC EDGAR filing since 1993 with Lucene-style queries over ticker, CIK, form type, filing date, company, SIC and 8-K items.
Text Search APISearch every word of every EDGAR filing and exhibit since 2001. Exact phrases, form type, CIK and date filters, results as JSON.
Document Download APIList every file in an SEC filing and download any document, exhibit, XBRL file or image from the EDGAR archive with one authenticated call.
Latest POS AM filings
| Company | Form | Filed | |
|---|---|---|---|
| NorthStar Earth & Space Enterprises, Inc. | POS AM | 2026-10-13 | EDGAR ↗ |
| Silvia, Inc. | POS AM | 2026-10-09 | EDGAR ↗ |
| Waldencast plc | POS AM | 2026-10-09 | EDGAR ↗ |
| Waldencast plc | POS AM | 2026-10-09 | EDGAR ↗ |
| Waldencast plc | POS AM | 2026-10-09 | EDGAR ↗ |
| Boost Run Inc. | POS AM | 2026-10-08 | EDGAR ↗ |
| BIOLIFE SOLUTIONS INC | POS AM | 2026-10-06 | EDGAR ↗ |
| BIOLIFE SOLUTIONS INC | POS AM | 2026-10-06 | EDGAR ↗ |
Use cases
- Detect deregistrations after mergers
- Track updates to shelf registrations
- Follow the life cycle of a registration statement
Related forms
Every Form S-1 registration statement and amendment since 1994: IPOs, follow on offerings and resale registrations, with offering terms as JSON.
S-3Shelf registrationEvery Form S-3 and automatic shelf S-3ASR since 1994: shelf registrations by seasoned issuers for future debt and equity offerings.
S-8Employee stock plan registrationEvery Form S-8 since 1994: shares registered for employee stock plans, option plans and ESPPs, a direct read on equity compensation dilution.
POSASRAutomatic shelf amendmentEvery POSASR post-effective amendment to an automatic shelf registration statement filed by well-known seasoned issuers since 2005.
FAQ
What is a POS AM filing?
A post-effective amendment to an already effective Securities Act registration statement that does not become effective automatically.
Why do companies file a POS AM after a merger?
To deregister securities that remain unsold under registration statements of the acquired company.
Every POS AM filing, one API call away
500 free calls a month. JSON, CSV, PDF and a Python SDK.