Procurify is a cloud-based procure-to-pay platform that helps organizations control purchasing and spending. It combines procurement, accounts payable, expense management, and payment workflows — purchase request management, configurable approvals, PO generation, vendor management, budget enforcement, and real-time spend analytics. It integrates with NetSuite, QuickBooks, Sage Intacct, and Dynamics 365.
Power end-to-end data operations for your Procurify API with Nexla. Our bi-directional Procurify connector is purpose-built for Procurify, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Procurify or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Procurify workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to Procurify using the OAuth 2.0 Client Credentials (two-legged) flow. In this flow, Nexla authenticates directly as a server-side application using a Client ID and Client Secret—no user login or browser redirect is required. Before creating a Procurify credential in Nexla, you must generate these credentials in your Procurify account.
Your Procurify user account must have permission to manage Integrations settings. Contact your Procurify administrator if this permission needs to be granted to your account.
Follow these steps to generate the Client ID and Client Secret that Nexla will use to authenticate with your Procurify account:
Sign in to your Procurify account and navigate to Settings in the left navigation bar.
In the Tools section of Settings, select Integrations.
Locate the API item in the integrations list and click View.
Click Create Application to begin generating a new set of API credentials.
In the Description field, enter a meaningful label that identifies the integration (e.g., Nexla Integration). Then click Create Application to confirm.
Procurify will display your new Client ID and Client Secret. Copy and securely store both values immediately.
Important
The Client Secret is displayed only once and cannot be retrieved again after you close this screen. If the Client Secret is lost, you must delete the application and create a new one.
Note your Procurify Base URL—this is the full domain URL of your Procurify instance (e.g., https://mycompany.procurify.com). You will need this value when configuring the credential in Nexla.
For complete information about generating Procurify API credentials, refer to the How to Create API Credentials article in the Procurify Knowledge Base, and the Authenticate with OAuth section of the Procurify developer documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Nexla authenticates with Procurify using the OAuth 2.0 Client Credentials grant (two-legged OAuth flow). Nexla will automatically exchange your Client ID and Client Secret for a short-lived Bearer access token, which is then used to authorize all API requests. The token is valid for 24 hours and is refreshed automatically by Nexla as needed—no manual token management is required.
Enter your Procurify Client ID in the Client ID field. This is the unique public identifier assigned to the application you created in your Procurify Integrations settings. The Client ID identifies your application to the Procurify API and is not sensitive.
Enter your Procurify Client Secret in the Client Secret field. This is the confidential password paired with the Client ID. Treat the Client Secret as you would a password—do not share it in plaintext or store it in unsecured locations.
The Client Secret field is masked for security. Ensure you have the correct value available before entering it, as the Client Secret cannot be retrieved from Procurify after the initial creation screen is closed.
Enter your Procurify Base URL in the Base URL field. This is the full domain URL of your Procurify instance, including the https:// protocol prefix (e.g., https://mycompany.procurify.com). Nexla uses this value to construct all API endpoint URLs and to request the OAuth access token from your organization's token endpoint at https://[your-domain].procurify.com/api/v3/oauth/token.
The Base URL is unique to your Procurify organization. It typically follows the pattern https://[company-subdomain].procurify.com. Do not include a trailing slash at the end of the URL.
Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Procurify connector tile, then select the credential that will be used to connect to the Procurify instance, and click Next; or, create a new Procurify credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Procurify endpoints. Each template is designed specifically for the corresponding Procurify endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Get Available User Permissions
Retrieves the complete list of available permissions in your Procurify system. Use this endpoint to audit what permission types exist in your organization or to support role and access management reporting.
This endpoint retrieves all permission definitions available in your Procurify instance. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically iterate through all pages to retrieve the complete permission list.
Use this endpoint together with the Get Available System Roles endpoint to build a comprehensive view of your organization's access control structure.
Get Available System Roles
Retrieves the list of available system roles and permission groups defined in your Procurify instance. Use this endpoint to understand how roles are structured, which permissions are grouped together, and to support access control auditing or reporting.
This endpoint retrieves all role and permission group definitions from your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
System roles in Procurify define which actions users can perform across purchasing, approval, and financial workflows. This data is useful for compliance audits and access reviews.
List Users
Retrieves a paginated list of users in your Procurify account, including profile details, role assignments, and account status. Use this endpoint to sync user directories, audit user access, or populate downstream HR and identity management systems.
This endpoint retrieves all users visible to the authenticated application. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically retrieve all pages.
To retrieve only the profile for the currently authenticated API user (rather than all users), use the Get Logged-in User endpoint instead.
Get Logged-in User
Retrieves the profile information of the currently authenticated API user. This is useful for verifying the identity and permissions of the credentials being used by Nexla, or for capturing the API application's user details as part of an audit trail.
This endpoint returns a single user record for the application user associated with the configured Client ID and Client Secret. No additional configuration is required.
Unlike the List Users endpoint, this endpoint is not paginated—it returns a single object representing the authenticated user's profile.
Get Locations
Retrieves a paginated list of locations defined in your Procurify account. Locations represent physical office, warehouse, or site addresses used in purchase orders and shipment routing. Use this endpoint to sync location data into ERP systems or for reporting by location.
This endpoint retrieves all active locations in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
Location data includes billing and shipping address details and is commonly used to map Procurify purchase orders to physical sites in downstream ERP or accounting systems.
List Departments
Retrieves a paginated list of departments defined in your Procurify account. Departments are used to categorize spending, assign budget owners, and route purchase requests through appropriate approval workflows. Use this endpoint to sync department structures into reporting tools or ERP systems.
This endpoint retrieves all departments in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
Get Account Codes
Retrieves a paginated list of account codes (GL codes) defined in your Procurify account. Account codes are used to classify spending for financial reporting and are typically mapped to general ledger accounts in your accounting or ERP system. Use this endpoint to sync account code data for reconciliation or financial reporting purposes.
This endpoint retrieves all account codes in your Procurify instance. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
Account codes in Procurify correspond to general ledger (GL) codes in your accounting system. Syncing this data is useful when validating that Procurify's coding aligns with your ERP's chart of accounts.
Get Accounts
Retrieves a paginated list of accounts from your Procurify instance. Accounts represent financial tracking categories used across procurement and AP workflows. Use this endpoint to retrieve account data for budgeting analysis, financial reporting, or ERP synchronization.
This endpoint retrieves all accounts in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
List Vendors
Retrieves a paginated list of active vendors (suppliers) in your Procurify account, including contact details, payment terms, and vendor status. Use this endpoint to sync your vendor master data into ERP, accounting, or supplier relationship management systems.
This endpoint retrieves all active vendors in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
Vendor data from Procurify is commonly used to maintain a synchronized supplier master in ERP and accounting platforms. This ensures that purchase orders and invoices reference accurate vendor information.
Get Active/Inactive Currencies
Retrieves a list of currencies configured in your Procurify account, including both active and inactive currencies. Use this endpoint to reference currency definitions when building multi-currency spend reports or validating currency codes used in purchase orders and transactions.
This endpoint retrieves all currency records in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
Get All Catalog Bundles
Retrieves a list of all catalog bundles defined in your Procurify account. Catalog bundles are groupings of catalog items that can be purchased together, often used to standardize procurement of related goods or services. Use this endpoint to audit your catalog structure or sync bundle definitions into reporting tools.
This endpoint retrieves all catalog bundles in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
Get All Catalog Items
Retrieves a list of catalog items available in your Procurify account. Catalog items represent pre-approved products and services that users can select when creating purchase requests, helping to standardize purchasing and control spending. Use this endpoint to export the product catalog for analysis or ERP synchronization.
This endpoint retrieves all catalog items in your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
Catalog item data includes pricing, vendor assignments, and any custom field values set on each item. Use the Get All Catalog Bundles endpoint to retrieve the bundle groupings that catalog items belong to.
Get All Order Items
Retrieves a list of order items from the global orders view in Procurify, with extensive filtering options by status, date range, vendor, account, department, and other criteria. Use this endpoint to pull historical purchase request and order line-item data for spend analysis, budgeting, or ERP integration.
This endpoint retrieves order items from the global orders view (API v2). No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
This endpoint accesses the legacy global order items view. For the current v3 order items endpoint with additional filtering options, use the List Order Items endpoint instead.
Get All Orders
Retrieves a list of orders (purchase orders) from the global orders view in Procurify, with filtering options by status, date range, department, location, and other attributes. Use this endpoint to export order records for spend reporting, ERP synchronization, or audit purposes.
This endpoint retrieves purchase orders from the global orders view (API v2). No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 20 records per page. Nexla will automatically paginate through all available records.
List Order Items
Retrieves a paginated list of all order items using the current Procurify v3 API, with extensive filtering options. This is the preferred endpoint for retrieving order line-item data in modern integrations. Use it for spend analysis, procurement reporting, or syncing order details into ERP or data warehouse systems.
This endpoint retrieves order items using the Procurify v3 API. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
For additional details about Procurify order item fields and filtering parameters, refer to the Procurify API Reference.
List Company Payment Methods
Retrieves a paginated list of company payment methods configured in your Procurify accounts payable module. Use this endpoint to audit available payment options or to sync payment method data into your accounting or ERP system.
This endpoint retrieves all company-level payment methods from your Procurify AP module. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
List Unbilled/Billed Items
Retrieves a paginated list of unbilled and billed items from the Procurify accounts payable module. Use this endpoint to track invoice status, identify items awaiting billing, or export AP item data for reconciliation with your accounting system.
This endpoint retrieves AP items—both those that have been invoiced and those that are still awaiting billing. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
This endpoint is part of Procurify's accounts payable functionality. Use it in combination with the List Pay Transactions endpoint to build a complete view of the AP lifecycle from receipt to payment.
List Pay Transactions
Retrieves a paginated list of payment transactions recorded in Procurify. Use this endpoint to export payment history for cash flow analysis, audit trails, or synchronization with your accounting or ERP system.
This endpoint retrieves payment transactions from your Procurify account. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
List Receipt Items by Order Item
Retrieves a paginated list of receipt items recorded in Procurify for goods received against purchase orders. Use this endpoint to track receiving activity, support three-way matching (PO, receipt, invoice), or export receiving data for ERP synchronization.
This endpoint retrieves receipt items from Procurify's receiving module. No additional configuration is required beyond selecting this endpoint template.
Results are returned in paginated pages of up to 100 records per page. Nexla will automatically paginate through all available records.
Receipt items in Procurify record the quantity and pass/fail status of goods received against a specific order item. This data supports three-way matching workflows when combined with purchase order and AP invoice data.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be fetched and displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Procurify data sources can also be manually configured to ingest data from any valid Procurify API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations, such as applying additional query filters, chaining multiple API calls, or accessing endpoints available in Procurify's v2 or v3 API that are not yet included as templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Procurify API endpoint URLs follow the pattern https://[your-domain].procurify.com/api/[version]/[resource]/. For example, to retrieve departments, the URL would be https://mycompany.procurify.com/api/v3/departments/. Refer to the Procurify API Reference for a complete list of available endpoints and their URL patterns.
Most Procurify paginated list endpoints return data nested under a results array, so the correct path to data is $.results[*]—the pre-built endpoint templates are pre-configured with this path automatically. Date/time macros are particularly useful for Procurify endpoints that accept date parameters, such as order or AP item endpoints that can be filtered by date ranges, and lookup-based macros are useful when constructing requests that require specific IDs (such as a department ID, vendor ID, or order ID) sourced from another Nexla data source.
The Authorization: Bearer [token] header is automatically handled by Nexla based on your Procurify credential configuration and does not need to be added as a request header.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Procurify data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Procurify destination, and select the Send to Destination option from the menu. Select the Procurify connector from the list of available destination connectors, then select the credential that will be used to connect to the Procurify organization, and click Next; or, create a new Procurify credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Procurify endpoints. Each template is designed specifically for the corresponding Procurify endpoint, making destination setup easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create New User
Creates a new user account in Procurify with the specified profile details and optional role assignment. Use this endpoint to provision users programmatically—for example, when onboarding employees in bulk from an HR system or identity provider.
Ensure the Nexset being sent to this destination contains the required user fields as defined by the Procurify API. Required fields typically include first name, last name, email address, and username. Optional fields include role assignments and department associations.
Each record in the Nexset will be sent as a separate user creation request (one record per API call). Confirm that each record represents a distinct user to be created.
User email addresses must be unique within your Procurify account. Attempting to create a user with an email address already in use will result in an error response from the Procurify API. For complete information about required and optional user fields, refer to the Procurify API Reference.
Update User
Updates an existing user's profile information, permissions, and settings in Procurify by user ID. Use this endpoint to synchronize user attributes from a source system—for example, updating department assignments, roles, or contact details when employee records change in your HR system.
The Procurify user ID must be provided in the Nexset data to identify which user record to update. The user ID is appended to the API URL to target the correct record. Ensure that the Nexset includes a field mapped to the Procurify user ID before configuring this destination.
Use the Get Users data source endpoint to retrieve existing user IDs if needed.
The update operation is a full replacement (PUT)—all required user fields must be included in each record, not just the fields being changed.
Because this endpoint uses a PUT (full replacement) method, all required user fields must be present in each record sent to this destination. Sending partial records may result in missing data on the updated user profile.
Deactivate User
Deactivates or deletes an existing user account in Procurify by user ID. Use this endpoint to programmatically offboard users—for example, when an employee departure is recorded in your HR system and their Procurify access should be removed automatically.
The Procurify user ID must be provided in the Nexset data to identify which user account to deactivate. Ensure that the Nexset includes a field containing the Procurify user ID for each record to be processed.
Each record in the Nexset will trigger a separate deactivation request for the specified user ID.
:::warning Important
This operation removes the specified user's access to Procurify. Verify that the correct user IDs are being sent before activating this destination to avoid unintended deactivations.
:::
Create New Location
Creates a new location in Procurify with billing and shipping address details. Use this endpoint to provision office locations, warehouses, or other physical sites programmatically—for example, when opening a new facility and needing to add it to Procurify for purchase order routing.
Ensure the Nexset contains the required location fields, including location name and address details. Refer to the Procurify API Reference for a complete list of required and optional fields for location creation.
Each record in the Nexset will be sent as a separate location creation request.
Create New Department
Creates a new department in Procurify with the specified properties. Use this endpoint to programmatically build out your organizational hierarchy—for example, when adding new departments from an HR or ERP system.
Ensure the Nexset contains the required department fields, including the department name. Additional optional fields may include the department's branch or location association.
Each record in the Nexset will be sent as a separate department creation request.
Update Department
Updates an existing department in Procurify by department ID. Use this endpoint to keep department records in Procurify synchronized with your authoritative source—for example, when department names or structures change in your ERP or HR system.
The Procurify department ID must be included in the Nexset data to identify which department to update. The department ID is appended to the API URL for each request.
Use the List Departments data source endpoint to retrieve existing department IDs if needed.
This is a full replacement (PUT) operation—all required department fields must be present in each record.
Create Account Codes
Creates a new account code (GL code) in Procurify with the specified properties. Use this endpoint to sync your chart of accounts from an ERP or accounting system into Procurify, ensuring that purchasing teams can code expenses accurately at the point of request.
Ensure the Nexset contains the required fields for account code creation, including the account code name and code value. Refer to the Procurify API Reference for the full list of required fields.
Each record in the Nexset will be sent as a separate account code creation request.
Account codes in Procurify correspond to GL codes in your accounting or ERP system. Syncing these from your ERP ensures that Procurify users always have access to the most current coding options when submitting purchase requests.
Update Account Code
Updates an existing account code in Procurify by account code ID. Use this endpoint to keep GL codes synchronized between Procurify and your authoritative ERP or accounting system when account code names or properties change.
The Procurify account code ID must be included in the Nexset data to identify which record to update. The account code ID is appended to the API URL for each request.
Use the Get Account Codes data source endpoint to retrieve existing account code IDs if needed.
This is a full replacement (PUT) operation—all required account code fields must be present in each record.
Create Vendor
Creates a new vendor (supplier) in Procurify with the specified properties and contact information. Use this endpoint to maintain vendor master data in Procurify in sync with your ERP or supplier management system—ensuring that buyers can select correct vendor records when creating purchase requests and orders.
Ensure the Nexset contains the required vendor fields, including vendor name. Optional fields include contact details, payment terms, and address information.
Each record in the Nexset will be sent as a separate vendor creation request.
Vendor names should be unique within your Procurify account to avoid duplicate supplier records. Consider implementing deduplication logic in your Nexla flow before sending data to this destination.
Update Vendor
Updates an existing vendor in Procurify by vendor ID with new properties and contact information. Use this endpoint to keep vendor master records in Procurify synchronized with your authoritative source system when supplier details change.
The Procurify vendor ID must be included in the Nexset data to identify which vendor record to update. The vendor ID is appended to the API URL for each request.
Use the List Vendors data source endpoint to retrieve existing vendor IDs if needed.
This is a full replacement (PUT) operation—all required vendor fields must be present in each record sent to this destination.
Create Catalog Item
Creates a new catalog item in Procurify with pricing, vendor assignment, and custom field data. Use this endpoint to programmatically populate your Procurify product catalog—for example, syncing approved products from an ERP or product management system so that buyers can select them in purchase requests without manual entry.
Ensure the Nexset contains the required catalog item fields, including item name, unit price, and vendor assignment. Custom fields defined in your Procurify account can also be populated.
Each record in the Nexset will be sent as a separate catalog item creation request.
Catalog items in Procurify support custom fields that can be configured for your organization's specific needs. Confirm that any custom field values in the Nexset match the expected format for your Procurify account configuration.
Update Catalog Item
Updates an existing catalog item in Procurify by item ID with new pricing, vendor assignments, and other details. Use this endpoint to keep catalog pricing and attributes current—for example, syncing price updates from a vendor price list or product database.
The Procurify catalog item ID must be included in the Nexset data to identify which item to update. The item ID is appended to the API URL for each request.
Use the Get All Catalog Items data source endpoint to retrieve existing catalog item IDs if needed.
This is a full replacement (PUT) operation—all required catalog item fields must be present in each record.
Create Requisition
Creates a new purchase requisition in Procurify with line items, location, department, and a required delivery date. Use this endpoint to programmatically submit purchase requests—for example, when an automated system or integrated application needs to trigger a purchasing workflow in Procurify.
Ensure the Nexset contains all required requisition fields. Required fields typically include:
Line items: One or more items to be purchased, each with a name, quantity, and unit price.
Location: The Procurify location ID to which the items should be delivered.
Department: The Procurify department ID that will be charged for the purchase.
Required date: The date by which the items are needed.
Each record in the Nexset will be sent as a separate requisition creation request. Confirm that each record represents a complete, self-contained requisition.
Submitted requisitions enter the standard Procurify approval workflow configured for the specified department and location. Ensure that the location and department IDs included in the Nexset are valid and active in your Procurify account. Use the Get Locations and List Departments data source endpoints to retrieve valid IDs.
Revise Purchase Order
Revises an existing purchase order in Procurify with updated items, addresses, payment terms, and other details. Use this endpoint when purchase order details need to be modified after initial creation—for example, when quantities change, pricing is revised, or a delivery address is updated.
The Procurify purchase order ID must be included in the Nexset data to identify which purchase order to revise. The PO ID is appended to the API URL for each request.
Use the Get All Orders data source endpoint to retrieve existing purchase order IDs if needed.
This is a full replacement (PUT) operation—all required purchase order fields must be included in each revision request.
Each record in the Nexset will trigger a separate revision request for the specified purchase order.
:::warning Important
Revising a purchase order may affect downstream approval workflows or vendor-facing documents. Confirm the intended changes before activating this destination to avoid unintended modifications to in-progress purchase orders.
:::
Create Company Payment Method
Creates a new company payment method in the Procurify accounts payable module. Use this endpoint to programmatically add payment options—for example, when onboarding a new corporate credit card or bank account that should be available for processing AP payments in Procurify.
Ensure the Nexset contains the required fields for payment method creation. Refer to the Procurify API Reference for the complete list of required and optional fields.
Each record in the Nexset will be sent as a separate payment method creation request.
Create Receipt Item
Creates a receipt item for a specified order item, recording the quantity of goods received and whether they passed or failed inspection. Use this endpoint to programmatically record goods receipts—for example, when receiving confirmations are captured in a warehouse management system and need to be recorded in Procurify to support three-way matching.
Ensure the Nexset contains the required fields for receipt item creation, including:
Order item ID: The Procurify order item ID that the receipt is associated with.
Pass quantity: The quantity of items received that passed inspection.
Fail quantity: The quantity of items received that failed inspection (if any).
Each record in the Nexset will be sent as a separate receipt item creation request.
Receipt items link goods receipt events to specific purchase order line items in Procurify, enabling three-way matching between the purchase order, receipt, and supplier invoice. Use the List Order Items data source endpoint to retrieve the order item IDs needed for this destination.
Procurify destinations can be manually configured to send data to any valid Procurify API endpoint. Manual configuration is useful when the required operation is not covered by a pre-built template, when custom request parameters are needed, or when accessing newer Procurify API endpoints not yet included as templates. Using manual configuration, you can also configure Nexla to automatically send the response received from the Procurify API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Common methods for Procurify write operations include POST (create new records such as users, vendors, departments, and requisitions), PUT (full replacement updates of existing records, requiring all fields), PATCH (partial updates), and DELETE (removing or deactivating records). Procurify accepts data in JSON format for all write operations.
Procurify API endpoint URLs follow the pattern https://[your-domain].procurify.com/api/[version]/[resource]/. For update or delete operations, append the record ID to the end of the URL—for example, https://[your-domain].procurify.com/api/v3/vendors/[vendor_id]/. Refer to the Procurify API Reference for a complete list of available endpoints.
The Authorization: Bearer [token] and Content-Type: application/json headers are automatically handled by Nexla based on your Procurify credential configuration and do not need to be added as request headers.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Procurify endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Procurify until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
