API Pipe or ASME Pipe for a Gas Transmission Line? The Question Has a Wrong Premise

Procurement teams sourcing pipe for high-pressure gas transmission lines sometimes frame the specification decision as a choice between API and ASME. API 5L pipe on one side, ASME-referenced pipe on the other. Which standard should govern the purchase?

The framing is wrong, and understanding why it’s wrong is useful — because the confusion leads to specification documents that either create compliance gaps or impose conflicting requirements that suppliers can’t simultaneously satisfy.

API 5L and ASME B31.8 are not competing standards describing the same thing. They describe different things and are designed to be used together. Sorting out which standard does what is the prerequisite to writing a specification that actually works.

What API 5L Governs

API 5L is a product specification. It defines the requirements for the steel pipe itself: the chemical composition of the steel, the manufacturing process, the mechanical properties the finished pipe must achieve, the dimensional tolerances, the testing required during production, and the documentation the mill must provide with the shipment.

When a purchaser specifies API 5L X65 PSL2, they are specifying a product — a pipe with a minimum yield strength of 65,000 psi, manufactured and tested to the requirements of Product Specification Level 2, which includes more stringent chemistry controls, toughness testing, and nondestructive examination than PSL1. The mill produces the pipe, tests it, and delivers it with a mill certificate confirming it meets the specified standard.

API 5L says nothing about how the pipeline should be designed — what operating pressure is permissible, what safety factors apply, how the pipe should be installed, or how the system should be operated. That is not its scope.

What ASME B31.8 Governs

ASME B31.8 is a design code. It specifies how a gas transmission and distribution pipeline system should be engineered: how to calculate allowable operating pressure based on pipe grade and wall thickness, what location class system to apply based on population density near the pipeline, what safety factors are required, how welds should be tested, how the completed system should be pressure-tested before commissioning, and what ongoing integrity management is required during operation.

ASME B31.8 references API 5L as the material standard for line pipe used in the systems it covers. It doesn’t define the pipe material itself — it points to API 5L for that and then tells you how to use that material safely in a pipeline system.

When a regulator or project specification requires that a gas pipeline be designed to ASME B31.8, it’s requiring that the engineering behind the pipeline — pressure rating, safety factors, testing, installation — conform to B31.8. It is not specifying what the pipe is made of; B31.8 handles that by referencing API 5L.

Why They Have to Be Used Together

A pipeline that specifies only API 5L pipe without a design code has defined the material but not the engineering. It doesn’t establish what operating pressure is permitted, what wall thickness is required for that pressure in the applicable location class, or how the system must be tested. You have a product specification with no design basis.

A pipeline that specifies only ASME B31.8 without a material specification has a design code that references a material standard but hasn’t specified which grade or PSL of that material is required. The design code tells you how to calculate required wall thickness for a given pressure and pipe grade — but if the grade isn’t specified, the calculation has an open variable.

A complete specification uses both: API 5L defines what the pipe is, ASME B31.8 defines how it’s used. The design calculation in B31.8 takes the API 5L grade (and its associated yield strength) and the operating conditions as inputs, and produces the required wall thickness and the maximum allowable operating pressure as outputs.

This is why procurement documents for gas transmission line pipe typically reference both standards. The pipe purchase order specifies API 5L, the grade, and the PSL. The project specification or engineering basis document specifies that the system design conforms to ASME B31.8. Neither reference makes the other redundant.

Where Specification Confusion Creates Real Problems

The confusion between the two standards shows up in a few recurring ways, each with its own consequence.

The first is a purchase order that specifies “ASME pipe” without referencing API 5L. ASME B31.8 covers system design; it doesn’t define a pipe product. A supplier receiving a purchase order that specifies only ASME B31.8 compliance has to guess at what material standard applies, because B31.8 itself will send them back to API 5L. The order is underspecified, and the material received may not be what the project actually needed.

The second is a specification that references API 5L but doesn’t specify PSL1 or PSL2. PSL1 and PSL2 are substantially different products. PSL1 has fewer mandatory mechanical tests, less stringent chemistry requirements, and no mandatory Charpy impact testing. PSL2 requires tighter chemistry, mandatory heat analysis, impact testing, and more extensive nondestructive examination. A pipeline designed to ASME B31.8 for sour service or in a high-consequence area typically requires PSL2, but if the purchase order says only “API 5L X65,” suppliers may quote PSL1 — which is less expensive and easier to source — and technically answer the specification as written.

The third is a project that imposes both API 5L and ASME B31.8 requirements in the purchase order without clarifying which governs when they address overlapping topics. Both standards specify hydrostatic testing of the pipe, for example, but with different test pressures and procedures. A supplier receiving a purchase order that references both without hierarchy has a conflict they have to resolve somehow — and they may resolve it in the way that’s most convenient for them rather than most conservative for the project.

Writing a Specification That Works

A workable specification for API pipe in a gas transmission application does three things clearly.

It specifies the pipe product: API 5L, the grade (X52, X60, X65, or whatever the design requires), and the PSL (almost always PSL2 for transmission service). It may add supplementary requirements from Annex H or other annexes if the service conditions warrant — sour service, offshore service, or other specific requirements.

It specifies the design basis: ASME B31.8, with the applicable edition, and any project-specific additions to the code’s requirements. This is where location class, design factor, and operating pressure limits come from.

It resolves any conflicts explicitly: where the standards overlap, the specification states which takes precedence. Typically the more stringent requirement governs, but that should be stated rather than assumed.

The two standards aren’t alternatives. They cover different parts of the same problem, and a specification that treats them as competitors ends up with gaps where neither standard is clearly in control.

The Regulatory Dimension

In many jurisdictions, the regulatory framework for gas transmission pipelines mandates specific editions of ASME B31.8 (or equivalent national standards) as the required design code. The regulation doesn’t prohibit API 5L — it typically incorporates it by reference as the material standard. But regulatory compliance requires demonstrating that the system design conforms to the applicable code edition, which means having documentation showing that the pipe material, the pressure calculations, the construction, and the testing all conform to B31.8.

A pipeline project that buys API 5L pipe but can’t demonstrate B31.8 design compliance may have physically adequate pipe but a regulatory problem. Conversely, a project that has excellent design documentation but pipe that doesn’t fully conform to API 5L requirements has a material problem. Both standards need to be satisfied for the completed system to be compliant.

The question isn’t API or ASME. The question is whether the specification correctly assigns each standard to the part of the project it actually governs.