Skip to main content

Precoro Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Precoro location. Use the Precoro destination connector to create purchase requisitions, manage suppliers, create and update inventory items, record payments, manage taxes and payment terms, and more — directly from your Nexla data flows.
precoro_api.png

Precoro

Create a Precoro Destination​

  1. Click the + icon on the Nexset that will be sent to the Precoro destination, and select the Send to Destination option from the menu.

  2. Select the Precoro connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Precoro organization, and click Next; or, create a new Precoro credential for use in this flow.

  3. In Nexla, Precoro destinations can be created using pre-built endpoint templates, which expedite destination setup for common Precoro endpoints. Each template is designed specifically for the corresponding Precoro endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Precoro destinations can also be configured manually, allowing you to send data to Precoro endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Precoro endpoints. Each template is designed specifically for the corresponding Precoro endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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 Purchase Requisition

    Create a new purchase requisition in Precoro. Use this endpoint to programmatically submit purchase requests from an external system — for example, when integrating an ERP, e-commerce platform, or expense management tool with your Precoro procurement workflow.

    • Ensure that the Nexset data contains the required fields for a Precoro purchase requisition before activating this destination. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user's roles and permissions in Precoro apply to requisitions created via the API. Ensure the API key was generated under a user account with permission to create purchase requisitions.

    For details about the required and optional fields for creating a purchase requisition via the Precoro API, refer to the Precoro Purchase Requisitions API documentation.

    Add Invoice Payment

    Create a new payment for an invoice in Precoro. Use this endpoint to record invoice payments from an external accounting system or payment processor, keeping your Precoro payment records in sync with your financial systems.

    • Ensure that the Nexset data contains the required payment fields, including the invoice reference and payment amount, before activating this destination. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user must have permission to record payments in Precoro. Ensure the API key was generated under a user account with the appropriate financial permissions.

    For details about the required and optional fields for creating an invoice payment via the Precoro API, refer to the Precoro Payments API documentation.

    Add Expense Payment

    Create a new payment for an expense in Precoro. Use this endpoint to record expense payments from an external system, such as an expense management tool or corporate card platform, keeping your Precoro expense records up to date.

    • Ensure that the Nexset data contains the required payment fields, including the expense reference and payment amount, before activating this destination. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user must have permission to record expense payments in Precoro.

    For details about the required and optional fields for creating an expense payment via the Precoro API, refer to the Precoro Payments API documentation.

    Cancel Payment by IDN

    Cancel an existing payment in Precoro by its IDN (internal document number) identifier. Use this endpoint when a payment must be voided or reversed due to an error, duplicate entry, or change in payment status from an external system.

    • Enter the IDN identifier of the payment to cancel in the Payment IDN field. This field is required. The IDN is a unique identifier assigned to each payment in Precoro and can be obtained from the Precoro UI or via the Get Payments source endpoint.
    • The authenticated user must have permission to cancel payments in Precoro. Cancellation via the API follows the same authorization rules as cancellation in the Precoro UI.

    For details about payment cancellation via the Precoro API, refer to the Precoro Payments API documentation.

    Create Supplier

    Create a new supplier in Precoro with a name and optional contact email addresses. Use this endpoint to automate supplier onboarding from an external vendor management system, ERP, or onboarding workflow.

    • Ensure that the Nexset data contains at least the supplier name before activating this destination. Contact email addresses are optional but recommended for supplier communication tracking. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user must have permission to create suppliers in Precoro.

    For details about the required and optional fields for creating a supplier via the Precoro API, refer to the Precoro Suppliers API documentation.

    Update Supplier

    Update an existing supplier's name and contact information in Precoro by supplier ID. Use this endpoint to keep supplier records in Precoro synchronized with an external vendor management system or master data management platform.

    • The supplier ID is embedded in the API endpoint URL for this template. Ensure that the Nexset data contains the correct supplier ID along with the updated name and contact information. The payload is sent as a JSON body in a PUT request to the Precoro API.
    • Supplier IDs can be obtained from the Precoro UI or via the List Suppliers source endpoint.
    • The authenticated user must have permission to update supplier records in Precoro.

    For details about the required and optional fields for updating a supplier via the Precoro API, refer to the Precoro Suppliers API documentation.

    Reject Supplier by ID

    Reject a supplier by marking it as rejected in the Precoro approval process. Use this endpoint to programmatically handle supplier rejection decisions from an external approval workflow or vendor screening system.

    • Enter the ID of the supplier to reject in the Supplier ID field. This field is required. Supplier IDs can be obtained from the Precoro UI or via the List Suppliers source endpoint.
    • The authenticated user must have permission to reject suppliers in Precoro. This action follows the same authorization rules as supplier rejection in the Precoro UI.

    Create Item

    Create a new inventory item in the Precoro catalog. Use this endpoint to automate item creation when synchronizing a product catalog, ERP item master, or procurement catalog with Precoro.

    • Ensure that the Nexset data contains at least the item name before activating this destination. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user must have permission to create items in Precoro.

    For details about the required and optional fields for creating an item via the Precoro API, refer to the Precoro Items API documentation.

    Update Item

    Update an existing inventory item in the Precoro catalog by item ID. Use this endpoint to keep your Precoro item catalog synchronized with an external product catalog or ERP item master.

    • Enter the ID of the item to update in the Item ID field. This field is required. Item IDs can be obtained from the Precoro UI or via the List Items source endpoint.
    • Ensure that the Nexset data contains the updated item name and any other fields to be modified. The payload is sent as a JSON body in a PUT request to the Precoro API.
    • The authenticated user must have permission to update items in Precoro.

    For details about the required and optional fields for updating an item via the Precoro API, refer to the Precoro Items API documentation.

    Create Payment Term

    Create a new company payment term in Precoro. Payment terms define the conditions under which a supplier invoice is expected to be paid (e.g., Net 30, Net 60). Use this endpoint to synchronize payment terms from an external financial system or ERP.

    • Ensure that the Nexset data contains the payment term name before activating this destination. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user must have permission to manage payment terms in Precoro.

    For details about the required and optional fields for creating a payment term via the Precoro API, refer to the Precoro Payment Terms API documentation.

    Update Payment Term

    Update an existing company payment term in Precoro by payment term ID. Use this endpoint to keep payment term definitions in Precoro synchronized with an external financial system or ERP.

    • Enter the ID of the payment term to update in the Payment Term ID field. This field is required. Payment term IDs can be obtained from the Precoro UI or via the Precoro API.
    • Ensure that the Nexset data contains the updated payment term name. The payload is sent as a JSON body in a PUT request to the Precoro API.
    • The authenticated user must have permission to manage payment terms in Precoro.

    For details about the required and optional fields for updating a payment term via the Precoro API, refer to the Precoro Payment Terms API documentation.

    Add Tax

    Create a new tax configuration in Precoro. Use this endpoint to synchronize tax rates and categories from an external tax management system or ERP, ensuring that Precoro's procurement documents apply the correct tax configurations.

    • Ensure that the Nexset data contains the tax configuration name before activating this destination. The payload is sent as a JSON body in a POST request to the Precoro API.
    • The authenticated user must have permission to manage tax configurations in Precoro.

    Update Tax by ID

    Update an existing tax configuration in Precoro by tax ID. Use this endpoint to keep Precoro tax configurations synchronized with an external tax management system or ERP.

    • Enter the ID of the tax configuration to update in the Tax ID field. This field is required. Tax IDs can be obtained from the Precoro UI or via the Get Tax List source endpoint.
    • Ensure that the Nexset data contains the updated tax name. The payload is sent as a JSON body in a PUT request to the Precoro API.
    • The authenticated user must have permission to manage tax configurations in Precoro.

