Marketplace

Bid project, package, invitation, bidder, form, submission, company, contact, file, and note operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 70 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

BIM model, viewpoint, estimating, estimate, cost-catalog, part, assembly, labor, and pricing operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 97 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Budget views, line items, modifications, changes, snapshots, forecasts, and reporting operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 53 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Change-order, change-event, direct-cost, and payment operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 75 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

RFQ, billing-period, subcontractor-invoice, requisition, payment, compliance, and commitment-export operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 62 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Commitment, purchase-order, work-order, contract line-item, and commitment change-order operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 70 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Company, office, program, role, trade, project-type, project-stage, and other company-setting operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 80 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Configurable tool, generic item, status, fieldset, configuration, and company permission operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 60 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Coordination issue, viewpoint, model, assignee, company, activity, attachment, and status operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 56 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Weather, accident, call, delay, delivery, dumpster, equipment, inspection, instruction, plan-revision, safety, visitor, and waste log operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 76 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Daily log headers, summaries, bulk updates, clones, manpower, work, productivity, quantity, note, and construction-report operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 41 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Company users, people, vendors, insurance, crews, departments, distribution groups, and permission-template operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 58 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Project users, people, vendors, memberships, assignments, distribution groups, insurance, and permission operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 60 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Drawing, photo, markup, layer, shape, document, revision, set, area, upload, and export operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 99 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Equipment, category, type, make, model, ownership, telematics, reading, service, attachment, and utilization operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 84 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Company and project managed-equipment, maintenance, model, type, category, make, attachment, log, and GPS operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 86 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Actual production quantity, material, and time-and-material entry, equipment, timecard, notification, attachment, and signature operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 43 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Timesheet, timecard, signature, time-type, rounding, task-code, and budget-configuration operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 81 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Currency, tax, unit-of-measure, and related construction-financial configuration operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 33 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Incident filters, types, severity levels, hazards, conditions, behaviors, work activities, and configuration operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 89 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Incident, injury, near-miss, environmental, property-damage, action, witness, attachment, and alert operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 61 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Checklist schedule, attachment, change-history, and filter operations. Generated from a point-in-time SHA-256 inventory of 610 official Procore OpenAPI resource documents retrieved 2026-07-20. This pack carries 18 of the suite's 2805 admitted operations. The vendor publishes the resources as separate moving documents, so this composition deliberately carries no misleading single-document OpenAPI pin. Enroll one production OAuth authorization-code connection for the fixed https://api.procore.com origin. Supply the documented Procore-Company-Id header when an operation requires it. Reads are uncached and are marked sensitive-read where the response can carry directory, financial, or personnel detail; every mutation requires approval, beta endpoints are labeled, and unsafe JSON response integers are preserved as strings. OAuth/token lifecycle, support PINs, BIM mint tokens, multipart-only requests, and the deferred beta Document Management v2 surface are excluded. No task, note, or project Source is claimed without the guide-mandated live field-path verification.

Complete callable PagerDuty REST API suite pinned to the official OpenAPI document: all 465 method/path operations with no exclusions. The compatibility root keeps all 14 prior operation IDs and wire routes while seven dependency packs carry 451 additional operations. Reads are uncached; sensitive reads are marked sensitive-read. Mutations are grant-off and approval-gated, with administrative and destructive changes requiring approval every run. JSON int64 values remain exact. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base.

PagerDuty enrichment integrations and schemas, automation actions, SRE Agent, templates, and workflow integrations. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

PagerDuty event orchestrations, enrichments, alert grouping, rulesets, and change events. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

PagerDuty incidents, incident workflows, incident types, custom fields, log entries, paused reports, priorities, and recommendations. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

PagerDuty users, schedules, schedule v3 resources, escalation policies, notifications, OAuth delegations, and licenses. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

PagerDuty services, business services, teams, dependencies, service custom fields, tags, abilities, and vendors. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

