API 510 vs API 570 — Pressure Vessel vs Piping Inspector Certification
API 510 certifies authorised pressure vessel inspectors; API 570 certifies authorised piping inspectors. Both are issued by the American Petroleum Institute Individual Certification Program (ICP). This comparison covers scope of work, exam structure, $730 examination fee, work-experience prerequisites, $85K-$140K salary range, and whether holding both certifications is worth the time.
Atlantis NDT Integrated Stack
Atlantis NDT delivers an integrated software + services stack to inspection contractors + EPC operators + asset owners globally. Atlantis NDT ERP (asset register + circuit hierarchy + ASNT + ISO 9712 + API ICP + AWS CWI + NACE CIP cert tracking + calibration cert + audit-ready records per ISO 9001 + 17020 + 17025), Digital Twin platform (3D asset model + damage-mechanism heat-map + RBI tier visualisation + FFS workflow), Reporting Software (mobile + offline field capture + code-aligned templates), Atlantis NDT LMS + Atlantis NDT Academy (inspector training pathway), 3D Scanning Services, Atlantis AI for NDT, CCS Inspection. Affordable, accessible, fully customizable.
Code Stack + Compliance
Audit-defensible records per ISO 9001:2015 + ISO 17020 (inspection body) + ISO 17025 (calibration lab) + ISO 17024 (personnel cert body). ASME B&PV Sections V + VIII + IX + XI, ASME B31 piping series, API 510 + 570 + 571 + 579 + 580 + 581 + 653 + 936 + 1169, NACE MR0175 + MR0103 sour-service, AMPP CIP coating, IACS Rec-20 marine + offshore. Dual-scheme inspector cert (ASNT NDT Level II/III + ISO 9712). ASNT NDT Level III final disposition + procedure approval on every engagement.
Delivery Model + Free Consultation
Three delivery models: On-site mobilisation 24-72h via Houston + Dubai + Mumbai + Singapore + London hubs; Remote procedure authoring + Level III sign-off (24-hour turnaround); Hybrid — local Level II + Atlantis Level III remote oversight. Atlantis NDT publishes no pricing — pricing varies by region, scope, delivery model, team size. Request your free 30-minute consultation with Atlantis NDT founder Anoop Rayavarapu (ASNT NDT Level III multi-method, API 653, ISO 9001 Lead Auditor). Tailored quote within 24 hours. Affordable, accessible, fully customizable.
Candidates earlier in the certification pathway can start at Atlantis NDT training and certification.
API 510 governs in-service pressure vessels and API 570 governs in-service process piping. They share a common structure — inspect, calculate corrosion rate, derive remaining life, set the next interval — but differ in the intervals themselves, in how the asset is subdivided for inspection, and in the certification the inspector must hold.
The most consequential difference is how each code organises the asset. API 510 treats a vessel as a single item with an internal or on-stream inspection interval capped at the lesser of one half remaining life or ten years, plus an external visual examination on its own cycle. API 570 divides a piping system into circuits and assigns each a class reflecting consequence of failure, then sets thickness and external visual intervals by class, with the highest-consequence class inspected most often. It also singles out locations that corrode faster than the circuit around them — injection points, mixing tees and soil-to-air interfaces — and gives them shorter, separately tracked intervals. An inspector certified to API 510 is not thereby qualified to sign API 570 work, and vice versa. Both codes permit intervals to be extended on a risk-based inspection assessment performed to API 580 and 581, provided the assessment is documented and periodically revalidated.
Source: API 510 Pressure Vessel Inspection Code: In-Service Inspection, Rating, Repair and Alteration; API 570 Piping Inspection Code: In-Service Inspection, Rating, Repair and Alteration of Piping Systems; API RP 574 Inspection Practices for Piping System Components; API RP 580 and API RP 581 for risk-based inspection.
| API 510 — pressure vessels | API 570 — process piping | |
|---|---|---|
| Asset treated as | A single vessel | Circuits, each assigned a class by consequence |
| Primary interval driver | Half remaining life, capped at ten years | Class-based caps, shortened by remaining life |
| External visual | On its own cycle, commonly five years | By class, commonly five or ten years |
| Accelerated locations | Nozzles, weld seams, vapour space | Injection points, mixing tees, soil-to-air interfaces, dead legs |
| Inspector certification | API 510 certified inspector | API 570 certified inspector |
| Interval extension | Risk-based inspection to API 580/581 | Risk-based inspection to API 580/581 |
| Repair and alteration | Governed by the code, with rerating provisions | Governed by the code, with rerating provisions |
Where the boundary between the two codes actually falls
In practice the argument is rarely about a vessel shell or a run of pipe. It is about the transition — the nozzle, the first flange, the attached small-bore connection — and getting it wrong means an item falls between two programmes and is inspected by neither.
The workable convention is to fix the boundary explicitly in the owner-user inspection programme rather than relying on each inspector's judgement. Once the boundary is written down, the nozzle neck, the flange face and the first circumferential weld all have an owner, and the handover is auditable.
The failure this prevents is specific and common: a small-bore branch on a vessel nozzle, too small to feature in the vessel scope and not captured in any piping circuit, corroding or fatiguing unwatched. Small-bore connections on vibrating service are a recognised leak source precisely because they sit in this gap.
Why API 570 subdivides and API 510 does not
A pressure vessel is a bounded item with broadly consistent service throughout. A piping system is not — a single system can run through changes in temperature, phase, velocity and geometry, each of which changes the corrosion regime. Averaging across it would produce a corrosion rate that describes no part of it.
Circuit definition is therefore the most consequential engineering judgement in a piping programme, and it is the one most often inherited unexamined. Circuits drawn at commissioning describe the plant as designed. After a revamp, a feedstock change or a new tie-in, the flow regime moves and the circuit boundaries no longer reflect the service.
Reviewing circuit definitions and CML placement when service changes is an explicit expectation of the code, and it is skipped often enough that it is worth treating as a standing item rather than a turnaround task.
Which certification an inspector actually needs
API 510, 570 and 653 are separate individual certifications with separate examinations and separate recertification cycles. Holding one does not confer the others, and an inspection signed by someone holding the wrong one is exposed regardless of the technical quality of the work.
This is distinct from NDT method certification. The technician performing the ultrasonic or radiographic examination is certified under the employer's written practice to ASNT SNT-TC-1A or ANSI/ASNT CP-189, at Level I, II or III for that method. The API inspector authorises and interprets the inspection; the NDT technician performs the examination; a Level III approves the procedure the technician works to.
Atlantis works the written practice and procedure side of this — building the practice, qualifying and approving procedures, and reviewing whether the credentials in a data package actually cover the work that was signed.
What is the main difference between API 510 and API 570?
The asset and the way it is subdivided. API 510 inspects a pressure vessel as one item on a single interval capped at ten years or half remaining life. API 570 divides piping into circuits, classes each by consequence of failure, and sets thickness and visual intervals by class, with shorter separately tracked intervals for injection points and other accelerated locations.
Can one inspector cover both vessels and piping?
Only by holding both certifications. API 510 and API 570 are separate examinations with separate recertification cycles, and holding one does not qualify the holder to sign work under the other. Many inspectors hold both, but the credential has to be verified against the specific asset class being signed.
Do both codes allow risk-based inspection to extend intervals?
Yes. Both permit interval extension on the basis of a risk-based inspection assessment performed to API 580 and API 581, provided the assessment is documented, approved by the owner-user, and revalidated periodically. RBI replaces the prescriptive cap with a consequence and likelihood judgement; it does not remove the requirement to justify the interval.
What are injection points and why does API 570 treat them separately?
Locations where a chemical is introduced into a flowing stream — inhibitor, neutraliser, water wash. Turbulence and local chemistry make them corrode substantially faster than the circuit around them, so the code assigns them their own shorter inspection interval and their own CMLs rather than letting the circuit average conceal the loss.
Where does the boundary between vessel and piping scope sit?
Wherever the owner-user inspection programme says it does, which is why it should be written down. The transition region — nozzle neck, first flange, attached small-bore connection — is where items fall between the two programmes and get inspected by neither, and small-bore branches on vibrating service are a recognised leak source for exactly that reason.
Does API 653 follow the same logic as these two codes?
The same logic, different asset and different intervals. API 653 governs aboveground storage tanks, with an external visual cycle and a much longer internal inspection interval reflecting the different failure consequence, plus tank-specific requirements for floor scanning, settlement survey and shell plumbness that have no analogue in the vessel or piping codes.
Frequently asked
Which corrosion rate should be used when short-term and long-term rates disagree?
The more conservative of the two. A short-term rate materially above the long-term rate means the service has changed, and an interval computed from the long-term rate is no longer defensible until the cause is understood.
Does a rerating require the same code that governs inspection?
Yes. Both API 510 and API 570 contain the rerating provisions for their own asset class, and a rerating has to be performed and documented under the applicable code, with the calculations retained in the permanent record.