API Valve Standards: How to Build a Project Requirement Set
API valve standards are not a single interchangeable rulebook. A pipeline ball valve, refinery gate valve, compact forged valve and pressure-relief device may each start from a different API product document, while testing, fire qualification, fugitive emissions, materials and dimensions can be governed elsewhere. The useful procurement task is to build a clause-by-clause requirement register for the actual valve tag, approved edition and purchaser options—not to add an undifferentiated list of API numbers to a datasheet.
Determine which API documents belong in the valve data package
Identify isolation, throttling, non-return, pipeline, wellhead or pressure-relief duty before choosing a product standard. Similar-looking valves can have different governing documents.
Check valve type, nominal size, pressure class, end connection, body construction and intended service against the published scope of the controlled standard.
A product standard may invoke routine tests, but an additional inspection or leakage standard can still be specified. State which document controls if requirements differ.
Many API documents contain selections or supplemental requirements that only apply when ordered. Capture them in the requisition rather than expecting the supplier to guess.
Fire-safe or fugitive-emissions evidence applies to a defined design family. Verify the tested configuration, extension basis and supplied-valve match.
Record editions, addenda, project amendments and precedence before design review. A generic claim of API compliance is not a complete order requirement.
Use each API reference only for the role within its scope
| Requirement route | Common API reference | Procurement use | Evidence to review |
|---|---|---|---|
| Pipeline valve product requirements | API 6D | Use when the valve and application fall within the pipeline-valve scope; identify applicable purchaser options and project supplements. | Approved datasheet, design review, material records, manufacturing and test dossier tied to tag and serial. |
| Bolted-bonnet steel gate valves | API 600 | Define the relevant gate-valve construction together with rating, dimensions, materials and project-specific requirements. | Section drawing, bill of materials, dimensions, pressure-test records and specified qualification evidence. |
| Compact forged gate, globe and check valves | API 602 | Apply only to products and ranges inside the document scope; confirm construction, ends and pressure-class route. | Approved drawing, material traceability, heat treatment, NDE where specified, assembly and pressure tests. |
| Butterfly valve product requirements | API 609 | State category, seat concept, end style, pressure class and any dimensional or test references used by the project. | Design identification, face-to-face and flange interface review, seat/shaft evidence and test report. |
| Valve inspection and pressure testing | API 598 | Define routine shell, closure and other applicable tests without treating the document as the product design standard. | Approved procedure, calibrated instruments, valve identification, actual results, failures and retest history. |
| Special design qualification | API 607, API 6FA or API 641 as applicable | Select by product applicability and project need; fire and emissions qualifications answer different risk questions. | Complete report, tested specimen details, laboratory or witness information, results and documented coverage statement. |
Six controls that make an API reference auditable
Explain why the chosen document applies to this valve type and service.
List the contract edition and any accepted project amendments.
Convert purchaser choices into explicit datasheet or requisition entries.
Coordinate pressure rating, face-to-face, flanges, welding ends and actuator connections.
Define calculations, drawings, procedures, certificates, test reports and qualification records.
Record conflicts and exceptions before manufacture instead of silently selecting the easier clause.
Claims and shortcuts this page does not support
API monogram and API design language are different claims
A manufacturer, facility, product or quality-system approval must never be implied solely because a valve is designed to an API document.
A fire-test report is not a blanket family certificate
Coverage depends on the standard, tested construction and permitted extension. Compare seats, packing, joints, materials, size and class.
The official publication controls
Summaries, old catalog tables and copied clauses can be incomplete. Verify the current project-approved edition through API and licensed controlled documents.
From requirement to auditable evidence
Information and records to define
How this resource should be used
Engineering and procurement guidance for buyers who need to identify the API standards, purchaser options and evidence applicable to a specific industrial valve—not a downloadable reproduction of API requirements.
Raymon Valve technical content team. Final project decisions require the controlled documents and responsible engineer or quality reviewer.
API owns and publishes the referenced standards. This page paraphrases document roles and deliberately omits copyrighted tables, pressures, durations and acceptance clauses. Verify scope and current catalog status at api.org, then use the licensed contract edition and approved project specification.
Technical scope reviewed 27 July 2026. Editions, procedures, acceptance criteria and product evidence must be reconfirmed before order.
API Valve Standards Guide FAQ
Is API 6D the standard for every ball valve?
No. API 6D applies to pipeline valves within its stated scope. Ball valves used in other plant services may be purchased under a different product standard or project specification, so application and product scope must be checked.
Does API 598 define the complete valve design?
No. API 598 is primarily used for inspection and pressure testing within its scope. Product construction, rating, dimensions, ends, materials and special qualifications may be governed by other documents.
What does an API-compliant valve quotation need to state?
It should identify the applicable product standard and edition, valve configuration, purchaser options, deviations, supporting standards, inspection plan, required qualification evidence and final documentation—not just the word API.
Where should a buyer verify an API standard edition?
Use API's official standards catalog and the licensed publication selected by the contract. Record the edition and addenda in the requisition because web summaries and legacy lists may be outdated.
Send the requirement and the evidence you need to verify
We will identify the applicable scope, missing records and approval path without inventing compliance claims.
English 
German 
Arabic 
French 
Spanish 
Italian 
Portuguese 
Russian