PagerDuty status pages and dashboards, webhooks, add-ons, extensions, and extension schemas. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

Transactional workflow pack for turning one single-item intake into one paid, reviewed, and delivered PDF. Core Seller may hold a separate outcome-offer row established through granted `core.seller.*` operations, but this pack, publisher, and version are distribution provenance only and never Seller identity or authority; the workflow creates no customer token, entitlement, or usage row. The saved exact-form origin defaults Seller registration off. Only an explicitly enabled run may create one exact core Seller draft and one-way attach an unlinked creator-owned row to the exact saved recipe before order/provider writes; it cannot activate, redirect, edit the offer definition, or put payment state in Seller. The core.seller.order row is the single durable fulfilment lifecycle record, surfaced owner-side in Settings -> Seller -> Orders; no member maintains task projections or shared-state rows. The exact-form origin crash-safely creates or recovers one Stripe Checkout Session and sends one checkout-link email behind a durable ambiguity fence. Checkout-link and delivery subject/body copy are bounded owner-authored recipe variables rendered only through closed placeholders; AI never writes customer communications. New sends pin the exact rendered subject with the core-derived opaque provider identity before dispatch, while legacy installed recipes and already-fenced rows retain their fixed-subject fallback. The attended mail reconciler may clear only one exact Sent identity, recipient, pinned-or-legacy subject, and timestamp match; legacy identity-free fences and all non-matches remain no-resend owner work. An owner-attended payment sweep lists orders awaiting payment, fresh-reads each order's own attached Session, and advances only exact complete-and-paid source truth through core.seller.order.confirm-payment, whose server fences re-verify the correlation and exact amount per order; the sweep is manual, so installation performs no provider read, and it never initiates money movement or touches Seller access. One separate manual reconciler closes an order as refunded only from an exact owner-selected Refund locator plus fresh Refund and PaymentIntent proof of a succeeded FULL refund of exactly that order's recorded payment, through core.seller.order.confirm-refund - the only way an order reaches refunded. A second attended inspector accepts one exact Dispute locator, fresh-reads the Dispute and the order's recorded PaymentIntent, and renders only bounded scalar source truth against the order's own amount; it never searches, aggregates, creates dispute state, calls a write/action operation, notifies, changes workflow state, references or renders evidence fields, or exposes a dispute action. V4 payment alone authorizes neither generation nor delivery before exact owner review and D-199 promotion. Static generation remains the default. Optional AI generation uses a source-checked attended-owner capability to re-read the row, canonical D-199 response, and template before server-deriving the selected mode. It may also source-check and pin one owner-selected local PDF or DOCX under 10 MiB. Docling receives only the closed core-pinned ref/hash carrier and converts its verified bytes into run-scoped Markdown; one hard-bounded nonempty template summary and, when a reference is selected, one hard-bounded nonempty reference summary join the existing bounded response projection under effective content declarations, while raw reference bytes, converted Markdown, and model key-point structures never enter durable workflow state or the strict renderer. Only one bounded escaped ai.draft scalar enters deterministic rendering. Authenticated exact-file cards route server-derived response/hash pins into source-checked owner approve-and-send, regenerate, reject, cancel, and mail-recovery actions. Approve-and-send re-reads the immutable D-199 recipient, uncached Stripe source truth, and exact durable PDF, then pins the artifact, rendered subject, sender, and opaque provider reconciliation identity before one attachment-bearing mail attempt. Every live mail adapter carries that identity. Delivery reconciliation retains its stronger exact attachment-byte match. Concrete duplicate-header, multiple-message, or source-mismatch evidence moves sending to durable ambiguous owner work without authorizing resend; repeated ambiguity does not churn state, and later exact proof may complete the same fence. Not-found or unavailable evidence preserves the current sending or ambiguous state, while stale or conflicting evidence fails closed. The attended delivery reconciler settles the checkout-link and delivery mail claims against the Sent collection through the same general fence; a claim that was never written is reported per leg, never resent. Regeneration retains the reviewed PDF before releasing its current pin and rendering fresh bytes. Cancellation does not refund payment. Automatic mail reconciliation, refund initiation, dispute lifecycle/action automation, and manual resend or source override remain disabled; partial or multiple dispute inspection is observational only.

