Why API Standards Matter More to a Buyer Than the Model Number
In oil, gas and petrochemical procurement, the API standard cited on a valve is often more operationally important than the brand or model — it determines whether the item will pass incoming inspection, whether it is compatible with the rest of the piping system's design basis, and in some jurisdictions whether it is legal to install at all. A buyer does not need to design to these standards, but does need to know what each one actually certifies so the right one ends up on the RFQ.
The four standards below cover the large majority of API-referenced valve purchases: large-bore cast-steel gate/globe/check valves (600), small-bore forged-steel gate valves (602), pipeline ball and check valves (6D), and the fire-test standard that frequently rides alongside both (607).
API 600: Cast Steel Gate, Globe & Check Valves
API 600 covers bolted-bonnet, cast-steel gate, globe and check valves used in refinery and petrochemical isolation service, typically DN50 and above. It specifies design features (OS&Y rising stem, bolted bonnet, back-seat), minimum wall thickness and testing requirements. This is the standard behind most large-bore refinery isolation gate valves — the default choice for primary isolation on hydrocarbon lines.
When citing API 600 on an RFQ, also specify the pressure class (150 through 1500) and body material (commonly WCB for general service, upgrading per medium) — API 600 sets the design and test rules, not the material or class, which the buyer still has to specify separately.
API 602: Forged Steel Small-Bore Gate Valves
API 602 is the small-bore counterpart to 600 — forged (rather than cast) steel gate valves, typically DN50 and below, used where the smaller bore makes forging more practical and economical than casting. Forged construction also gives a denser, more defect-resistant body for small, high-pressure-class applications.
A common buyer mistake is specifying API 600 for a small-bore item where API 602 is the correct and more cost-effective standard — check the bore size against both standards' typical ranges before locking the spec. See API 600 vs API 602 for a direct comparison.
API 6D: Pipeline Valves — Ball, Check and Plug
API 6D covers valves used in pipeline service — predominantly ball and check valves, with a strong emphasis on bidirectional sealing, full-bore design for pigging compatibility, and in many cases an anti-static device so that static charge cannot arc across the ball during operation. This is the standard for transmission and gathering pipeline isolation, distinct from plant/refinery isolation covered by API 600.
If the application is a cross-country or gathering pipeline rather than in-plant process piping, API 6D — not API 600 — is usually the applicable standard; confirm with the project's piping engineer which service category the line falls under.
API 607: Fire Test for Soft-Seated Quarter-Turn Valves
API 607 (closely related to ISO 10497) is a fire-test standard, not a design standard — it certifies that a soft-seated valve (typically a ball valve) continues to hold pressure during and after exposure to a standardized fire, through a combination of graphite packing and a metal-to-metal backup seal behind the primary soft seat. It commonly rides alongside API 6D on pipeline ball valves and alongside general service ball valves anywhere emergency shutdown duty is specified.
Specify API 607 explicitly whenever the valve is intended for emergency shutdown (ESD) or any duty where fire-safe performance is a regulatory or project requirement — it is not implied automatically by API 6D or API 600 compliance and has to be called out separately on the RFQ.
A useful habit when reviewing an incoming RFQ against these four standards is to ask which one the project document actually cites by number, rather than inferring it from a general description like "refinery-grade" or "pipeline-rated." Project specifications are usually precise about this, and matching the cited standard exactly avoids the rework of discovering at inspection that a valve built to API 600 was actually required to be API 6D for a pipeline segment, or vice versa.
Several of these standards are periodically revised, and a project specification that cites a specific edition year is doing so deliberately — most commonly because the project's engineering basis or an EPC contract was fixed against that edition. Supplying a valve built to the current edition when an earlier one was specified can create a documentation mismatch at inspection even if the physical valve itself would easily satisfy either version, so matching the cited edition, not just the standard number, is worth confirming on any project-driven RFQ.
Frequently Asked Questions
Do I need API 600 and API 607 on the same valve?
Only if the valve is a soft-seated design (most gate valves are metal-seated and do not need 607). Fire-safe soft-seated ball valves commonly carry both 6D (or general service) and 607 together.
Is API 6D only for pipelines, or does it apply in plants too?
API 6D is specifically a pipeline valve standard. In-plant process isolation typically falls under API 600 or 602 depending on bore size, even though the valve types (ball, gate) may overlap.
What pressure class should I specify alongside API 600?
Match the class to the line's design pressure per ASME B31.3 — API 600 does not set the class itself. Class 150 and 300 cover most refinery isolation duty; higher classes apply to specific high-pressure services.
Can a non-API-certified valve ever be used on an API-spec project?
Generally no for the pressure-retaining items the spec explicitly calls out — most EPC contracts require the cited API certification as a contractual and inspection condition, not just a performance guideline.
Next step
Tell us which API standard your project spec cites — or describe the service and let us confirm the applicable standard — and we will quote against the correct certification scope from the start.
Request a quotation → See the oil & gas solution