Overview
A typed Procore adapter for Bun and AbsoluteJS applications. Authentication is supplied by the caller; use Citra's procore provider and Absolute Auth's encrypted grants/coordinated refresh for OAuth.
Procore
@absolutejs/procorev0.2.0betaCommerce & GrowthTyped Procore catalog and delivery-log adapter with bounded transport and explicit uncertain write outcomes.
#Installation
BASH
bun add @absolutejs/procore#Capabilities
Overview
A typed Procore adapter for Bun and AbsoluteJS applications. Authentication is supplied by the caller; use Citra's procore provider and Absolute Auth's encrypted grants/coordinated refresh for OAuth.
Supports companies, projects, project users/vendors/locations, cost codes, purchase orders, commitment contracts, and delivery-log reads/creation. Catalog results deliberately contain only the fields required for explicit mapping. Imported users do not grant application permissions.
Requests use fixed Procore origins, company headers, explicit project IDs, bounded response bodies and pagination, and reject redirects. Provider-supplied pagination URLs are never followed with credentials. Incomplete, duplicate, or capped catalogs fail instead of silently returning partial results. Callers remain responsible for authorization and matching a selected project to its company.
Show 4 more
ProcoreError exposes a sanitized code and outcome. An unknown write outcome means the request may have succeeded: do not automatically retry it. Persist intent before creating a delivery log, include a stable tracking number, and reconcile the receipt using an explicit log date. The adapter does not promise provider idempotency or automatically approve logs. It does not calculate business quantities, select mappings, or enforce a customer's approval policy.
The access-token callback must implement its own bounded execution. HTTP requests default to 15 seconds, 4 MiB, 20 pages, and 10,000 items. Sandbox and the default production API origin are supported; region-specific production routing needs separate configuration work before deployment to a regional tenant.
API contracts: Procore REST reference, OAuth endpoints, daily logs.
Run bun run typecheck, bun test, and bun run build.
Delivery files
uploadFile(companyId, projectId, {name, contentType, bytes}) supports PDF, JPEG, PNG and UTF-8 plain text up to 2 MiB. It obtains project-scoped Procore upload instructions and sends signed form fields and file bytes to the returned S3 destination without an OAuth header. Redirects and non-S3 destinations are rejected. It returns the upload ID for DeliveryLogInput.uploadIds. Unassociated uploads may expire; persist your upload receipts and associate them promptly. An interrupted upload may leave an orphan; it does not establish a delivery log.
Delivery writes require timeHour and timeMinute. Use the reviewed date/time and retain the time zone in your business snapshot. Receipts expose attachment names, record IDs, and upload IDs when identifiable from Procore download paths; signed download URLs are omitted. Missing attachment identity must not be treated as proof of a matching attachment. signal cancels in-flight requests and prevents sends after asynchronous credential resolution.
Outcomes
What you can build
Delivery files
uploadFile(companyId, projectId, {name, contentType, bytes}) supports PDF, JPEG, PNG and UTF-8 plain text up to 2 MiB. It obtains project-scoped Procore upload instructions and sends signed form fields and file bytes to the returned S3 destination without an OAuth header. Redirects and non-S3 destinations are rejected. It returns the upload ID for DeliveryLogInput.uploadIds. Unassociated uploads may expire; persist your upload receipts and associate them promptly. An interrupted upload may leave an orphan; it does not establish a delivery log.
Hardening checklist
Production guidance
Make every external boundary explicitPin the deployed @absolutejs/procore version, replace example or memory-backed dependencies with durable implementations, bound external calls, protect credentials, and emit enough evidence to retry or recover safely.
Follow in order
Troubleshooting path
1
Trace from the first failed boundary
Reproduce the smallest canonical @absolutejs/procore example, confirm the supported entry point and version in the API explorer, then inspect the first boundary that did not produce its documented result.
#@absolutejs/procore quick start
Partial snippet# @absolutejs/procore
TS
import { createProcoreClient } from "@absolutejs/procore";
const procore = createProcoreClient({
environment: "sandbox",
accessToken: async () => tokenFromYourCredentialResolver,
});
const projects = await procore.projects(selectedCompanyId);
const logs = await procore.deliveryLogs(
selectedCompanyId,
selectedProjectId,
"2026-10-07",
);#Public entry points
Supported entry points declared by this project’s package manifest. Internal dist paths are not part of the package contract.
@absolutejs/procorePublic package entry point declared in package.json.
#Package commands
Scripts declared by this project’s package manifest.
bun run buildbun build src/index.ts --outdir dist --target=bun && tsc -p tsconfig.build.json
bun run testbun test
bun run typechecktsc --noEmit
#API reference
Search the declarations exported by the current package type files. Expand a symbol to inspect its source-backed signature.
12 symbols
TS
class ProcoreError extends Error {
readonly code: string;
readonly outcome: "rejected" | "unknown";
readonly httpStatus?: number | undefined;
constructor(code: string, outcome?: "rejected" | "unknown", httpStatus?: number | undefined);
}@absolutejs/procore