Reference · built on requestConnectorInventory, WMS & procurement

Procurify

Purchase requisitions, purchase orders, vendor catalogs, and goods receiving via the Procurify REST API v3.

Request accessPricing ↗

About

Procurify is a cloud-based purchasing and spend management platform designed for mid-market organizations to control organizational spend. Its REST API v3 enables external systems to submit purchase requisitions, track approval routing workflows, generate and dispatch approved purchase orders, record physical receiving against packing slips, and reconcile vendor bills.

Through Fibric, an operator monitors inventory replenishment needs and pending procurement approvals in Procurify, proposing order requests or receiving records for purchasing manager approval.

This is a reference listing. It documents what Fibric would read from Procurify and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Order requests, spend line items, and approval states via GET /api/v3/order-requests/
  • Purchase orders, supplier terms, and delivery schedules through GET /api/v3/purchase-orders/
  • Vendor profiles, payment terms, and contact records from GET /api/v3/vendors/
  • Goods receiving records, received quantities, and packing slip notes via GET /api/v3/receivings/
  • Chart of accounts, department budgets, and expense code structures from GET /api/v3/chart-of-accounts/

Proposed actions

  • Target capability: propose creating an order requisition for purchasing workflow approval
  • Target capability: propose creating a draft purchase order for an approved requisition
  • Target capability: propose logging a receiving transaction against delivered purchase order lines
  • Target capability: propose updating vendor contact information or payment terms

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Automate inventory reorder requisition drafts

    When inventory levels hit defined reorder points, propose creating structured order requests in Procurify assigned to appropriate department budget codes.

    With Reorder Point, Purchase Order Draft

  • Log warehouse receiving for delivered purchase orders

    When physical shipments arrive at the dock, verify delivered quantities against open Procurify purchase orders and propose logging receipt records.

    With Receipt Variance, Inbound Delay

  • Chase unfulfilled vendor purchase orders

    Track open purchase orders approaching their promised delivery dates and propose vendor follow-up notices to verify shipping status.

    With PO Chase, Lead-Time Drift

Requirements

  • An active Procurify subscription with API access enabled on your company subdomain
  • An API client token generated by an administrator with permissions across Purchasing and Receiving
  • Valid chart of accounts and department identifiers configured in Procurify setup
Authentication
OAuth 2.0 Bearer token passed in the Authorization header to your company domain endpoint at {domain}.procurify.com.

Limits

  • The Procurify REST API enforces a rate limit of 100 requests per minute per client token
  • Order requests must satisfy mandatory custom fields configured in organizational procurement policies
  • Receiving logs cannot be modified once linked vendor bills are approved for payment

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Procurify ↗

Questions and answers

How does Fibric access our Procurify company instance?
Fibric connects via HTTPS to your unique Procurify subdomain at {domain}.procurify.com/api/v3/, authenticating with an OAuth 2.0 Bearer token generated by your administrator.
Can Fibric approve spending requests in Procurify?
Fibric does not approve spending requests autonomously. It submits purchase requests and surfaces pending approvals for authorized budget managers to review within established policies.
Does Procurify support partial goods receiving via API?
Yes. The /receivings/ endpoint allows recording partial shipment quantities against specific line items, marking received portions while keeping remaining line items open.
Ask about Procurify

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Procurify through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy