API 5L SR5, SR6 and SR8: why the edition matters

If an old specification, stock list or supplier offer says “API 5L SR5 / SR6 / SR8,” the first question should be: which edition of API 5L?

These SR numbers are a good example of why supplementary-requirement codes must not be interpreted from memory or from a vendor table. API 5L has been reorganized substantially over its long history, and the meaning — or even existence — of a particular SR number depends on the edition.

The short answer

• SR5 and SR6 are well-established legacy fracture-toughness references found in older API 5L editions.
• SR8 is especially edition-sensitive. Historical records show it used for a Charpy absorbed-energy requirement in much older API 5L material, while later editions reorganized supplementary requirements.
• Modern API 5L editions use an annex-based structure for many special requirements; you should not translate an old SR number into a current requirement without checking the governing edition.

SR5 in the 43rd-edition structure

A public historical copy of API 5L 43rd edition shows SR5 as fracture-toughness testing using Charpy V-notch specimens for pipe size 4½ in. or larger. It included options addressing shear-area and absorbed-energy criteria.

This is important because many commercial websites oversimplify SR5 as:

“Charpy for welded pipe 20 in. and larger, X52 and above.”

That shorthand does not accurately describe the full legacy SR5 scope.

SR6 in the 43rd-edition structure

In the same historical structure, SR6 covers drop-weight tear testing (DWTT) on welded pipe of size 20 in. or larger, Grade X52 or higher.

DWTT and Charpy testing answer related but different fracture-behaviour questions. An RFQ should not treat them as interchangeable tests.

Why SR8 causes so much confusion

Historical industry documents use SR8 differently from what many current vendor webpages imply.

For example, an NTSB metallurgical report discussing pipe manufactured to API 5L 34th edition states that SR8 would have specified a Charpy absorbed-energy requirement, while SR5 addressed shear-fracture appearance.

Later API 5L editions reorganized fracture-toughness requirements. By the 43rd edition, the familiar fracture-toughness references prominently included SR5, SR6 and other supplementary requirements; by the 45th/46th-edition era, API 5L had moved major special-service and fracture-control requirements into normative annexes.

So a statement such as:

“SR8 = fracture toughness testing, latest API 5L”

is not sufficiently precise for procurement.

What replaced the old SR-style approach?

Modern API 5L is organized around the base PSL requirements plus annexes for additional service or performance needs. In the 46th-edition framework, examples included:

• Annex G — ductile fracture propagation resistance;
• Annex H — sour service;
• Annex J — offshore service;
• Annex K — special-service NDT;
• Annex N — longitudinal plastic strain capacity.

For offshore pipe, see API 5L Annex J. For the NDT relationship, see Annex E vs Annex K.

How to handle an RFQ containing SR5, SR6 or SR8

Do not delete the requirement and do not silently convert it. Instead:

1. Identify the API 5L edition cited by the project.
2. If no edition is stated, request clarification.
3. Determine exactly what the project expects: Charpy shear area, Charpy absorbed energy, DWTT, fracture-arrest performance, or another requirement.
4. Check whether the old SR reference is still valid in that edition.
5. If the project has been updated to API 5L 47th, map the technical intent, not just the number, to the current standard.
6. Record the clarification in the PO/specification rather than relying on supplier interpretation.

Why this matters for stock material

Old stock can legitimately be certified to an older API 5L edition. In that case, an SR marking may make sense for that original edition.

The problem arises when a purchaser assumes the same SR number carries the same meaning in a new-edition order. Retesting can verify some properties, but it does not automatically convert material from one edition or supplementary requirement system to another.

Current-edition note

API published API Spec 5L 47th edition in June 2026. For a new purchase that is not contractually fixed to an earlier API 5L edition, confirm the applicable edition with the project/purchaser; the current API publication is the 47th edition. Verify the exact supplementary/annex requirements in the licensed governing edition.

MetalMate takeaway

SR numbers are not timeless definitions. SR5 and SR6 are recognizable legacy fracture-toughness requirements; SR8 is strongly edition-dependent. Whenever you see an SR number in an API 5L enquiry, identify the edition before interpreting the requirement.

Related Knowledge

• API 5L PSL1 vs PSL2
• API 5L Annex J for offshore service
• API 5L Annex E vs Annex K

References

• API, API Spec 5L 47th edition announcement: https://www.api.org/products-and-services/standards/important-standards-announcements/api-announces-47th-edition-of-foundational-line-pipe-standard-5l
• API, API Spec 5L 46th-edition announcement / historical edition context: https://www.api.org/products-and-services/standards/important-standards-announcements/standard-5l
• NTSB, Metallurgical factual report discussing API 5L 34th-edition SR5/SR8 requirements: https://data.ntsb.gov/Docket/Document/docBLOB?FileExtension=pdf&FileName=22-003+-+Coolidge+AZ+pipe-Rel.pdf&ID=13389445