Optional verified-event accelerator for Paid Document Fulfillment. Install and bind it separately; the base pack remains inert. A checkout completion reaches paid only through core.seller.order.confirm-payment after a fresh Session read; a refund closes the order only after fresh Refund and PaymentIntent reads prove one succeeded full refund. The order row is the single lifecycle record (Settings -> Seller -> Orders). Event snapshot fields are never transition authority.

One-install PandaDoc front door over two bounded domain packs and five existing document workflows. The suite publishes 123 executable catalog operations covering 116 of 127 unique operations from PandaDoc's immutable official OpenAPI at commit 81beb8c87a80528882ff6dfa0b57fdf6b17f1c08. This 12-operation compatibility root preserves every prior operation ID, effective route, result shape, approval behavior, and single-page bound while dependencies add 111 operations. Seven deliberate aliases provide five complete collection walks plus URL and template branches for the two union-shaped create routes. Eleven fail-closed exclusions cover the OAuth credential exchange, seven multipart/query-marker upload routes, one required DELETE body, and two deprecated v1 log routes. Coverage spans documents, recipients, fields, attachments, downloads, reminders, sections, settings, templates, content, contacts, folders, members, logs, webhooks, notary, catalog, workspaces, and users. The upgrade repairs origin/path composition, documentary requiredness, stale entity claims, binary file capture, complete pagination, and exact integer parsing. OAuth bearer credentials remain connection-owned; a manually enrolled API-Key authorization connection can supply the same ingredient. Existing workflow reads and writes retain their approval behavior, while every new mutation requires approval. No Source is claimed without live field-presence proof.

PandaDoc templates, content-library items, forms, folders, contacts, members, logs, webhooks, notary, product catalog, workspaces, users, and communication preferences. Generated from PandaDoc's immutable official OpenAPI at commit 81beb8c87a80528882ff6dfa0b57fdf6b17f1c08. This leaf carries 58 of the suite's 123 catalog operations over 116 unique admitted routes. The ingredient uses the origin-only API base and the official full /public/v1, /public/v2, and /public/beta paths. JSON requests expose documentary top-level fields; union endpoints are split into required branch aliases; multipart upload variants remain excluded in favor of URL-backed JSON routes. Binary GET responses become private file_refs, unsafe JSON integers remain exact strings, reads are uncached, and every mutation is approval-gated.

Workflow pack for Recued-sent PandaDoc documents. It composes the PandaDoc capability pack with a closure ledger: send one draft or approved document through the existing PandaDoc approval gate, persist only the document/template linkage in data.shared, and let a scheduled watcher re-read that exact document until PandaDoc reports completion, exception, or an approval-complete state that needs the owner to send again. This pack does not duplicate PandaDoc auto reminders, manual reminders, auto-expiration, webhook administration, or general document status dashboards; it adds Recued-visible closure state for documents Recued sent.

PandaDoc document lifecycle, recipients, fields, attachments, reminders, sections, settings, downloads, linked CRM objects, quotes, and beta document intelligence. Generated from PandaDoc's immutable official OpenAPI at commit 81beb8c87a80528882ff6dfa0b57fdf6b17f1c08. This leaf carries 53 of the suite's 123 catalog operations over 116 unique admitted routes. The ingredient uses the origin-only API base and the official full /public/v1, /public/v2, and /public/beta paths. JSON requests expose documentary top-level fields; union endpoints are split into required branch aliases; multipart upload variants remain excluded in favor of URL-backed JSON routes. Binary GET responses become private file_refs, unsafe JSON integers remain exact strings, reads are uncached, and every mutation is approval-gated.

