The Form OIP ORDR Files Dataset is a collection of EDGAR submissions of form type OIP ORDR — "Order Instituting Proceedings / Order" instruments issued by the U.S. Securities and Exchange Commission. Each record is one filing-level folder, identified by the EDGAR accession number, containing a structured metadata.json describing the submission envelope plus the underlying typeset order PDFs. The substantive author of every order is the Commission itself, acting either as a body of five Commissioners or, more commonly, through one of its Divisions under delegated authority and signed out by the Secretary of the Commission. The form type covers two related document genres in one dataset: enforcement-style orders that simultaneously institute administrative proceedings and impose findings, bars, civil penalties, disgorgement, or cease-and-desist obligations; and delegated-authority orders disposing of applications for exemptive relief, substitution orders under Section 26(c) of the Investment Company Act, and other administrative grants. Records date from February 2009, when the EDGAR form-type taxonomy began routinely capturing these orders as standalone machine-addressable submissions, through the present, and are distributed as monthly ZIP containers along the URL path form-oip-ordr-files/<YYYY>/<YYYY-MM>.zip.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset contains every EDGAR submission carrying the OIP ORDR form type, packaged for bulk retrieval. Each record corresponds to one Commission order — either an enforcement-style "Order Instituting Administrative Proceedings, Making Findings, And Imposing Remedial Sanctions" entered against named respondents, or a delegated-authority order granting exemptive, substitution, or interpretive relief to a named applicant. Both genres share an identical legal-document architecture: a Commission caption, a statutory recitation, a narrative recital of facts or procedural posture, a findings block, an ordering clause, and the Secretary's signature.
Physically, the dataset is delivered as monthly ZIP archives. Each archive contains a single year-month root directory whose only children are accession-number folders. Inside each folder sits exactly one metadata.json describing the EDGAR submission, plus one or more typeset order PDFs named filename<sequence>.pdf where <sequence> corresponds to the sequence value in the metadata's documentFormatFiles array. Image files from the original EDGAR submission are excluded; the typeset order PDF — which carries the substantive content — is always present. OIP ORDR filings have been disseminated through EDGAR as typeset PDFs wrapped in the standard EDGAR SGML submission envelope; the form has not transitioned through ASCII, HTML, or XBRL formats, and the order PDFs carry a selectable text layer rather than requiring OCR.
Three identifiers operate at distinct layers within each record and should not be conflated: the EDGAR accession number locates the filing within EDGAR and within this dataset (the dashed form appears as accessionNo inside metadata.json; the un-dashed form is the folder name); the SEC file number tracks the underlying docket (for example the 812-xxxxx series for investment-company applications, the 3-xxxxx series for enforcement matters); and the SEC release number printed on the face of the PDF is the citable identifier for the order in Commission publications and subsequent references.
A record is layered as follows. The outer ZIP archive contains a single year-month root directory whose only children are accession-number folders. Each accession folder holds two kinds of artifacts: exactly one metadata.json describing the submission, and one or more original EDGAR documents named filename<sequence>.pdf where <sequence> corresponds to the sequence value in the metadata's documentFormatFiles array. Image files from the original EDGAR submission are excluded from the dataset; the typeset order PDF — which carries the substantive content — is always present.
metadata.json objectmetadata.json is a flat JSON object describing the EDGAR submission envelope. Its content-bearing fields are:
formType — fixed at "OIP ORDR".accessionNo — the dashed-form EDGAR accession number (for example "9999999997-15-002520"), the canonical filing identifier and the un-dashed root of the containing folder name.filedAt — an ISO-8601 timestamp with timezone offset recording when the order was filed into EDGAR (for example "2015-03-09T10:36:18-04:00").description — a short human-readable label, typically of the form "Form OIP ORDR - <subtype>" where the subtype distinguishes 1934 Act, 1940 Act, or Advisers Act orders (e.g. "40-OIP Order").linkToFilingDetails — absolute URL to the primary order PDF on www.sec.gov.linkToTxt — absolute URL to the EDGAR complete submission text file (the SGML-wrapped bundle of all documents in the submission).linkToHtml — absolute URL to the EDGAR filing-index HTML page.linkToXbrl — empty string; OIP ORDR orders are not XBRL-tagged.documentFormatFiles — an array with one element per document in the original EDGAR submission, plus a trailing element for the auto-generated complete submission text file. Each element carries sequence (string such as "1", "2", …, or a blank space for the complete submission text file), size (string-encoded byte count), documentUrl (absolute URL on www.sec.gov), type (the EDGAR document type label, normally "OIP ORDR" for the order itself), and an optional description.dataFiles — array reserved for structured-data documents; empty for this dataset.seriesAndClassesContractsInformation — array reserved for fund series/class metadata; typically empty, but potentially populated where the underlying order involves registered investment company series and classes.entities — an array of party objects describing the filing entities recorded in the EDGAR header. Each entity carries companyName with a role label in parentheses (e.g. "PACIFIC LIFE INSURANCE CO (Filer)"), the zero-padded 10-digit cik, the SEC fileNo referencing the underlying application or proceeding docket (for example "812-14359"), the EDGAR filmNo, the governing act code ("33", "34", "40" for the Investment Company Act, etc.), type matching the form type, plus issuer attributes carried over from the EDGAR header such as irsNo, stateOfIncorporation, and fiscalYearEnd.id — a stable 32-character hexadecimal hash uniquely identifying the record within the dataset.The entities array is the dataset's structured surface for cross-referencing respondents or applicants. For delegated-authority orders the entity is typically the applicant; for enforcement-style orders it is the respondent named in the caption. The fileNo field tracks the docket itself and is independent of both the EDGAR accession number and the release number printed on the order.
Each filename<sequence>.pdf is a typeset SEC order. Despite the variety of statutory bases, OIP ORDR orders share a stable internal structure and are generally short (two to a small number of pages). The layout, in order of appearance, is as follows.
Commission caption. The first page opens with the centered Commission caption — three lines reading "UNITED STATES OF AMERICA / BEFORE THE / SECURITIES AND EXCHANGE COMMISSION".
Statutory header and release number. Immediately below the caption sits the statutory header, naming the governing Act (Securities Exchange Act of 1934, Investment Company Act of 1940, Investment Advisers Act of 1940, or Securities Act of 1933) together with the substantive release number under that Act and the issuance date — for example INVESTMENT COMPANY ACT OF 1940 / Release No. 31499 / March 6, 2015. Enforcement-style orders typically list multiple release numbers in parallel (one per Act invoked) and may add the Administrative Proceeding file number.
"In the Matter of" docket block. A horizontal rule introduces the docket caption. The left column lists each respondent or applicant on its own line, followed by the principal place of business address, and closes with the SEC file number in parentheses. Each line is terminated by a colon on the right — a vestige of the two-column docket layout. A second horizontal rule closes the block.
Order title. The order's substantive title is centered next, naming the specific statutory section under which the order operates — for example ORDER INSTITUTING ADMINISTRATIVE PROCEEDINGS PURSUANT TO SECTION 15(b) OF THE SECURITIES EXCHANGE ACT OF 1934, MAKING FINDINGS, AND IMPOSING REMEDIAL SANCTIONS, or, in the exemptive-relief genre, ORDER UNDER SECTION 26(c) OF THE INVESTMENT COMPANY ACT OF 1940. Compound titles such as MAKING FINDINGS, AND IMPOSING REMEDIAL SANCTIONS AND A CEASE-AND-DESIST ORDER are common where multiple Acts are invoked.
Recitals and findings. The body is organized as numbered Roman-numeral sections (I, II, III, …) or as labeled paragraphs, depending on the genre.
Ordering clause. A transition word — typically Accordingly, or IV. — introduces the operative order. The ordering clause begins IT IS HEREBY ORDERED (enforcement genre) or IT IS ORDERED (delegated-authority genre), recites the statutory authority, and enumerates the sanctions, undertakings, or grants imposed. Enforcement orders commonly enumerate cease-and-desist requirements, censures, bars from association, civil penalties with payment terms and Fair Fund or Treasury allocation instructions, and undertakings such as compliance certifications. Delegated-authority orders typically state that the requested action is approved, "effective immediately, subject to the conditions contained in the application, as amended."
Delegation recital and signature. Where the order is issued under delegated authority, a recital identifies the delegating Division — For the Commission, by the Division of Investment Management, under delegated authority, or analogous language for the Division of Enforcement, the Division of Trading and Markets, or the Division of Corporation Finance. The signature block names the Secretary of the Commission with typed name and title; the PDF is a typeset filing rather than a wet-ink scan.
Footnotes and pagination. Page-foot footnotes frequently carry scope-limiting language (for example, identifying which respondents specific findings apply to in multi-respondent matters); they are part of the operative text and should be preserved in extraction. Pages are numbered at the foot.
A record includes the entire textual content of the order PDF (Commission caption, statutory header and release numbers, docket block, order title, factual recitals and findings, ordering clauses, delegation recital, signature block, footnotes, and page numbers), all non-image documents associated with the EDGAR submission, and the structured metadata.json describing the submission envelope and the parties.
Image files from the original EDGAR submission are excluded from the dataset. Because the substantive narrative of the order is invariably carried by the typeset PDF, the image exclusion is rarely material for content extraction; what is excluded would typically be Commission seals, signature graphics, or rasterized exhibits. The dataset does not bundle the Commission's prior notice release (cited inside exemptive-relief orders by its own Investment Company Act release number), the underlying application giving rise to a delegated-authority order, or the complaint or investigative record giving rise to an enforcement order — only the Commission's order document itself. Related orders against affiliated respondents or co-applicants are filed as separate accession numbers and therefore appear as separate records.
Several nuances matter for reading and extracting records.
entities array in metadata.json reflects the EDGAR filer registration and may not enumerate every named party that appears inside the order — particularly in multi-respondent enforcement matters where some respondents are not separately registered with EDGAR.linkToTxt field continues to expose the SGML-wrapped complete submission text file, whose payload is the same PDF in base64-encoded form.The substantive issuer of every OIP ORDR document is the U.S. Securities and Exchange Commission, acting either as a body of five Commissioners or, far more commonly, through one of its Divisions under delegated authority and signed out by the Secretary of the Commission. The order is the Commission's own legal instrument; no private party drafts or signs it.
Inside metadata.json, however, the EDGAR entities array does not always identify the Commission as filer. Two filing patterns appear:
9999999997 series). The respondents named in the caption (broker-dealers, advisers, transfer agents, issuers, associated persons, accountants under Rule 102(e), etc.) are subjects of the order, not filers, and frequently do not appear in the entities array at all.(Filer) in entities (for example, an investment company or insurer applying under Section 26(c) of the Investment Company Act). The Commission still issues and signs the order; the applicant is the registrant whose EDGAR identity carries the submission.In both cases the operative author is the SEC. The entities array reflects the EDGAR submission envelope, not the legal authorship of the order.
The persons or entities named inside an OIP ORDR fall into two populations matching the two genres above.
Respondents (enforcement genre) may include any party within the Commission's administrative jurisdiction: registered broker-dealers and their associated persons; registered investment advisers and their supervised persons; registered investment companies and their officers, directors, and affiliated persons; municipal securities dealers, municipal advisors, transfer agents, and clearing agencies; public accountants and accounting firms subject to Rule 102(e); Section 12 / Section 15(d) reporting issuers facing registration revocation or suspension; officers and directors subject to bars; and other persons previously enjoined or criminally convicted in securities matters.
Applicants (delegated-authority genre) are typically registered investment companies, insurance company separate accounts, investment advisers, or other regulated entities seeking exemptive, substitution, or interpretive relief under the 1940 Acts or the 1933 / 1934 Acts.
There is no periodic schedule. Each record is event-driven and dated to the day the Commission issues and disseminates the order. The triggering events fall into a small number of procedural postures:
For the enforcement postures, the trigger is the Commission's adjudicatory vote (or delegated action). For the delegated-authority posture, the trigger is the lapse of the notice period coupled with the Division's decision to enter the final order.
The order text recites the specific statutory section(s) under which it is issued. Frequently invoked authorities include:
The Commission's Rules of Practice (17 C.F.R. Part 201) govern procedure, including Rule 200 (contents of an OIP), Rule 155 (default), and Rule 240 (settlements).
Records arrive ad hoc on the date the Commission issues the order. Volume reflects the Division of Enforcement's recommendation pipeline, the negotiation of settlements, the Commission's voting calendar, the maturation of predicate events for follow-on bars, and the application docket for delegated-authority orders. The dataset's earliest records date to February 2009, when the EDGAR form-type taxonomy began routinely capturing these orders as standalone machine-addressable submissions; the underlying statutory authority and order-issuing practice are decades older.
(Filer) role within entities is a reliable cue that the order is the delegated-authority genre rather than an enforcement order.OIP filings (institutions of proceedings that will be followed by a contested hearing) and standalone ORDR filings (subsequent orders entered after a proceeding has matured). The combined OIP ORDR form is reserved for instruments where institution and disposition occur in a single document — typically settlements, defaults, summary procedures, or delegated-authority grants.Form OIP ORDR sits inside a small family of EDGAR form types used by the Commission itself to disseminate its own orders, plus a wider perimeter of enforcement-adjacent releases that live outside EDGAR. The closest neighbors differ along three axes: whether the order only institutes a proceeding or also resolves it, whether the underlying matter is enforcement or delegated-authority relief, and whether the artifact is an EDGAR-filed instrument at all. The comparisons below are organized along those axes.
A standalone OIP institutes an administrative or cease-and-desist proceeding against named respondents, sets the charges, and demands an answer, but does not make findings or impose sanctions in the same document. OIP ORDR is the merged form: institution and disposition arrive together. Use OIP to track newly opened, still-contested matters that will be litigated before an ALJ or the Commission; use OIP ORDR for matters resolved in a single instrument — almost always settlements, defaults, Section 12(j) revocations, or summary dispositions.
A standalone ORDR is any Commission order not paired with the institution of a new proceeding: orders entered after a contested OIP has matured, orders modifying or vacating prior orders, orders ruling on motions, or orders denying applications. Overlap with OIP ORDR is structural — both are Commission-signed orders — but ORDR is downstream or self-contained, whereas OIP ORDR is the combined opener-and-resolver. Subsequent modifications, waivers, or post-settlement clarifications of an OIP ORDR matter are filed as ORDR, not OIP ORDR.
CT ORDER (consolidated tape) filings are Commission orders entered under the national market system framework — approving, modifying, or extending plans for consolidated market data, NMS plan amendments, and related infrastructure dispositions. They share the "order" designation with OIP ORDR but name plan participants and SROs rather than respondents or applicants, and they carry no findings of violation. They are not a proxy for enforcement activity.
A meaningful share of OIP ORDR filings are Section 12(j) registration revocations against delinquent Exchange Act reporting issuers. Related Section 12(j) artifacts can also surface under adjacent form-type tags depending on procedural posture (e.g., suspensions versus revocations, contested versus default). Where the question is specifically "what issuer registrations did the Commission revoke or suspend, and against which CIKs," OIP ORDR captures the combined institution-and-revocation orders, while standalone OIP filings capture the contested institutions that have not yet resolved.
25-NSE is filed by national securities exchanges, not by the Commission, to remove a security from listing and registration on that exchange. It can appear downstream of an OIP ORDR — for example, after the Commission revokes an issuer's Section 12 registration — but the filer, mechanism, and legal effect are different: 25-NSE is an exchange-initiated administrative removal, OIP ORDR is a Commission order acting on persons or issuers. They are complements in a delisting timeline, not substitutes.
Commission trading suspension orders temporarily halt trading in a specific security (typically ten business days) under Section 12(k) of the Exchange Act, usually because of questions about the adequacy of public information. They are disseminated by the Commission through separate channels and form-type conventions and act on the security, not on persons, with no findings and no enumerated respondents. OIP ORDR acts on named respondents or applicants with formal findings and durable consequences (bars, revocations, penalties, granted relief). Many enforcement arcs begin with a trading suspension against a security and later produce an OIP or OIP ORDR against the persons responsible — but the two are not interchangeable.
Delegated-authority OIP ORDRs that grant exemptive or substitution relief under the Investment Company Act sit at the end of an application pipeline. The application itself is filed by the applicant under forms such as 40-APP (and amendments); the Commission then publishes a notice of the application, and — if no hearing is requested — issues the final order, which is what surfaces as an OIP ORDR. To trace the full sequence of an exemptive matter, the application forms carry the applicant's request and supporting representations, while OIP ORDR carries only the Commission's final disposition.
Inside the OIP ORDR form type itself, two genres coexist: enforcement-style orders (Section 15(b) of the Securities Exchange Act of 1934, 21C, 203(f), 9(b), Rule 102(e), and similar) and delegated-authority orders disposing of applications (Section 26(c) substitutions, Section 6(c) and Section 17(b) exemptions). Both share document architecture but answer different questions. Filtering by description (e.g., "40-OIP Order") and by whether entities lists an applicant in (Filer) role versus a generic SEC filer CIK is the most reliable structural separator.
SEC Litigation Releases summarize civil actions the Commission has filed in federal district court. They are press-style announcements, not operative legal instruments, and are not EDGAR filings. A single enforcement matter can produce both a Litigation Release (covering the parallel civil case) and an OIP ORDR (covering the administrative resolution against a regulated person); joining the two gives the full picture. Use Litigation Releases for the civil-court track; use OIP ORDR for the in-house administrative track.
AAERs are a curated, editorially indexed subset of Commission enforcement actions involving accountants, auditors, and financial-reporting violations. They are published as releases, not EDGAR submissions. Many AAER-tagged matters also appear as OIP ORDR filings on EDGAR when the administrative resolution is recorded. Accounting and Auditing Enforcement Releases provide a topic filter; OIP ORDR is a form-type population. Researchers focused on accounting misconduct typically start at AAER and pull the corresponding OIP ORDR for the underlying order text.
The Commission assigns release numbers within statute-specific series (e.g., Investment Company Act Release No. 31499) that index its orders editorially. These release numbers are printed inside OIP ORDR PDFs and are the citable identifiers in Commission publications. The release-number system and the EDGAR OIP ORDR dataset are two views of the same orders — an editorial index layer and a filed-document layer — not different orders. Identifier hygiene matters: accession number (EDGAR), file number (docket), and release number (citable) should be treated as distinct keys.
OIP ORDR is distinguished by one document doing two procedural jobs: it both opens and disposes of an administrative matter, with the Commission as the issuing author and the Secretary as signer. It covers two substantive genres — enforcement settlements/defaults/12(j) revocations and delegated-authority exemptive grants — that share document architecture but answer different questions.
Use OIP ORDR when the question is: what administrative matters did the Commission both bring and resolve in a single order, against which respondents or applicants, under which statutory authority, and on what terms.
Use something else when the question is:
Form OIP ORDR filings combine an order instituting administrative proceedings with findings and sanctions. The dataset serves a narrow set of enforcement, compliance, and risk functions that each read different parts of the order: the respondent caption, the statutory authority, the factual findings, and the operative bars, suspensions, revocations, penalties, disgorgement, and undertakings.
Defense counsel in the enforcement bar use the corpus as precedent when negotiating Wells responses and settled proceedings for broker-dealers, advisers, associated persons, and delinquent issuers. They benchmark comparable cases on failure-to-supervise, books-and-records, Section 15(b) revocations, and AML matters. Load-bearing fields: statutory authority paragraph, framing of findings, length of associational bars, civil penalty amounts, and undertaking terms used to draft offers of settlement aligned with prior Commission practice.
CCOs, compliance counsel, and supervisory analysts at broker-dealers, RIAs, transfer agents, and municipal securities firms mine the factual findings for control failures, WSP gaps, and supervisory lapses that have drawn enforcement attention, then recalibrate policies and training. They also screen new hires against bar language to avoid onboarding barred individuals. Key fields: caption and respondent identifiers, bar scope, and collateral registration consequences.
Pre-hire screening vendors serving the securities industry use OIP ORDR records to verify candidate-disclosed regulatory actions on Forms U4 and U5. They parse respondent names and aliases, order date, statutory provisions, and the operative sanction language to detect omissions or mischaracterizations in candidate disclosures.
Researchers building or auditing aggregated broker and adviser misconduct datasets use OIP ORDR records as primary source. They link respondents to registration histories and reconcile public disclosure entries against the Commission's order text. Central fields: respondent identifiers, Exchange Act or Advisers Act section invoked, sanction type, and effective dates of bars and suspensions.
Law, finance, accounting, and public-policy researchers code the dataset for empirical work: sanction distribution by respondent type, relative use of Section 15(b), Section 12(j), and Advisers Act Section 203(f), penalty trends, follow-on actions after criminal or civil judgments, and cooperation-credit effects. They extract statutory authority, findings, sanctions schedule, and issuance date for panel and event-study designs; the 2009-onward continuity supports long-horizon work.
Reporters covering enforcement and white-collar matters use OIP ORDR as the authoritative source for what was charged and ordered. They quote findings to describe conduct, cite the sanctions paragraphs for what was imposed, and use the caption to identify firms and individuals. Comparative reporting draws on counts of delinquent-filer revocations and penalty trends across periods.
Diligence teams at private funds, prime brokers, custodians, fund administrators, family offices, and corporate development groups screen sub-advisers, introducing brokers, fund directors, and key principals. OIP ORDR matters more than complaints because it reflects findings, not allegations. Analysts check whether the target or its principals appear in the caption, the statutes invoked, whether bars remain in effect, and whether cease-and-desist or undertaking obligations are still operative.
Vendors of adverse-media, sanctions, and regulatory-action screening tools ingest OIP ORDR filings into structured watchlists. Engineers and data scientists rely on consistent respondent identifiers, accession-level provenance, statutory citations, sanction-type classification, and effective dates to drive entity resolution and ongoing-monitoring alerts in KYC and AML pipelines.
Teams building retrieval-augmented systems for legal research and compliance Q&A use the corpus to ground outputs in Commission language. The standardized caption / authority / findings / sanctions structure supports chunking, citation grounding, and structured extraction. Developers care about the full document text and accession-level metadata for citation.
Experts retained in securities matters cite prior OIP ORDR findings and remedy language to opine on industry standards of conduct, supervisory expectations, and the calibration of disgorgement, loss, and penalty amounts in comparable cases.
Defense lawyers and compliance teams use the dataset to benchmark conduct and remedies; background-check, disclosure, and diligence groups use it to verify individual and entity histories; academics and journalists use it to analyze and report on Commission practice; and regtech and AI builders use it as structured primary-source input. Across all of these, the value comes from the same three features: authoritative respondent identification, explicit statutory grounding, and definitive findings and sanctions issued by the Commission.
The use cases below tie to specific fields in the OIP ORDR record: the entities array and "In the Matter of" docket block for party identification, the statutory header and release numbers for legal grounding, the findings sections for conduct narratives, and the ordering clause for sanctions, bars, and grants.
Enforcement defense teams pull comparable OIP ORDR settlements before drafting an offer of settlement. They filter on the statutory authority cited in the order title (for example, Section 15(b) of the Exchange Act paired with Section 203(f) of the Advisers Act), then extract civil penalty amounts, disgorgement, bar duration, and undertakings from the ordering clause. The output is a precedent table aligning the client's facts with the Commission's prior calibration of remedies.
Broker-dealer and RIA compliance teams, plus diligence analysts at funds and prime brokers, search respondent names from the docket block and entities array against candidate or counterparty lists. They parse the ordering clause for the scope of associational bars (broker, dealer, investment adviser, municipal securities dealer, transfer agent, NRSRO) and any time-bar reentry rights, flagging individuals whose bars remain operative. The output feeds onboarding decisions and ongoing KYC monitoring.
Researchers and data vendors isolate delinquent-issuer revocation orders by filtering OIP ORDR records whose order title invokes Section 12(j) of the Exchange Act. From each order they extract the respondent issuer name, CIK from the entities array, file number, and the operative revocation paragraph, producing a per-issuer registration-status table that can be joined to EDGAR reporting histories and subsequent 25-NSE delistings.
Investment-management lawyers and fund-operations teams separate delegated-authority orders from enforcement orders using the description field (for example, "40-OIP Order") and the Division recital ("by the Division of Investment Management, under delegated authority"). They index orders by the statutory section in the title — Section 26(c) substitutions, Section 6(c) and 17(b) exemptions — and link each to its applicant via the entities array and fileNo (812- series), supporting drafting of new applications that mirror prior granted relief.
Academic researchers code the corpus at scale by extracting filedAt, statutory authority from the header, respondent type from the caption, and sanction tuples (bar type and duration, penalty amount, disgorgement, cease-and-desist) from the ordering clause. The resulting panel supports event studies on Dodd-Frank collateral-bar adoption, penalty inflation, cooperation credit, and the share of matters resolved under Section 15(b) versus Section 203(f) over the 2009-onward window.
LLM developers chunk OIP ORDR PDFs along the stable architectural boundaries (caption, statutory header, "In the Matter of" block, findings, ordering clause, signature) and attach accessionNo, release number, and linkToFilingDetails as citation metadata. Retrieval queries on phrases such as "failure to supervise" or "books and records" return passages with verifiable provenance, anchored to the citable release number rather than a hallucinated paraphrase.
Background-check vendors serving the securities industry match candidate-supplied disclosures against the corpus by joining on respondent name, order date (filedAt), and statutory provision. Discrepancies between the candidate's narrative and the Commission's findings or sanction text are flagged for the hiring firm, with the order PDF served as the source document for adjudication.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-oip-ordr-files.json
This endpoint returns dataset metadata including name, description, last updated timestamp, earliest sample date (February 2009), total records and total size, covered form types (OIP ORDR), container format (ZIP), and file types (PDF, JSON). It also returns the full dataset download URL along with the list of individual container files, each with its size, record count, last updated timestamp, and direct download URL. Poll this endpoint to monitor which containers were modified in the most recent refresh and selectively download only the updated containers. No API key is required to call this endpoint.
1
{
2
"datasetId": "1f13365b-9ae0-6a01-b473-cfaa44784c22",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-oip-ordr-files.zip",
4
"name": "Form OIP ORDR Files Dataset",
5
"updatedAt": "2026-04-15T18:20:21.207Z",
6
"earliestSampleDate": "2009-02-01",
7
"totalRecords": 48,
8
"totalSize": 1490737,
9
"formTypes": ["OIP ORDR"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["PDF", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-oip-ordr-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-04-15T18:20:21.207Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-oip-ordr-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing all OIP ORDR filings from February 2009 to present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-oip-ordr-files/2026/2026-03.zip?token=YOUR_API_KEY
Downloads one individual monthly container archive instead of the full dataset, useful for incremental updates based on the updatedAt timestamps returned by the index API. This endpoint requires an API key.
The Form OIP ORDR Files Dataset covers EDGAR submissions with form type OIP ORDR — "Order Instituting Proceedings / Order" instruments issued by the U.S. Securities and Exchange Commission. The form covers both enforcement-style orders that institute administrative proceedings and impose findings or sanctions in a single document, and delegated-authority orders disposing of applications for exemptive, substitution, or interpretive relief.
One record is a single EDGAR submission of form type OIP ORDR, materialized as a per-filing folder named with the un-dashed EDGAR accession number. Each folder contains exactly one metadata.json describing the submission envelope (form type, filing timestamp, links, entities array, document list) plus one or more typeset order PDFs carrying the substantive Commission caption, statutory header, "In the Matter of" docket block, findings, ordering clause, and Secretary's signature.
The substantive issuer is always the SEC, acting either as the five-member Commission or, more commonly, through one of its Divisions under delegated authority, and signed by the Secretary of the Commission. In EDGAR, enforcement-style orders are submitted under a generic SEC filer CIK (the 9999999997 series), while delegated-authority orders disposing of applications are typically submitted with the applicant listed in (Filer) role inside the entities array.
A standalone OIP only institutes a proceeding and demands an answer; it makes no findings and imposes no sanctions. A standalone ORDR is any Commission order not paired with the institution of a new proceeding, such as post-hearing dispositions or modifications. OIP ORDR is the merged form where institution and disposition arrive in one document — typically used for settlements, defaults, Section 12(j) revocations, summary procedures, and delegated-authority grants.
The dataset's earliest records date to February 2009, when the EDGAR form-type taxonomy began routinely capturing these orders as standalone machine-addressable submissions. Coverage runs through the present, with records arriving ad hoc on the date the Commission issues each order rather than on any periodic schedule.
Records are distributed inside monthly ZIP container archives along the URL path form-oip-ordr-files/<YYYY>/<YYYY-MM>.zip. Within each accession-number folder, the structured submission envelope is provided as metadata.json, and the underlying order documents are typeset PDFs named filename<sequence>.pdf. OIP ORDR filings have never transitioned through ASCII, HTML, or XBRL; the PDFs carry a selectable text layer, so OCR is not required.
Litigation Releases summarize civil actions the Commission has filed in federal district court and are press-style announcements rather than operative legal instruments or EDGAR filings. AAERs are an editorially curated index of enforcement actions involving accountants, auditors, and financial-reporting violations. Both indexes point at matters that often also produce an OIP ORDR for the administrative resolution; OIP ORDR carries the operative order text, while Litigation Releases and AAERs are editorial overlays.