Configure Manually​

Precoro destinations can be manually configured to send data to any valid Precoro API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Precoro API after each call to a new Nexla webhook data source.

The Precoro API base URL is https://api.precoro.com. The Precoro API enforces rate limits of 60 requests per minute, 1,500 per hour, and 3,000 per day. For information about available Precoro API endpoints and their required request body fields, refer to the Precoro API documentation.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Precoro API from the Method pulldown menu. Common methods for Precoro destination operations include:

    • POST: For creating new records (purchase requisitions, suppliers, payments, taxes, etc.)
    • PUT: For replacing or fully updating existing records by ID
    • DELETE: For removing records when supported by the endpoint

Data Format​

  1. Select the format in which the Nexset data will be sent to the Precoro API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. Precoro's API accepts data in JSON format for all write operations.

API Endpoint URL​

  1. Enter the URL of the Precoro API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://). For update operations that target a specific record (such as updating a supplier or item), include the record's ID at the end of the URL path.

For example, to update a supplier with ID 123, the URL would be https://api.precoro.com/suppliers/123. To create a new supplier, the URL would be https://api.precoro.com/suppliers.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the X-AUTH-TOKEN or email authentication headers in this field — these are handled automatically by the Precoro credential configured for this destination.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Precoro destination, select the attributes from the Exclude Attributes pulldown menu. This is useful when the Nexset contains fields that are not accepted by the Precoro API and would cause request errors.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Property Inside JSON Object

  1. Enter the name of the JSON property that should contain the batched records in the Property Name field.
  2. If any additional properties should be included in the request, enter the properties in the Other Props field in JSON format.

Code

  1. Enter the code that will be used to create the batched request in the code editor below the Grouping Algorithm field.

Response Webhook​

Optional

Nexla can automatically send the response received from the Precoro API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as the ID of a newly created record or the result of an update operation.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Precoro API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.

  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Precoro API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Precoro API using the current settings.

Save & Activate the Destination​

  • 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 begin sending data to the configured Precoro endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Precoro until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.