Integration with Rahi

(Please note that this integration is still in development and subject to change.)

As a Preferred Distributor Partner, Rahi offers an integration to send asset information such as Model, Manufacturer, Serial Number, Purchase Date, and PO Number directly into Oomnitza when the product is ordered.

This integration is built and hosted by Rahi. For further details please see below. For any questions, or to request an integration, please contact your Rahi representative and ask about the Oomnitza EDI integration.

For more information on Rahi, visit  

Available Information

Rahi's integration with Oomnitza allows for the transmission of the following fields. 

  • serial_number

  • po_number

  • po_number_line

  • rahi_manufacturer

  • model

  • rahi_manu_part_number

  • rahi_warehouse_location

  • purchase_date

  • purchase_currency

  • purchase_price

  • rahi_ship_date

  • rahi_asset_tag

  • ship_to_customer

  • rahi_shipping_date

  • rahi_shipping_carrier

  • rahi_tracking_no

All fields are sent from Rahi to Oomnitza by default and are mapped based on the External ID of the Field in Oomnitza. Any fields sent to Oomnitza without a corresponding external ID will be ignored. Once the Rahi integration is in place, any of the fields listed above can be integrated by creating a new custom field in Oomnitza with an External ID that matches the desired field.


For more information on creating custom fields in Oomnitza, please visit on Customizing Oomnitza.

What Rahi needs from you:

To configure the integration, Rahi requires a few key pieces of information to get it set up.

  1. Oomnitza Endpoint URL (e.g.
  2. Client API token (See Below)

Steps below take place after customers work with Oomnitza to create an environment for that customer/company.

Acquiring a Token: 

In order to generate an API token in Oomnitza, navigate to the Settings page and select “API”.


From the API page, Select “+ Add New” to generate a new API token. You’ll be prompted to enter a name for the token:


Once you’ve done this, you’ll be given the new API token. This will only be displayed once, and cannot be recovered if lost, so make sure to store it somewhere secure:


For external services, we recommend creating a new User that is specific to that service. Once created, you can log in as that user and generate an API token associated with that account. This makes the activity of the API token easier to identify and control, and prevents issue as your team members change.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk