API valve standards help buyers, engineers, and procurement teams check whether an industrial valve is suitable for a specific service. They can affect valve design, pressure class, materials, testing, fire-safe performance, marking, and the documents supplied with the order.
The hard part is that one API number does not cover every valve decision. API 6D is often used for pipeline valves, API 600 and API 602 are linked with gate valve construction, API 608 is used for metal ball valves, API 609 covers butterfly valves, API 598 deals with inspection and testing, and API 607 is used for fire testing.
This guide explains the main API valve standards in plain English. It also shows how to match each standard to valve type, service condition, test requirement, and procurement document, so your RFQ is clear before a supplier quotes.
What Are API Valve Standards?
API valve standards are technical documents used in the oil, gas, petrochemical, power, pipeline, and process industries. They help define how a valve should be designed, made, tested, marked, inspected, and documented for a given service.
In valve procurement, an API standard is not just a label on a datasheet. It tells the buyer what type of valve the standard covers, what pressure and temperature range may apply, which tests are expected, and what evidence should be supplied with the shipment.
Different API standards control different parts of the valve decision. A design standard may define construction and pressure boundaries, while a testing standard may define shell, seat, or closure tests. A fire-safe standard or fugitive-emission standard may be added when the service has extra safety or environmental risk.
Because API editions and addenda can change, buyers should confirm the current requirement before placing an order. For edition status and official update notices, check the API latest updates page and match the requirement to the project specification.
API Valve Standards Quick Reference Table
The table below gives a practical first check. It does not replace the project specification or the purchased API document, but it helps you see which API standard is normally linked with each valve type or test requirement.
For live projects, always confirm the latest edition, addenda, and client requirements before ordering. This is especially important for pipeline valves, fire-safe service, fugitive-emission service, and valves supplied with third-party inspection.
| API standard | Common valve or topic | Main purpose | Buyer note |
|---|---|---|---|
| API 6D | Pipeline valves | Specification for pipeline and piping valves, often used for ball, gate, check, and plug valves in pipeline service | Check the current API Spec 6D edition and any project addenda |
| API 600 | Steel gate valves | Heavy-duty bolted bonnet steel gate valve construction | Useful for refinery, petrochemical, power, and high-pressure process service |
| API 602 | Small forged steel gate, globe, and check valves | Forged compact valve construction for smaller sizes and severe service | Often compared with API 600 when buyers choose cast or forged gate valves |
| API 603 | Corrosion-resistant gate valves | Gate valve construction for stainless steel and corrosion-resistant alloy service | Confirm material grade, body/bonnet design, and pressure class in the RFQ |
| API 594 | Check valves | Check valve design, including wafer, lug, and flanged styles | Ask for flow direction, cracking pressure needs, installation position, and pressure class |
| API 598 | Valve inspection and testing | Shell, seat, backseat, and closure test requirements for many valve types | Use it with the valve design standard; it is not a design standard by itself |
| API 599 | Metal plug valves | Plug valve design and pressure-temperature requirements | Confirm whether the plug valve is lubricated, non-lubricated, flanged, or butt-welded |
| API 607 | Fire testing for quarter-turn valves and soft-seated valves | Fire-safe test performance under defined test conditions | Do not treat it as a general ball valve design standard; use it with the valve design standard |
| API 608 | Metal ball valves | Ball valve design for flanged, threaded, and welded-end metal ball valves | API has issued a public API 608 7th edition notice, so buyers should confirm edition status |
| API 609 | Butterfly valves | Butterfly valve design for lug, wafer, and flanged-end types | Confirm seat type, disc material, pressure class, and shut-off requirement |
| API 6FA | Fire testing for API 6D and API 6A valves | Fire test method for pipeline and wellhead-related valve applications | Use when the project asks for fire testing beyond normal pressure testing |
| API 622 / 624 / 641 | Fugitive emissions | Packing and valve emission performance testing | Important for refinery, chemical, VOC, and low-emission service requirements |
Use this table as a starting point, then check the exact valve type, service medium, pressure class, temperature, material, end connection, and inspection documents. A correct API valve specification usually combines a design standard, a test standard, and any special fire-safe or emission requirement.
How to Choose the Right API Standard by Valve Type and Service
The best way to choose an API valve standard is to start with the valve type, then check the service condition. A valve for a process line, a pipeline, a fire-risk area, or a low-emission unit may need different standards even when the valve body looks similar.
Do not choose the standard only from the valve name. A ball valve, gate valve, check valve, or butterfly valve still needs the correct size range, pressure class, material, end connection, test method, and document package.
Start with the valve type
For gate valves, API 600 is often used for steel gate valves in larger process duties, while API 602 is often used for smaller forged steel gate, globe, and check valves. If the project is deciding between cast and forged gate valve construction, the API 600 vs API 602 guide is the better next step.
For ball valves, API 608 is commonly linked with metal ball valve construction. API 6D is used when the project needs a pipeline valve specification. If a ball valve could fall into either route, compare API 608 vs API 6D before finalising the RFQ.
Then check the service condition
The same valve type may need extra requirements when the service is high pressure, high temperature, flammable, corrosive, sour, low-temperature, or emission-sensitive. In those cases, the design standard is only one part of the specification.
- For pipeline service, check whether API 6D is required.
- For general shell, seat, and closure testing, state API 598 or the project test procedure.
- For fire-risk service, add the required fire-test standard and certificate scope.
- For VOC or low-emission service, confirm the fugitive-emission requirement.
- For document-controlled projects, list MTC, test report, inspection record, drawing, and certificate requirements in the RFQ.
Write the requirement as separate lines
A clear RFQ should not hide all requirements inside one phrase such as “API valve”. Write the design standard, testing standard, fire-safe or emission requirement, material, pressure class, end connection, operation method, and document package as separate lines.
This makes supplier quotations easier to compare. It also helps the engineering team see whether the offered valve matches the actual service, instead of only matching a familiar API number.
Design, Testing, Fire-Safe, Emission and Documentation Standards
When buyers read an API valve standard number, the first question should be: what job does this standard do? Some API standards guide the valve design, some guide the pressure test, and some only apply when the service needs fire-safe or low-emission performance.
This is why one API number is rarely enough for a complete valve RFQ. A correct specification often combines a design standard, a test standard, and any special safety or document requirement.
Design and construction standards
Design standards define the valve type, pressure boundary, construction style, materials, dimensions, marking, and pressure-temperature direction. API 6D is commonly used for pipeline valves, API 600 for steel gate valves, API 602 for small forged valves, API 608 for metal ball valves, and API 609 for butterfly valves.
Inspection and pressure testing standards
Testing standards focus on how the finished valve is checked. API 598 is often used for shell, seat, backseat, and closure testing across many industrial valve types.
Buyers should state the test standard, test medium, leakage requirement, and witness point clearly. If the RFQ only says “API valve”, the supplier may quote a suitable design but miss the inspection level your project expects.
Fire-safe and fugitive-emission standards
Fire-safe standards are added when the valve must keep a defined level of sealing and operation after fire exposure. API 607 is often discussed for quarter-turn valves and soft-seated valves, while API 6FA may apply to certain pipeline or wellhead-related valve applications.
API 607 is not a general ball valve design standard. If the project needs a fire-safe ball valve, the buyer should check the design standard and the fire-test certificate scope together. For this specific difference, see API 607 vs API 608.
Fugitive-emission standards, such as API 622, API 624, and API 641, are different again. They are used when stem packing and valve sealing performance matter for refinery, chemical, VOC, or low-emission service.
Documentation and traceability requirements
Documents are not a small detail in API valve procurement. A valve can meet the technical requirement but still fail project review if the MTC, pressure test report, inspection record, certificate copy, drawing, or marking record is missing.
For pipeline valves, document review can be especially important because API 6D projects often ask for clear traceability and project-specific inspection records. If you are checking a ball valve for pipeline service, this API 6D ball valve guide explains the topic in more detail.
The safest approach is simple: write the design standard, test standard, fire-safe or emission requirement, and document package as separate lines in the RFQ. That makes the quote easier to compare and reduces disputes after production.
Specification Checklist for API Valve Procurement
A clear API valve RFQ should do more than name one standard. It should tell the supplier what valve type, service condition, test requirement, and document package the project needs.
Use this checklist before asking for a quotation. It helps reduce wrong offers, missing certificates, unclear test reports, and delays during technical review.
| RFQ item | What to state | Why it matters |
|---|---|---|
| Valve type | Ball, gate, globe, check, butterfly, plug, or control valve | The API standard depends on the valve type and service role |
| Size and pressure class | NPS / DN size, ASME Class or PN rating, bore type, and pressure-temperature requirement | Wrong class or bore selection can make the valve unsuitable for the line |
| Material and trim | Body material, trim, seat, stem, packing, gasket, coating, and corrosion allowance if needed | Material mismatch can cause corrosion, leakage, or document rejection |
| End connection | Flanged, butt-welded, socket-welded, threaded, wafer, lug, or other connection type | End connection affects standard scope, face-to-face length, installation, and pressure boundary design |
| Design standard | For example API 6D, API 600, API 602, API 608, API 609, or another project-approved standard | This tells the supplier which construction rules the valve must follow |
| Testing standard | API 598, project test procedure, shell test, seat test, closure test, and witness requirement | Testing needs must be clear before production and inspection |
| Special safety requirement | Fire-safe, anti-static, blow-out proof stem, fugitive-emission, sour service, hydrogen service, or low-temperature service | These requirements may need extra design checks, tests, or certificates |
| Document package | MTC, pressure test report, inspection report, certificate copy, drawing, IOM manual, and packing list | Many industrial orders are delayed by missing documents, not only by valve quality issues |
For industrial projects, share the full working condition with the supplier instead of sending only an API number. MacoTango can review the valve type, material, pressure class, test requirement, and document needs for industrial valve standards support before the quotation is finalised.
How MacoTango Supports API / ASME / ANSI Valve Projects
API valve standards are only useful when they are matched with the real working condition. Before production, the supplier should understand the medium, pressure, temperature, valve type, operation method, inspection level, and document needs.
MacoTango supports industrial valve projects where API, ASME, ANSI, and related standards are part of the buyer’s specification. The product range includes common industrial valve types such as ball valves, gate valves, globe valves, check valves, butterfly valves, control valves, and actuated valve assemblies.
For an API-standard order, the important review points usually include body material, pressure class, end connection, trim, seat design, actuator choice, test method, marking, and document package. These details should be checked before the purchase order, not after the valve is finished.
Buyers can use MacoTango’s API / ASME / ANSI valve projects information as a starting point, then send the project specification for engineering review. If the order needs MTCs, pressure test reports, inspection records, or certificate copies, list those documents clearly in the RFQ.
Need Help Selecting an API Valve Standard?
API valve standards help make industrial valve procurement clearer, but the correct choice depends on more than one number. A reliable specification should connect the valve type, size, class, material, service condition, design standard, test method, inspection level, and document package.
Before sending an RFQ, check whether the project needs a design standard such as API 6D, API 600, API 602, API 608, or API 609, plus a testing or safety requirement such as API 598, API 607, API 6FA, or a fugitive-emission standard. This makes the quotation easier to compare and reduces document problems later.