Author: Bruce Zheng, Co-Founder and Valve Engineer at NTGD Plug Valve
Last Updated: June 26, 2026
An API 599 plug valve is a metal plug valve specified for industrial service under the API 599 standard framework. For buyers, EPC teams, and QA/QC engineers, the standard number is only the starting point. A complete RFQ still needs valve size, pressure class, body material, plug design, end connection, operation method, service medium, temperature, inspection documents, and testing requirements.
When a project specification calls for an API 599 plug valve, the immediate questions are practical: What data should be included in the RFQ? Which related standards must be separated from API 599? What documents should be checked before shipment? If the buyer only writes “API 599 plug valve” without construction, material, testing, and document details, different suppliers may quote different valve designs, and the mismatch may appear later as missing test records, flange incompatibility, material approval issues, or inspection rework.
API 599 is often discussed together with API 598, API 6D, and API 6A. These standards are not interchangeable. API 598 is normally tied to valve inspection and pressure testing, API 6D is tied to pipeline valve requirements, and API 6A is tied to oilfield and wellhead equipment. Other project-level standards, including fire-safe, emission, pressure-temperature, flange, and welding-end requirements, should be reviewed separately when the project specification requires them.
This guide explains what buyers should check before requesting an API 599 plug valve, approving manufacturer documents, or arranging final inspection. It does not provide the full API 599 text, does not offer an API 599 PDF download, and does not replace the project specification or the latest official standard.
What Is API 599 for Plug Valves?
API 599 is used in industrial plug valve specifications when the project requires a recognized standard for metal plug valves. In buyer terms, it helps define the expected design basis, but it does not complete the whole purchase specification by itself.
For edition control and exact scope wording, verify the applicable standard through an authorized listing such as API Std 599 before finalizing the RFQ.
A common but incomplete RFQ line is:
API 599 plug valveThat statement is not enough for a manufacturer, inspector, or purchasing team to confirm the correct valve. The RFQ still needs to define service conditions, construction details, testing expectations, documentation requirements, and client-specific approval criteria.
API 599 in Buyer Terms
For procurement and engineering teams, API 599 should be treated as a design and specification reference for plug valves, not as a full purchase description.
A buyer still needs to define:
- valve size;
- pressure class;
- body and trim material;
- plug type;
- lubricated or non-lubricated design;
- sleeve, lining, seat, or hard-facing requirement;
- flanged, threaded, or welded end connection;
- operation method;
- testing standard;
- inspection document package;
- marking and nameplate requirements.
These fields directly affect supplier selection and document approval. If the design type is missing, one supplier may quote a lubricated plug valve while another quotes a sleeved or lined design. If the end connection standard is missing, the valve may fit the written standard but still create flange drilling, gasket, or welding problems during installation. If material, sleeve, or lining details are not stated, the offer may pass a basic commercial check but fail service compatibility or QA/QC approval.
Why Buyers Search for API 599 Plug Valves
Most searches for API 599 plug valves come from project execution situations. A buyer may have a specification that mentions API 599 but does not explain how to prepare the RFQ. An EPC engineer may need to separate API 599 from API 598 or API 6D. A QA/QC team may need to check whether the MTC, pressure test report, nameplate, and approved drawing match the purchase order.
The search intent is usually not only “What is API 599?” It is also:
- Can this plug valve meet my project specification?
- What information should I give the supplier?
- Which documents should I request?
- Is API 599 a testing standard?
- Is API 599 enough for pipeline or oilfield service?
- Which related standards should be written separately?
What This Article Covers
This article focuses on the buyer-facing side of API 599 plug valves:
- API 599 plug valve scope;
- covered and not-covered items;
- RFQ data requirements;
- related standards boundary;
- inspection document review;
- product bridge for common plug valve designs;
- FAQ for standard confusion.
It does not reproduce API 599 standard text. It also does not provide free PDF downloads, pressure test charts, leakage allowance tables, supplier lists, price lists, or product catalogues.
API 599 Scope: Which Plug Valves Are Covered?
API 599 is most relevant when a project specification calls for metal plug valves in industrial service. The exact construction still depends on valve design, size, pressure class, material, connection type, and service condition.
Metal Plug Valves and Quarter-Turn Design
A plug valve uses a cylindrical or tapered plug with a port through the plug. The plug rotates to open, close, or divert flow. In an API 599 plug valve RFQ, the buyer should confirm that the valve is an industrial metal plug valve with a pressure-retaining body, plug-type obturator, and construction suitable for the specified industrial service.
The key boundary is not a long list of other industrial valve families. The practical boundary is this: API 599 plug valve language should not be used for household plumbing plugs, shower valve parts, or generic non-industrial “plug” items. The project specification should clearly identify the valve as a plug valve, then define design, material, pressure rating, end connection, and inspection requirements.
End Connections: Flanged, Threaded and Welding Ends
API 599 plug valve discussions often include flanged, threaded, and welding-end configurations. However, the end connection must still be specified clearly in the RFQ.
Buyers should confirm:
| End Connection Item | What to Check | Why It Matters |
|---|---|---|
| Flanged end | RF, FF, RTJ, flange standard, drilling, pressure class | Affects piping compatibility, gasket selection, bolting, and site fit-up |
| Threaded end | Thread type, size, pressure rating | Affects installation method and sealing reliability |
| Butt welding end | Pipe schedule, weld end preparation, material | Affects welding procedure, field installation, and weld-end compatibility |
| Socket welding end | Socket size, pressure class, material | Affects compact piping connections and weld preparation |
| Face-to-face or end-to-end dimension | Applicable dimensional standard or approved drawing | Prevents replacement mismatch, layout conflict, and installation delay |
The RFQ should not simply say “API 599 with flanged ends.” It should state the flange type, pressure class, material, dimensional basis, and any client-specific piping requirements.
Lubricated and Non-Lubricated Plug Valve Designs
API 599 plug valves may be discussed in relation to different plug valve designs. The buyer should clarify whether the project needs:
- lubricated plug valve;
- non-lubricated plug valve;
- sleeved plug valve;
- lined plug valve;
- metal-seated plug valve;
- hard-faced design;
- pressure-balanced design.
These terms should not be treated as interchangeable. A lubricated plug valve relies on sealing support from sealant and may require periodic maintenance, so the RFQ should address sealant compatibility, operation condition, and maintenance access. A non-lubricated or sleeved plug valve relies on sleeve material and sealing construction, so the RFQ should state sleeve material, temperature limit, chemical compatibility, and shutoff expectation.
Lined, metal-seated, and hard-faced designs should be treated as RFQ design fields, not as generic catalogue labels. The buyer should connect each design choice to the actual medium, temperature, pressure differential, corrosion risk, and inspection requirement.
Size, Pressure Class and Material Are Still Project-Specific
API 599 does not remove the need to specify the main valve data. The buyer must still define:
| Specification Field | Example of Buyer Input | Why It Matters |
|---|---|---|
| Size | NPS / DN | Defines connection size, bore requirement, and layout compatibility |
| Pressure class | Class 150, 300, 600, 900, 1500, etc. | Defines the pressure-temperature basis together with material and service |
| Body material | WCB, CF8M, alloy steel, ductile iron, etc. | API 599 does not replace material compatibility review for medium and temperature |
| Plug material | Stainless steel, alloy, coated or hard-faced plug | Affects sealing surface, wear resistance, and operating life |
| Sleeve / lining / seat | PTFE, PFA, rubber, metal seat, hard facing | Affects chemical compatibility, temperature limit, and shutoff reliability |
| End connection | Flanged, threaded, butt weld, socket weld | Affects piping fit-up, installation, and field inspection |
| Operation method | Lever, gear, pneumatic actuator, electric actuator | Affects torque review, accessibility, and automation interface |
| Service medium | Oil, gas, chemical, steam, slurry, water, etc. | Drives material, sleeve, lining, packing, and sealing selection |
| Temperature | Minimum and maximum operating temperature | Affects sleeve, lining, packing, and material suitability |
| Inspection documents | MTC, test report, ITP, drawing, datasheet | Affects QA/QC approval and shipment release |
What API 599 Does Not Cover by Itself
A strong API 599 plug valve specification should also define related standards and project requirements. API 599 alone should not be used as a substitute for all design, testing, inspection, and application details.
API 599 Is Not an API 598 Testing Guide
API 599 and API 598 serve different roles in a purchase specification. API 599 is used for the plug valve standard and specification basis, while API 598 is commonly used for valve inspection and pressure testing.
Buyer action: state the testing standard separately in the RFQ and request a traceable pressure test report. Detailed shell test procedures, closure test procedures, test pressure tables, and leakage allowance charts should be handled in the testing specification or a dedicated plug valve testing and inspection article.
For detailed factory testing, leakage checking, and maintenance inspection procedures, keep this article focused on API 599 and use plug valve testing and inspection methods as the deeper testing reference.
API 599 Is Not the Same as API 6D
API 6D is normally associated with pipeline valve requirements. A plug valve may appear in a pipeline project, but an API 599 plug valve should not be assumed to meet API 6D requirements automatically.
Buyer action: if the project is pipeline service or the specification states API 6D, write API 6D as a separate requirement and confirm it before quotation.
API 599 Is Not the Same as API 6A
API 6A is associated with oilfield and wellhead equipment. It may involve high-pressure upstream, manifold, wellhead, cementing, or fracturing service.
Buyer action: do not use API 599 as a substitute for an API 6A oilfield specification. If API 6A is required, treat it as a separate product and standard review.
API 599 Does Not Replace Fire-Safe or Fugitive Emission Requirements
Some projects require fire-safe testing, fugitive emission qualification, or special environmental compliance. These requirements may involve API 607, API 6FA, API 641, or client-specific specifications.
Buyer action: state fire-safe or emission qualification separately in the RFQ if required. Do not assume it is included just because the valve is described as API 599.
API 599 Is Not a Free PDF or Catalogue Page
Some users search for “API 599 PDF” or “API 599 latest edition.” A technical article should not replace the official standard source. Buyers should verify the applicable edition through official standard channels, client specifications, EPC documents, or purchase requirements.
Buyer action: cite the required standard edition in the RFQ’s design standard field, then add the missing project data, testing requirement, and document package.
API 599 Covered vs Not Covered
| Item | Current Page Treatment | Buyer Action |
|---|---|---|
| API 599 plug valve definition | Covered | Use as the main article scope, then add project-specific RFQ data |
| Metal plug valve scope | Covered | Confirm industrial plug valve construction and service suitability |
| Flanged, threaded, welding ends | Covered as RFQ fields | Specify exact end connection, dimensional basis, and piping interface |
| Lubricated / non-lubricated design | Covered as product bridge | Define sealing method, sleeve/lining material, and service condition |
| Size, class, material | Covered as RFQ data | Include in RFQ, datasheet, drawing, and document review |
| API 598 testing | Boundary only | State the testing standard in the RFQ and request a traceable test report |
| API 6D pipeline valve | Boundary only | Confirm whether pipeline valve requirements apply before quotation |
| API 6A oilfield valve | Boundary only | Treat as a separate oilfield standard and product review |
| Fire-safe / emission requirements | Boundary only | State fire-safe or emission qualification separately if required |
| API 599 PDF download | Not covered | Use official standard sources and project documents |
| Product catalogue / price list | Not covered | Route product selection or quotation details to the product/RFQ process |
Key RFQ Data for an API 599 Plug Valve
A complete RFQ should translate the standard requirement into clear project data. This helps the manufacturer select the correct design and helps the buyer compare offers on the same technical basis.
Basic Valve Data
The first part of the RFQ should define the valve body, pressure class, material, and connection requirements.
| RFQ Field | What to Provide | Why It Matters |
|---|---|---|
| Valve type | API 599 plug valve | Confirms the valve family and prevents generic valve substitution |
| Size | NPS / DN | Defines connection size, bore requirement, and layout fit |
| Pressure class | Class rating or project pressure rating | Links the valve to the required pressure-temperature envelope |
| Body material | WCB, CF8M, alloy, ductile iron, etc. | API 599 does not select material for the service; medium and temperature still control suitability |
| Plug material | Stainless steel, alloy, coated or hard-faced plug | Influences sealing surface durability, wear behavior, and operation life |
| End connection | Flanged, threaded, butt weld, socket weld | Controls piping compatibility and site installation method |
| Face-to-face / end-to-end | Standard or approved drawing requirement | Prevents installation mismatch and replacement delays |
| Operation | Lever, gear, pneumatic, electric | Drives torque review, automation interface, and access requirements |
Design and Service Data
The second part should define service conditions and sealing construction.
| RFQ Field | What to Provide | Why It Matters |
|---|---|---|
| Design type | Lubricated, non-lubricated, sleeved, lined, metal-seated | Changes sealing method, torque behavior, maintenance requirement, and supplier construction |
| Sleeve / lining | PTFE, PFA, rubber, metal seat, hard facing, etc. | Controls chemical compatibility, temperature limit, and shutoff reliability |
| Medium | Oil, gas, chemical, water, slurry, steam, etc. | Drives material, lining, sleeve, packing, and sealing review |
| Temperature | Minimum and maximum | Can limit sleeve, lining, packing, and body material selection |
| Pressure differential | Normal and maximum | Affects operating torque, sealing load, gear selection, and actuator sizing |
| Corrosion risk | Chloride, acid, caustic, sour service, etc. | If not declared, the valve may suffer premature sleeve, seat, lining, or body failure |
| Solids or abrasion | Clean fluid, particles, slurry, crystals | Drives plug, seat, and lining selection to reduce erosive wear and leakage risk |
| Operation frequency | Normally open, normally closed, frequent operation | Affects wear expectation, gear/actuator review, and maintenance planning |
Standards and Document Requirements
The third part should define compliance and inspection expectations.
| Requirement | What to State in RFQ | Buyer Note |
|---|---|---|
| Design standard | API 599 or project-specified standard | Keep design standard separate from testing standard |
| Pressure testing standard | API 598 or project requirement | Request a traceable test report that matches the RFQ |
| Fire-safe requirement | API 607 / API 6FA if required | Do not assume it is included in API 599 wording |
| Emission requirement | API 641 or project requirement if applicable | Confirm packing and qualification only when required |
| Pressure-temperature basis | ASME B16.34 or project requirement | Confirm material, class, and service condition together |
| Flange requirement | ASME B16.5 or project flange standard | Confirm RF / RTJ / FF, drilling, and gasket interface |
| Weld end requirement | ASME B16.25 or project requirement | Confirm pipe schedule and weld preparation |
| MTC | EN 10204 3.1 / 3.2 or project requirement if applicable | Confirm material traceability and certificate level |
| Inspection level | Factory inspection, client witness, third-party inspection | Clarify before production, not after shipment |
| Marking / nameplate | Size, class, material, standard, tag, manufacturer | Check against PO, drawing, and inspection documents |
API 599 vs Related Plug Valve Standards
The most useful way to handle standard confusion is to define each standard’s role. A buyer should not treat all “API plug valve” wording as the same requirement.
| Standard / Requirement | Main Role in Buyer Review | How to Treat It in This Article |
|---|---|---|
| API 599 | Plug valve design / specification reference | Main focus |
| API 598 | Valve inspection and pressure testing | Boundary only; request test report |
| API 6D | Pipeline valve requirements | Boundary only; future dedicated topic |
| API 6A | Oilfield / wellhead equipment | Boundary only; future dedicated topic |
| API 607 / API 6FA | Fire-safe testing where required | Light mention only |
| API 641 | Fugitive emission qualification where required | Light mention only |
The most common specification error is treating API 599, API 598, and API 6D as interchangeable labels. The result can be a valve designed to one requirement, tested to another, and applied in a service context that was not clearly reviewed.
Project-level supporting specifications may still be required. ASME B16.34 may appear for pressure-temperature and valve design references; ASME B16.10 may appear for face-to-face or end-to-end dimensions; ASME B16.5 may appear for flange requirements; ASME B16.25 may appear for butt-welding ends. AWWA, MSS, or other standards may apply in different plug valve contexts, especially when the project is not a petroleum or petrochemical API 599 specification. These should be treated as supporting project specifications, not as the main topic of this API 599 article.
API 599 vs API 598
API 599 helps define the plug valve specification. API 598 is used for inspection and pressure testing. In an RFQ, both may be relevant, but they should be written as separate fields.
A clear purchase requirement may need to state:
Design standard: API 599
Testing standard: API 598 or project-specified testing requirementThe test report should then match the testing requirement. Do not use API 599 wording as a substitute for the pressure test requirement.
For the testing boundary, reference an authorized listing for API Std 598 so the testing requirement is kept separate from the API 599 design standard.
API 599 vs API 6D
API 6D should be reviewed when the valve is part of a pipeline valve specification. API 6D may involve different documentation, marking, design, and testing expectations compared with a general API 599 plug valve requirement.
If a project specification states API 6D, the buyer should not downgrade the requirement to only API 599 without engineering approval.
For pipeline projects, use the API publication summary for API Specification 6D as the boundary reference rather than assuming every API 599 plug valve also satisfies pipeline-valve requirements.
API 599 vs API 6A
API 6A is a separate oilfield equipment context. It may involve high-pressure upstream, wellhead, manifold, or related oilfield service. It should not be merged into a general API 599 plug valve article.
If the buyer needs an API 6A plug valve, the RFQ should be treated as a separate oilfield plug valve specification.
API 599 and ASME Project Specifications
ASME standards often appear in plug valve project documents because they support pressure-temperature ratings, dimensions, flange requirements, or welding-end details.
For buyers, the practical point is simple: API 599 alone does not define every dimensional or connection detail needed for manufacturing and installation. The RFQ should state the applicable ASME or project dimensional standard when required.
Inspection Documents Buyers Should Check Before Shipment
A buyer should not wait until shipment to discover that the documents do not match the project requirement. Inspection document review should begin before production approval and continue before final release.
Material Certificate / MTC
The material certificate should support the material stated in the datasheet and purchase order.
Check whether the MTC covers:
- body material;
- plug material;
- stem material;
- sleeve, lining, or seat material if applicable;
- bolting or pressure-retaining parts if required;
- heat number and traceability if specified;
- chemical and mechanical properties if required by project documents.
If the RFQ requires stainless steel, alloy steel, low-temperature carbon steel, or corrosion-resistant material, the MTC should not be treated as a formality. A material mismatch can delay inspection release, create traceability gaps, or require document correction before shipment.
Pressure Test Report
The pressure test report should confirm that the finished valve was tested according to the RFQ or project requirement. For API 599 plug valve orders, buyers should check whether API 598 or another specified testing requirement applies.
At report level, confirm:
- the report identifies the exact valve by tag, serial number, size, and class;
- the stated testing standard matches the RFQ;
- the test result is recorded clearly;
- the report is signed or witnessed as required by the project;
- the report can be traced to the approved drawing, datasheet, or purchase order.
This article does not provide API 598 test pressure tables, hold times, or leakage allowance charts. Detailed testing methods should be handled in the project testing specification or a dedicated plug valve testing and inspection guide.
Nameplate and Marking
Before shipment, the nameplate and marking should be checked against the purchase order and approved documents.
| Nameplate / Marking Item | What to Check |
|---|---|
| Valve size | Matches RFQ and approved drawing |
| Pressure class | Matches purchase order |
| Body material | Matches datasheet and MTC |
| Standard reference | Matches project requirement |
| Tag number | Matches project line list or valve list |
| Manufacturer identification | Correct and traceable |
| Flow / operation indication | Included if required |
| Heat or serial number | Matches traceability documents if required |
A nameplate error may look minor, but it can create a documentation mismatch during site receiving inspection or final QA/QC release.
Drawing, Datasheet and ITP Review
For engineered projects, the buyer should also review:
- approved general arrangement drawing;
- valve datasheet;
- material list;
- ITP;
- inspection release note;
- packing list;
- coating or painting record if required;
- certificate package.
The approved drawing and datasheet should match the actual valve before shipment. If the drawing shows a gear-operated flanged valve but the packing list shows a lever-operated threaded valve, the document package has a serious mismatch.
How API 599 Relates to Plug Valve Product Selection
API 599 helps define a standard basis, but plug valve selection still depends on the actual service. The standard does not automatically decide whether the project needs a lubricated, non-lubricated, sleeved, lined, or pressure-balanced design.
Lubricated Plug Valve
A lubricated plug valve may be used where sealant-assisted sealing or specific industrial isolation conditions are required. In an API 599 RFQ, the buyer should state sealant compatibility, service medium, temperature, pressure differential, operation frequency, and maintenance expectation.
If the RFQ calls for sealant-assisted sealing, compare the service medium, sealant compatibility, pressure differential, and maintenance access against the lubricated plug valve product specification before quotation.
Do not specify a lubricated design only because a catalogue shows an API 599 plug valve. The RFQ should confirm whether the medium, site maintenance access, and operation method support that design.
Non-Lubricated / Sleeved Plug Valve
A non-lubricated or sleeved plug valve uses a sleeve or soft sealing element to support sealing and reduce friction. In an API 599 RFQ, the buyer should state sleeve material, chemical compatibility, temperature limit, shutoff requirement, pressure class, and operating torque requirement.
For projects where sleeved or non-lubricated plug valves are specified in oil and gas service, the existing guide on API standards for sleeved plug valves can support the product-specific side of this review.
This design can be relevant where lubricant contamination is not acceptable or where a low-maintenance sealing arrangement is preferred, but it still depends on the actual medium and temperature.
Lined or Corrosion-Resistant Plug Valve
If the medium is corrosive, a lined plug valve or corrosion-resistant material may be required. API 599 alone does not define chemical compatibility.
For corrosive media, the lining material should be reviewed together with the API 599 RFQ fields; use the lined plug valve page as the product bridge for lining and chemical-compatibility discussions.
The RFQ should state medium concentration, operating temperature, pressure, and corrosion risk. Lining material, body material, plug material, and sleeve material should be reviewed together.
Pressure-Balanced or High-Pressure Plug Valve
For higher pressure or difficult operating conditions, the buyer may need to discuss a pressure-balanced design, gear operation, or actuator sizing. The project should not assume that all API 599 plug valves have the same operating torque or pressure behavior.
When pressure differential, operating torque, or actuator sizing becomes a concern, route the product discussion to the pressure-balanced plug valve page instead of turning the API 599 guide into a high-pressure product page.
The RFQ should include pressure differential, operation frequency, gear or actuator preference, and any torque-related site limitation so the manufacturer can review the correct design.
Typical Applications Where API 599 Plug Valves May Be Specified
API 599 plug valves may appear in petroleum, petrochemical, chemical, and general industrial service specifications. However, the application itself should not override the actual service data.
Petroleum and Petrochemical Service
In petroleum and petrochemical projects, plug valves may be used for isolation or shutoff service. The buyer should still define material, class, sealing design, fire-safe requirement, testing requirement, and inspection documents.
A project that says “oil and gas service” is not specific enough. The manufacturer still needs fluid, pressure, temperature, connection, operation, and inspection requirements.
Chemical and Industrial Process Lines
For chemical and industrial process lines, the key issue is often material compatibility. A plug valve that works for one medium may not be suitable for another medium at a different concentration or temperature.
The RFQ should clearly state:
- chemical name and concentration;
- operating and design temperature;
- normal and maximum pressure;
- solids or crystallization risk;
- corrosion allowance or lining requirement;
- leakage or shutoff requirement.
When the Project Specification Should Override Generic Assumptions
The project specification should control the final requirement. If the project requires a specific standard edition, material, inspection level, fire-safe test, third-party witness, or document package, those requirements should be stated directly.
Generic catalogue wording is not enough for engineered procurement.
Common Mistakes When Specifying API 599 Plug Valves
Mistakes in API 599 plug valve procurement usually happen before production. They start with incomplete RFQs, unclear standards, or missing inspection requirements.
| Mistake | Risk | Better RFQ Approach |
|---|---|---|
| Writing only “API 599” | Supplier may quote different construction, materials, or documents | State design standard, valve construction, size, class, materials, test standard, and document package together |
| Confusing API 599 with API 598 | Test report may not match project expectation | Use separate RFQ fields for design standard and testing standard |
| Treating API 6D as the same as API 599 | Pipeline requirements may be missed | Confirm whether pipeline valve requirements apply before supplier quotation |
| Treating API 6A as the same as API 599 | Oilfield service requirements may be missed | Use a separate API 6A review when wellhead or oilfield equipment is required |
| Ignoring sleeve or lining material | Chemical compatibility and shutoff reliability risk | Review medium, temperature, sleeve/lining material, and shutoff requirement together |
| Ignoring operation method | Torque, gear, or actuator mismatch | State lever, gear, pneumatic, or electric operation and provide pressure differential if relevant |
| Not checking documents before shipment | Rework, release delay, or receiving inspection issue | Hold shipment release until MTC, test report, nameplate, drawing, and PO match |
| Searching only for PDF | Specification remains incomplete | Verify the official standard edition and prepare complete RFQ data |
Final RFQ and Inspection Checklist for API 599 Plug Valves
Use this final fit-check before sending an RFQ, approving documents, or releasing the valve for shipment. The goal is not to repeat every detail in the article, but to confirm the highest-risk items.
Before Sending RFQ
| Checkpoint | Confirmed? |
|---|---|
| Valve is clearly specified as an API 599 plug valve | |
| Size / NPS / DN and pressure class are defined | |
| Body, plug, sleeve, lining, and seat materials are defined where applicable | |
| End connection and dimensional basis are stated | |
| Lubricated, non-lubricated, sleeved, lined, or metal-seated design is clarified | |
| Medium, temperature, pressure differential, corrosion, and abrasion risk are provided | |
| Operation method is defined | |
| Testing standard and inspection document package are stated | |
| Fire-safe or emission requirement is stated if applicable | |
| Latest applicable standard edition is controlled by project documents |
Before Approving Manufacturer Documents
| Document | What to Check |
|---|---|
| Datasheet | Matches RFQ and project specification |
| General arrangement drawing | Size, end connection, operation, face-to-face |
| Material list | Matches body, plug, sleeve, lining, and trim requirements |
| MTC | Supports material and traceability requirements |
| ITP | Matches inspection and witness requirements |
| Test report or test procedure reference | Matches required testing standard |
| Nameplate draft | Matches marking requirement |
| Packing and preservation plan | Matches shipping and site storage requirements |
Before Shipment or Final Inspection
| Inspection Item | What to Confirm |
|---|---|
| Valve configuration | Matches approved drawing and purchase order |
| Nameplate | Size, class, material, standard, tag, manufacturer |
| End connection | Matches drawing and piping requirement |
| Operation | Lever, gear, or actuator matches requirement |
| Test report | Complete, traceable, and aligned with RFQ |
| MTC | Matches pressure-retaining materials |
| Drawing revision | Latest approved version |
| Certificate package | Complete before shipment |
| Packing | Suitable for transport and site storage |
When to Ask NTGD Plug Valve for Specification Review
Ask for a specification review when:
- the project mentions API 599 but does not define valve construction;
- API 599, API 598, API 6D, or API 6A appear together in the same specification;
- the medium is corrosive, abrasive, high-temperature, or difficult to seal;
- sleeve, lining, plug material, or operation method is unclear;
- the inspection document package is not clearly defined;
- the buyer needs to compare supplier offers on the same basis.
FAQ About API 599 Plug Valves
What does API 599 actually cover for plug valves?
API 599 is used as a standard reference for metal plug valves in industrial service. For buyers, it helps define the design/specification basis, but it does not replace RFQ data such as size, class, material, end connection, service condition, testing standard, and document requirements.
What is an API 599 plug valve?
An API 599 plug valve is a plug valve offered or specified according to API 599 requirements. The buyer still needs to confirm the exact construction, material, sealing design, end connection, operation method, testing requirement, and inspection documents.
What is the API standard for plug valves?
API 599 is one important API standard associated with plug valves. Depending on the project, API 598, API 6D, API 6A, API 607, API 6FA, API 641, ASME standards, or other project standards may also appear, but each has a different role.
Is API 599 a testing standard?
API 599 should not be treated as the main testing standard. Valve inspection and pressure testing are usually stated separately, often with API 598 or another project-specified testing requirement.
What is the difference between API 599 and API 598?
API 599 is related to plug valve specification. API 598 is related to valve inspection and pressure testing. A purchase order may need both, but design standard and testing standard should be written as separate RFQ fields.
Does API 599 cover pressure testing?
API 599 may appear in the same purchase specification as pressure testing requirements, but buyers should confirm the actual testing standard and request a traceable test report. Detailed test pressure tables or leakage criteria should be checked against the applicable testing standard and project documents.
What is the difference between API 599 and API 6D?
API 6D is associated with pipeline valve requirements. API 599 plug valves and API 6D plug valves may overlap in some projects, but they should not be assumed to be the same. If API 6D is required, it should be stated clearly.
Is API 599 the same as API 6A?
No. API 6A is associated with oilfield and wellhead equipment. If the service is wellhead or oilfield equipment, treat API Specification 6A as a separate specification review instead of folding it into the API 599 plug valve scope.
Does API 599 apply to sleeved or non-lubricated plug valves?
It may be relevant depending on valve construction and project specification. Buyers should confirm sleeve material, sealing design, temperature, medium, pressure class, and documentation requirements rather than relying only on the standard number.
Do buyers need an API 599 PDF?
Buyers should verify the required edition through official standard channels, client specifications, or EPC documents. Instead of searching for PDFs, reference the required edition in the RFQ’s design standard field and then provide complete valve data.
How should buyers verify the latest API 599 edition?
Verify it through official standard sources, client specifications, EPC documents, or purchase specifications. Do not rely only on old PDF copies, catalogue descriptions, or supplier wording.
What should be included in an API 599 plug valve RFQ?
At minimum, include size, pressure class, body material, plug and sleeve or lining material, end connection, operation method, service medium, temperature, pressure differential if relevant, testing standard, inspection documents, and any fire-safe or emission requirements.
What documents should be checked before inspection or shipment?
Check the approved drawing, datasheet, MTC, pressure test report, ITP, nameplate, marking, packing list, and certificate package. These documents should match the purchase order and approved technical submittals before shipment release.
Conclusion
An API 599 plug valve specification should be clear enough for the manufacturer to select the correct valve and for the buyer to inspect the correct documents. The standard number alone is not enough.
Before sending an RFQ, separate the design standard, testing standard, material requirements, end connection, service data, and document package. Before shipment, check whether the MTC, test report, nameplate, drawing, and certificate package match the purchase order and approved documents.
Use the checklist above to complete the RFQ before quotation and to reduce approval delays before shipment. When API 599 appears together with API 598, API 6D, or API 6A, or when material, sleeve, lining, or inspection document requirements are unclear, the specification should be reviewed before the order is placed.
Application / Specification Support
If your project specification mentions API 599 plug valves, NTGD Plug Valve can review the RFQ data before quotation. Share the plug valve size, pressure class, material, plug type, sleeve or lining requirement, end connection, operation method, service medium, temperature, and inspection document requirements for a specification review.
For a broader product-fit discussion, send the completed RFQ fields through the plug valve specification review channel so the valve construction, testing standard, and document package can be checked together.
This review is most useful when the project mixes API 599 with API 598, API 6D, or API 6A, or when the valve design, material compatibility, testing standard, or shipment document package is not clearly defined.