API especIFicación 7-1 is the API eespecIFicaciónIFicación for covered rotary perforar stem elements used in the sarta de perforación and bottom-hole assembly, iNCluding portabrocass, heavy peso tubería de perforación, kellys, perforar stem subs, kelly valves and stabilizers. These components are not estándar tubería de perforación,they are used to add peso and stIFfness, transmit par, connect perforar-string sections, stabilize the BHA, or tensile, compressive and bending loads. The API especIFicación 7-1 estándar defines the main manufacturing, inespecIFicacióNCión, marking and release requirements for these products. In procurement documents, API especIFicación 7-1 helps convert product names such as portabrocas, HWDP or stabilizer into measurable ordering and acceptaNCe requirements.In practical use, API especIFicación 7-1 refers to the eespecIFicaciónIFicación designation used in RFQs, quotations, purchase orders and product descriptions. The API especIFicación 7-1 estándar refers to the complete technical document used to control production, inespecIFicacióNCión and entrega acceptaNCe.
For buyers, the key point is to apply the correct estándar to the correct product. API especIFicación 7-1 is used for covered rotary perforar stem elements. estándar tubería de perforación should normally be especIFicaciónIFied under API especIFicación 5DP, while rotary shouldered unión roscado and gauging should be reviewed under API especIFicación 7-2.
API SPEC 7-1 Latest Edition and Document Status
For procurement and inespecIFicacióNCión planning, the applicable edition of API especIFicación 7-1 should be confirmed before the RFQ or purchase order is issued. Current estándar-store records list API especIFicación 7-1, Rotary perforar Stem Elements, Second Edition, February 2023, with later updates iNCluding Errata 1, Addendum 1 and Errata 2. API’s official Errata 2 notice also identIFies the affected publication as API eespecIFicaciónIFicación 7-1, Rotary perforar Stem Elements, Second Edition, February 2023.
This edition check matters because the proveedor, buyer and third-party inespecIFicacióntor should work from the same controlled estándar basis. IF the purchase order only states “API 7-1” without edition or update requirements, acceptaNCe details may be interpreted dIFferently during production, inespecIFicacióNCión or final document review.
A clear RFQ should state the required API especIFicación 7-1 edition, applicable addenda or errata, product type, unión requirement, inespecIFicacióNCión scope and release documents. This keeps the material certIFicado, NDT report, dimensiónal inespecIFicacióNCión, unión gauging record and marking review aligned with the same estándar basis.
Products Covered by API SPEC 7-1
API especIFicación 7-1 covers selected rotary perforar stem elements used in the sarta de perforación and bottom-hole assembly. These products are not grouped only by name; they are controlled because they transmit par, add stIFfness or peso, connect dIFferent perforar-string members, stabilize the BHA, or provide a defined interface for perforación and coring tools.
For procurement, the important point is to confirm whether the ordered item is actually within the API 7-1 product scope, and then define the correct material, geometry, unión, inespecIFicacióNCión and release documents. A product name alone is not enough for technical acceptaNCe.
API SPEC 7-1, API SPEC 7-2 and API SPEC 5DP: Correct Stand
API especIFicación 7-1, API especIFicación 7-2 and API especIFicación 5DP are often mentioned together in perforar-string procurement, but they do not control the same part of the product. API especIFicación 7- applies to seleAPI especIFicación 7-2 controls rotarAPI especIFicación 5 applies to standa
The simplest way to separate them is this: API especIFicación 7-1 controls the covered perforación component, API especIFicación 7-2 controls the rotary shouldered unión, and API especIFicación 5DP controls estándar tubería de perforación.
A portabrocas, HWDP, kelly, sub or stabilizer may be ordered under API especIFicación 7-1, but its unión should still be checked according to API especIFicación 7-2 when a rotary shouldered unión is involved. estándar tubería de perforación should normally be especIFicaciónIFied under API especIFicación 5DP, because the tubería body, grado, PSL, upset ends, soldado unións and tubería de perforación entrega requirements belong to that estándar logic.
For HWDP, API especIFicación 7-1 should be used for the product body, material control, inespecIFicacióNCión and release requirements, while API especIFicación 7-2 should be especIFicaciónIFied for rotary shouldered unión roscado and gauging. For estándar tubería de perforación, API especIFicación 5DP should be used for the tubería body, grado, PSL, upset ends and soldado unións, while API especIFicación 7-2 should still be used for the unión. This prevents the proveedor, buyer and third-party inespecIFicacióntor from using dIFferent acceptaNCe criteria during production, inespecIFicacióNCión and final document review.
API 7-2 unión acceptaNCe should be supported by rosca gauging records and shoulder-condition checks. API 5DP tubería de perforación should iNClude tubería de perforación body, unión, weld-zone, grado, PSL and traceability records. This estándar separation makes the purchase order easier to inespecIFicaciónt and reduces disputes before shipment release.
RFQ and Standard Scope Review for API SPEC 7-1
Before issuing an RFQ or purchase order, the buyer should first confirm whether the ordered item belongs to API especIFicación 7-1 scope or another API estándar. API especIFicación 7-1 applies to covered rotary perforar stem elements such as HWDP, portabrocass, kellys, perforar stem subs and stabilizers. estándar tubería de perforación should normally be especIFicaciónIFied under API especIFicación 5DP, while rotary shouldered unión roscado and gauging should be controlled under API especIFicación 7-2.
This estándar separation is important because one perforar-string package may iNClude several dIFferent products. A estándar tubería de perforación line may require API especIFicación 5DP for the tubería body, grado, PSL, upset ends and soldado unións. An HWDP or portabrocas line may require API especIFicación 7-1 for product manufacturing, inespecIFicacióNCión, marking and entrega release. The unión on either product may still require API especIFicación 7-2 for rosca form, shoulder condition, dimensiónal conformity and gauging records.
The purchase order should not rely only on a general product name such as “portabrocas” or “HWDP.” It should state the applicable estándar edition, OD, ID, longitud, unión type, material grado, NDT scope, dimensiónal inespecIFicacióNCión, unión gauging requirement and final document package.
A practical RFQ line may be written as follows:
Heavy Weight Drill Pipe, API SPEC 7-1, 5 in OD, NC50 connection, welded or integral construction as specified, API SPEC 7-2 thread gauging required, NDT and dimensional inspection per approved ITP, MTC, heat-treatment record, hardness report, connection gauging record, final inspection report and packing list required.
For portabrocass, kellys, subs and stabilizers, the same logic applies: confirm the correct estándar first, then define the product geometry, unión requirement, inespecIFicacióNCión scope and release records. IF monograma API marking is required, it should be written as a separate purchase requirement rather than assumed from API 7-1 compliaNCe.
This approach helps the proveedor, buyer and third-party inespecIFicacióntor work from the same technical basis. It also reduces disputes during production, document review and shipment release, eespecIFicaciónially when API 7-1 products, API 5DP tubería de perforación and API 7-2 unións appear in the same order.
monograma API Marking and API especIFicación 7-1 CompliaNCe
API especIFicación 7-1 compliaNCe and monograma API marking are dIFferent purchase requirements.
API especIFicación 7-1 compliaNCe means the product is fabricaciónd, inespecIFicaciónted and released according to the applicable API 7-1 technical requirements. monograma API marking means the product is marked by an API-licensed fabricante within its approved license scope.
For procurement, the RFQ or purchase order should clearly state whether monograma API marking is required. IF monograma API is not required, the buyer should still request complete API 7-1 compliaNCe documents, iNCluding MTC, heat-treatment record, inespecIFicacióNCión reports, unión gauging record, marking verIFication and packing-list traceability.
API 7-1 AcceptaNCe Checks and Required Release Records
API 7-1 acceptaNCe is not only a document collection process. Each inespecIFicacióNCión item should prove that the delivered rotary perforar stem element matches the purchase order, the approved product scope and the agreed technical requirements. For buyers and third-party inespecIFicacióntors, the main purpose is to confirm three things before shipment release: the product is correctly identIFied, the critical manufacturing steps are controlled, and the final records are traceable to the same heat number, lot number and product marking.
The release package should show one continuous traceability chain: product marking → heat number → MTC → heat-treatment record → mechanical test report → dureza record → NDT report → dimensiónal inespecIFicacióNCión → unión gauging record → final inespecIFicacióNCión → packing list.
CoNClusion
API especIFicación 7-1 should be used as a practical purchasing and inespecIFicacióNCión basis for covered rotary perforar stem elements, not just as a estándar name in a quotation. For products such as HWDP, portabrocass, kellys, perforar stem subs and stabilizers, buyers should confirm the product scope, material grado, tratamiento térmico, dimensións, unión type, inespecIFicacióNCión requirements and final release documents before production starts.
The safest approach is to match each item with the correct estándar. API especIFicación 7-1 applies to covered rotary perforar stem elements, API especIFicación 7-2 should be used for rotary shouldered unión roscado and gauging, and API especIFicación 5DP should be used for estándar tubería de perforación. This avoids confusion between product-body requirements, unión requirements and tubería de perforación entrega requirements.
Before shipment release, the buyer should review a complete traceability package, iNCluding MTC, heat-treatment record, mechanical test report, dureza record, NDT report, dimensiónal inespecIFicacióNCión, unión gauging record, marking verIFication and packing list. When these records match the product marking and purchase order, the API 7-1 product can be inespecIFicaciónted, accepted and released with much less technical risk.
FAQ
Q: What is API SPEC 7-1 used for?
A: API SPEC 7-1 is used for rotary drill stem elements such as drill collars, HWDP, kellys, drill stem subs and stabilizers. It helps define product scope, material, manufacturing, inspection, marking and delivery requirements.
Q: What is the latest edition of API SPEC 7-1?
A: Current standard-store records list API Spec 7-1 as the Second Edition, published in February 2023, with Errata 1, Addendum 1 and Errata 2 updates included. Project teams should verify the controlled edition and updates before issuing a PO.
Q: Does API SPEC 7-1 cover standard drill pipe?
A: No. Standard drill pipe is normally specified under API SPEC 5DP. API SPEC 7-1 covers rotary drill stem elements such as HWDP, drill collars, kellys, subs and stabilizers.
Q: What is the difference between API SPEC 7-1 and API SPEC 7-2?
A: API SPEC 7-1 covers selected rotary drill stem elements as products. API SPEC 7-2 covers threading and gauging requirements for rotary shouldered connections.
Q: Should API Monogram be written in the purchase order?
A: Yes. If the project requires API Monogram marking, it should be stated clearly in the RFQ and PO. API 7-1 compliance and API Monogram marking are related, but they are not the same purchase requirement.
