Ordering a valve to the wrong equipment scope is one of the most expensive mistakes in oil and gas procurement. For a wellhead or Christmas tree package, buyers normally evaluate API 6A; for a transmission pipeline or pipeline facility, they usually evaluate API 6D. Getting this right protects the pressure designation, testing regime, and documentation level. Start from the valve’s location and function, then confirm against the project specification and required standard edition.
Where the wellhead system ends and the pipeline system begins
API Specification 6A addresses wellhead and Christmas tree equipment used to contain and control pressure at the well. Depending on the equipment and project scope, this can include gate valves, chokes, check valves, plugs, connectors, and related pressure-control components. Drilling contractors, well-service companies, upstream EPC teams, and production operators are typical buyers.
API Specification 6D addresses pipeline and piping valves used in petroleum and natural gas transportation systems. Common product types include ball, gate, plug, and check valves. Pipeline EPC contractors, midstream operators, compressor or metering station teams, and terminal buyers commonly reference it.
The physical location alone is not always enough. A production facility may include wellhead equipment, gathering lines, process piping, and an export pipeline within one project. Mark the battery limits on the P&ID or line list and ask which specification governs each valve tag. The broader oil and gas valve application overview can help procurement teams organize valve requirements by service area.
Decision rule: Do not select the standard because two valves look similar. Select it from the equipment function, system boundary, purchaser specification, and governing standard scope.
Match the standard to equipment location and function first
| Evaluation point | API 6A direction | API 6D direction | Buyer action |
|---|---|---|---|
| Primary service area | Wellhead and Christmas tree equipment | Pipeline and pipeline-facility service | Identify the valve tag on the P&ID and system boundary drawing. |
| Typical buyer | Upstream operator, drilling contractor, well-service company | Pipeline operator, midstream EPC, terminal contractor | Confirm the end user’s approved project specification. |
| Typical valve functions | Well isolation, pressure control, choking, flow control | Line isolation, sectionalizing, non-return service | State whether the valve isolates, throttles, or prevents reverse flow. |
| Pressure designation | API 6A working-pressure framework | Pipeline pressure class or rating framework required by the project | Do not convert designations by name alone; verify allowable pressure at temperature. |
| Specification levels | PSL and other API 6A requirement categories may apply | API 6D has its own design, test, and documentation provisions | Write the required level or supplementary requirements into the RFQ. |
| Common valve types | Gate, choke, check, plug, and associated wellhead equipment | Ball, gate, plug, and check valves | Confirm that the requested product type is within the cited edition’s scope. |
| End connection | API 6A flanged or other specified wellhead connections | Flanged, butt-weld, or other project-approved pipeline ends | Provide connection standard, size, rating, bore, and mating details. |
| Operating concerns | High pressure, erosion, sand, well fluids, sour conditions | Long-distance isolation, pigging, cavity pressure, buried service | Describe solids, corrosion, pigging, and installation environment. |
| Testing basis | API 6A requirements tied to product and specification level | API 6D valve pressure and functional requirements | List required witnessing, acceptance criteria, and certificates. |
| Aktywacja | Manual, hydraulic, or project-specified operation | Manual, electric, pneumatic, hydraulic, or gas-over-oil as specified | Supply fail position, stroke time, power source, and control interface. |
| Dokumentacja | Records appropriate to the selected API 6A requirements | Records required by API 6D and the purchase specification | Agree on the document index before order placement. |
For a more focused pipeline discussion, buyers can review the guide to the API 6D standard for pipeline ball valves. Teams comparing adjacent valve standards may also find the API 608 and API 6D comparison useful, especially when a ball valve appears on process piping rather than a transmission pipeline.
For concrete API 6A equipment examples, compare the API 6A standard mud gate valve i API 6A check valve when defining wellhead-side pressure, trim, end-connection, and test requirements. Final selection should still match the project specification and service conditions.
Turn the service conditions into a complete valve specification
Writing only “API 6A valve” or “API 6D ball valve” leaves major technical decisions unresolved. Before requesting quotations, convert process data into a valve data sheet. At minimum, confirm the following:
- Valve type and function: gate, ball, plug, check, choke, isolation, throttling, or non-return duty.
- Nominal size and bore: include full-opening or reduced-bore requirements and whether pig passage is necessary.
- Pressure and temperature: provide design pressure, operating pressure, minimum and maximum temperatures, and credible transient conditions.
- Głoska bezdźwięczna: identify oil, natural gas, produced water, drilling fluid, multiphase fluid, hydrogen sulfide, carbon dioxide, solids, or chemical injection content where applicable.
- Przybory: state body, bonnet, stem, closure member, trim, seat, seal, bolting, overlay, and corrosion allowance requirements.
- Connections: define flange or weld-end standard, facing, schedule, bore, transition, and mating dimensions.
- Działanie: specify handwheel, gearbox, lever, actuator type, available utility, fail action, controls, and position feedback.
- Environment: note buried, offshore, desert, low-temperature, corrosive atmosphere, fire exposure, or hazardous-area conditions.
For API 6A equipment, the purchaser may also need to define the applicable product specification level, performance requirement, temperature class, material class, and other project-specific categories. These selections should reflect the actual well conditions rather than a default copied from an earlier order. The overview of API 6A PSL levels explains why the requested level affects manufacturing, verification, and documentation expectations.
If your team is deciding between API scopes, JH Valve / Janhen Valve can review the technical requirement before quotation. Share the service media, pressure, temperature, valve size, materials, applicable standard and edition, actuator arrangement, and leakage requirements so that assumptions and missing data can be identified early.
Testing and records must match the selected standard
A supplier statement that a valve is “API compliant” is not a complete inspection plan. Ask which API document, edition, product scope, and purchaser supplements are included. Buyers should also distinguish a product manufactured to specified technical requirements from any separate licensing, monogram, quality-system, or third-party approval requirement. Request documentary evidence appropriate to the contract rather than assuming one statement covers all of these items.
Prepare an inspection and test plan that identifies hold, witness, review, and surveillance points. Depending on the valve and purchase specification, the plan may address material identification, dimensional checks, visual examination, nondestructive examination, shell testing, seat testing, functional operation, actuator testing, coating inspection, and final marking review.
Material traceability is especially important when the service includes sour fluids, low temperatures, or project-restricted metallurgy. Ask how heat numbers are transferred through manufacturing and which material certificates must accompany pressure-containing and pressure-controlling parts. If sour-service standards, fire testing, fugitive-emission testing, or impact testing apply, cite the exact project requirement; they should not be assumed merely because API 6A or API 6D is specified.
API 6D projects may require buyers to clarify seat arrangement, preferred sealing direction, double block and bleed or double isolation and bleed expectations, cavity-pressure relief behavior, drain and vent provisions, and valve operating torque. These terms should be used according to the governing edition and project specification. For ball valve applications, the discussion of cavity relief testing for API 6D valves highlights a requirement that should be resolved before approval.
When two oil and gas valve quotations are not comparable
A lower quotation may simply exclude technical requirements included by another bidder. Normalize offers in a bid tab rather than comparing the total price first. Ask each bidder to identify deviations and assumptions line by line.
- Wrong scope: The quotation references API 6D for wellhead equipment, or API 6A for a pipeline valve, without a project-specific explanation.
- Missing standard edition: “Latest edition” may not match the edition named by the end user or contract.
- Unclear pressure basis: The offered designation is not checked against temperature, material group, and connection rating.
- Generic material description: Terms such as stainless trim or soft seat do not define exact grades, overlays, elastomers, or temperature limits.
- Unresolved bore: Full-bore, reduced-bore, and piggable requirements are not stated.
- Actuator omissions: Torque basis, safety factor, fail position, accessories, hazardous-area requirements, and control voltage are absent.
- Testing exclusions: Witnessing, supplementary NDE, low-temperature tests, or special leakage criteria are priced as later options.
- Incomplete records: The offer does not identify material certificates, test certificates, drawings, procedures, or final data-book contents.
Also check lifecycle consequences. A nonstandard seat compound, stem packing arrangement, actuator accessory, or special bolting choice can complicate future maintenance. Ask for recommended commissioning and operational spares, preservation instructions, installation orientation, operating limits, and the information needed to identify replacement parts. Do not postpone these questions until the valve reaches site.
Build an RFQ that separates API 6A requirements from API 6D requirements
A practical inquiry package should include a valve schedule plus tag-specific data sheets. The following template can be copied into an RFQ and expanded to match the project:
- Project, facility, valve tag, line number, and equipment location.
- Required standard, edition, addenda, purchaser specification, and order of precedence.
- Valve type, size, bore, pressure designation or class, and flow direction.
- Design and operating pressures and minimum, normal, and maximum temperatures.
- Fluid composition, phase, solids, corrosive constituents, and sour-service status.
- Body, trim, closure, seat, seal, bolting, overlay, and coating requirements.
- End connection standard, facing or weld preparation, dimensions, and mating information.
- Manual operator or actuator type, fail action, utilities, control signal, stroke time, and accessories.
- API 6A PSL or other applicable requirement categories, or API 6D functional and sealing requirements.
- Inspection, NDE, pressure testing, leakage acceptance, witnessing, and third-party inspection requirements.
- Marking, preservation, packing, lifting, storage, and delivery coordination requirements.
- Required drawings, material records, test certificates, procedures, spare-parts list, and final data book.
Require bidders to return a compliance matrix with every deviation clearly marked. This is more reliable than treating silence as acceptance. For an interface package containing both wellhead and pipeline valves, use separate data-sheet sections so that API 6A terminology is not unintentionally applied to API 6D items.
Freeze the technical scope before the order is placed
Freeze the technical scope before commercial award: confirm the standard boundary, edition, data sheet, approved drawing process, inspection points, documentation schedule, spare parts, and delivery interfaces. Pay particular attention to unresolved comments that affect body material, end dimensions, pressure rating, seat design, or actuator sizing; these can create expensive site changes.
Send JH Valve / Janhen Valve your completed valve list, data sheets, P&IDs, project specifications, and inspection requirements for a structured quotation review. A clear inquiry allows the proposed valve type, materials, connections, operation, testing scope, documents, and deviations to be evaluated before purchase.
Często zadawane pytania
Can an API 6A valve be used instead of an API 6D valve?
Not automatically. The two specifications address different equipment scopes and technical frameworks. Any substitution must be reviewed against the valve function, design conditions, connections, testing, documentation, and the end user’s project requirements.
Does API 6D apply to every valve in an oil and gas plant?
No. API 6D is associated with pipeline and piping valve applications within its defined scope. Process units may specify other valve standards, so buyers should check the line class, P&ID, valve data sheet, and governing project specification.
What information is essential for an API 6A valve RFQ?
Provide the equipment type, size, working pressure, temperature and material classes, required PSL or other applicable categories, media composition, end connections, actuation, testing, inspection, and documentation requirements.
Should the standard edition be written on the purchase order?
Yes. The purchase documents should identify the edition and any addenda required by the contract or end user. Buyers should also define which requirement takes precedence if the data sheet, project specification, and standard conflict.
Are API 6A and API 6D pressure ratings directly interchangeable?
No direct equivalence should be assumed from the rating name alone. Engineering must verify the applicable standard, design pressure and temperature, materials, end connections, allowable ratings, and project safety requirements.
Final thoughts
The correct standard follows the valve’s function and system boundary: API 6A for applicable wellhead and Christmas tree equipment, and API 6D for applicable pipeline and pipeline-facility valves. Confirming that boundary first makes pressure, material, sealing, testing, actuation, and documentation decisions easier to control throughout procurement.
