Is API 682 actually mandatory, or just recommended? The standard answer across the industry is the same: “API 682 is a voluntary standard.” That answer is technically correct at the standards-body level — and practically misleading for the engineer holding a project specification that says “pumps per API 610.”
The confusion is predictable. API publishes voluntary standards. No government regulation names API 682 directly. But multiple independent mechanisms — contractual, regulatory, and owner-driven — routinely make API 682 compliance non-negotiable for specific applications. The real question is not whether the standard is voluntary. It’s whether your project specification has already made it mandatory without saying so explicitly.
The API 610 Contractual Cascade
API 610 editions 1 through 7 included mechanical seal specifications directly within the pump standard. Starting with the 8th Edition, API 610 deferred all seal specifications to API 682. That single editorial decision created the most powerful trigger for mandatory API 682 compliance in the industry.
Any purchase order calling for “pumps per API 610” now automatically invokes API 682 for the mechanical seal system. The cascade is contractual, not optional: pump specification references pump standard, pump standard references seal standard. An engineer who specifies API 610 pumps has already specified API 682 seals — whether the purchase order mentions API 682 or not.
Since API 610 is the globally dominant standard for centrifugal pumps in petroleum and petrochemical service, this cascade alone makes API 682 effectively mandatory for the majority of refinery and chemical plant pump installations. I’ve seen too many engineers assume they can substitute non-API seals on an API 610 pump — until the owner’s inspector shows up and asks for qualification test documentation.
This matters beyond new construction. Retrofit projects on existing API 610 pumps inherit the same cascade. Replacing a seal on a pump that was originally specified to API 610 means the replacement seal falls under API 682 scope — even if the original seal predates the standard. The contractual chain doesn’t expire with the first installation.
If your project specification references API 610, stop asking whether API 682 is mandatory. It already is.
What “Per API 682” Actually Invokes
Writing “per API 682” on a specification sheet is a three-word commitment that invokes hundreds of specific requirements. The standard operates on a default framework — it makes choices for you unless you explicitly opt out.
The Default Framework
Unless the purchaser indicates otherwise, API 682 pre-selects seal type, rotating or stationary configuration, seal arrangement, material combinations, piping plan, and instrumentation. The design philosophy targets at least three years of uninterrupted service while complying with emissions regulations. Every default stays active unless the purchaser’s data sheet specifically requests an alternative.
This opt-out design catches EPC contractors off guard. The API 682 4th Edition changed the default monitoring instrumentation from pressure switches to transmitters — a change described as “likely to be controversial and expensive.” Purchasers who preferred the older technology now must request switches in their specifications. The standard reversed the default, and anyone who wrote “per API 682 4th Edition” without reading the fine print accepted transmitters automatically.
Qualification Testing Obligations
API 682 compliance is not self-declared. A seal earns “per API 682” status only after passing qualification testing across five required test fluid groups: water, propane, caustic, cold oil, and hot oil. Test durations run up to 200 hours per seal type and medium variant. Hydrostatic testing requires holding 1.5 times the rated pump working pressure for a minimum of 30 minutes.
These are not guidelines. They are contractual obligations once the standard is invoked. An API 682-compliant seal that skips qualification testing in any of the five fluid groups is not API 682-compliant — regardless of how well it performs in the field.
Normative vs Informative: Which Requirements Are Binding
Some API 682 clauses are binding obligations; others are advisory guidance. The standard calls these normative (required) and informative (descriptive but not required). This distinction has not always been apparent to engineers reading the standard, and misunderstanding it leads to both over-specification and under-specification.
The “Shall” vs “Should” Distinction
Clauses using “shall” are mandatory once the standard is invoked. “Should” indicates a recommendation. Section 9.1.5 requires: “All controls and instruments shall be located and arranged to permit easy visibility by the operators.” Section 8.1.8 mandates: “Local operation, venting, filling, and draining shall be accomplished from grade.” These are binding obligations that extend well beyond the seal itself into the entire seal support system — piping, instrumentation, and accessibility.
Every connection point in a seal support system is a potential leak path and reliability risk in hydrocarbon service. API 682 now endorses tubing over welded pipe to minimize these connection points. Non-compliance with seal support system design constitutes a specification violation even if the seal itself meets every API 682 requirement.
Where Conservative Limits Create Confusion
API 682 type classifications create temperature envelopes that don’t always match actual material capabilities. Type A seals carry a temperature limit of 176 C, yet the FFKM o-rings used in these seals can withstand temperatures up to 327 C. The standard’s conservative limits serve as guardrails — they prevent edge-case failures across diverse applications rather than reflecting absolute material boundaries.
The API 682 standard specifies this for a reason. I’ve worked on Dowtherm service applications where engineers pushed beyond API 682 Type A limits because the materials could technically handle it. What they didn’t account for was Dowtherm degrading to form coke deposits at surprisingly low temperatures without oxygen present. The standard’s conservatism absorbed that risk. Ignoring it creates problems the material data sheet never warned about.
Why a “Voluntary” Standard Becomes Mandatory in Practice
The “API 682 is voluntary” framing is accurate at the standards-body level but fails the engineer who needs to know if their specific project requires compliance. The API 610 cascade is the most direct trigger, but at least three additional pathways make API 682 compliance practically unavoidable.
The Regulatory Floor
EPA Method 21 sets a fugitive emission threshold of 1,000 ppm by volume for rotating equipment. OSHA Process Safety Management requirements for hazardous service add another layer. Neither regulation names API 682 directly — but both create a performance floor that often necessitates API-grade sealing solutions.
Defective seals can leak 270 to 1,300 times the permitted emission rate while still passing basic air tests. That gap between “passes air test” and “meets emission limits in actual service” is exactly what API 682 qualification testing closes. A seal tested across five fluid groups for up to 200 hours provides documented evidence that it performs under realistic conditions — not just bench conditions.
When your plant must demonstrate emission compliance during an EPA audit, the qualification test documentation behind an API mechanical seal becomes your evidence trail. Without it, you’re defending seal selection with nothing but a manufacturer’s data sheet.
Owner and EPC Specifications
Major refinery and petrochemical operators maintain internal engineering standards that mandate API 682 regardless of what the pump standard says. These owner specifications typically apply to all rotating equipment in hydrocarbon service, not just API 610 pumps. EPC contractor specifications routinely include “per API 682” language as a baseline requirement across all seal applications.
The scope extends further than most engineers expect. API 682 applies not only to API 610 pumps but also to pumps designed to ASME B73.1, ASME B73.2, and API 676. If your facility runs any of these pump standards under an owner specification that references API 682, compliance is required across the fleet — not just on the API 610 units.
Cartridge mechanical seal designs are the standard format for API-compliant installations, and their pre-assembled configuration reduces the installation errors that cause the majority of premature seal failures. When an owner specification mandates API 682, the cartridge format is typically a practical necessity: field-assembled component seals introduce too many variables for reliable compliance.
Buffer Fluid and System Obligations
API 682 mandates a minimum 28-day refill interval for buffer or barrier fluid in Plan 53 systems. The standard covers the complete seal support system — from the piping plan configuration through instrumentation accessibility requirements. These system-level obligations surprise engineers who thought API 682 was just about the seal faces.
What the spec sheet doesn’t tell you is how far the “shall” requirements reach once invoked. Instrument visibility from grade level, connection minimization throughout the support piping, and specific refill intervals are all contractual commitments — not recommendations. Missing any one of them during a compliance audit constitutes a specification violation, even when the seal itself performs flawlessly.
The Bottom Line
API 682 is voluntary in the same way a building code is voluntary — until someone writes it into a contract. The standard becomes mandatory through the API 610 cascade, through emission regulations that demand its testing rigor, and through owner specifications that reference it by name. Asking “is API 682 mandatory” without specifying the project context is asking the wrong question. The right question: does my purchase order, directly or by reference, invoke any standard that points to API 682? For most refinery and petrochemical pump installations, the answer is already yes.