V2 one-install PayPal front door over 13 immutable source-pinned feature packs. The visible compatibility root grows from 21 to 70 operations while preserving every established operation ID, route, argument, entity, risk, approval, result-path, and cache contract; compatibility hardening adds recursively closed requests, explicit required empty JSON bodies, and lossless unsafe-integer responses. The installed family publishes 109 catalog operations covering 105 of 115 unique official routes, including 4 useful complete-page-walk aliases; 10 multipart, inbound-callback, internal-scope, or provider-prose-deprecated routes fail closed. Root additions are action-only so the established read surface does not silently widen default grants; remaining reads and one reserved action per source stay in the dependency leaves. Every new mutation requires approval, reads are uncached and not approval-gated, money movement and irreversible financial decisions are destructive, and supported POST retries require caller-owned PayPal-Request-Id values. Bearer authorization and merchant/partner identity headers remain connection-owned, Prefer is binding-owned, JSON Patch arrays use bounded verbatim JSON, projected JSON is recursively closed, and unsafe response integers stay exact. This root intentionally omits a misleading single openapi_source because PayPal publishes thirteen independent contracts; each dependency leaf carries its exact hash pin and the generated audit fixture reconciles every root route. No workflow or work-entity Source is claimed over financial or control-plane records.

PayPal billing plans, pricing, subscriptions, lifecycle controls, captures, and subscription transactions. Generated from PayPal's immutable commit-pinned Subscriptions OpenAPI 1.8. This source-pinned leaf carries 2 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal catalog product creation, lookup, listing, and controlled updates. Generated from PayPal's immutable commit-pinned Catalog Products OpenAPI 1.0. This source-pinned leaf carries 2 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal checkout order creation, updates, payment confirmation, authorization, capture, and shipment tracking. Generated from PayPal's immutable commit-pinned Orders OpenAPI 2.32. This source-pinned leaf carries 1 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal dispute detail, status, escalation, adjudication, evidence requests, and settlement offers. Generated from PayPal's immutable commit-pinned Disputes OpenAPI 1.11. This source-pinned leaf carries 1 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal invoice and template reads, lifecycle actions, payment and refund records, and QR or number generation. Generated from PayPal's immutable commit-pinned Invoices OpenAPI 2.6. This source-pinned leaf carries 5 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal partner onboarding referrals and referral status retrieval. Generated from PayPal's immutable commit-pinned Partner Referrals OpenAPI 2.5. This source-pinned leaf carries 2 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal web experience profile listing, detail, creation, replacement, patch, and deletion. Generated from PayPal's immutable commit-pinned Payment Experience Web Profiles OpenAPI 1.3. This source-pinned leaf carries 3 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal payment authorization, reauthorization, capture, void, refund, and eligible-method operations. Generated from PayPal's immutable commit-pinned Payments OpenAPI 2.12. This source-pinned leaf carries 2 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal batch payout creation, batch and item detail, and unclaimed-item cancellation. Generated from PayPal's immutable commit-pinned Payouts OpenAPI 1.9. This source-pinned leaf carries 3 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal transaction reporting with a complete page-walk alias over the established compatibility search. Generated from PayPal's immutable commit-pinned Transaction Search OpenAPI 1.9. This source-pinned leaf carries 1 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal transaction shipment-tracking creation, list, detail, and update; the provider-prose-deprecated batch-create route is excluded. Generated from PayPal's immutable commit-pinned Shipment Tracking OpenAPI 1.9. This source-pinned leaf carries 3 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.

PayPal customer payment-token and setup-token creation, listing, retrieval, and deletion. Generated from PayPal's immutable commit-pinned Payment Method Tokens OpenAPI 3.4. This source-pinned leaf carries 4 of the installed family's 109 catalog operations; the family covers 105 of 115 unique official routes with 10 exact fail-closed exclusions. Bearer authorization and merchant/partner identity remain connection-owned, new reads are uncached and not approval-gated, every mutation requires approval, documented PayPal-Request-Id values are mandatory for supported mutation retries, JSON inputs are bounded, and unsafe response integers remain exact strings. No financial or control-plane object is misrepresented as a task, note, or project Source.