This information is aimed to developers only. If you're not a developer, you probably don't need to know about all this.

To get an API key, you should have access to a Megaventory account. If you don't have a Megaventory account, you can sign-up for free at:

Once you sign-in to your Megaventory account, you may click the Profile Icon to access your profile information:


click the key icon to generate an API key and hit Update at the bottom:

Then, head over to

Example: getting all products

If you click on Product / ProductGet function, you'll see that you need to do a POST request to: with the payload (example):


to retrieve all your products.

You can also do a GET request for the same at the following URL:

Example: inserting a client

A POST request to with the following payload (example):

"mvSupplierClient": {
"SupplierClientID": 0,
"SupplierClientType": "Client",
"SupplierClientName": "My dummy client"
"mvRecordAction": "Insert"

will insert a new client with name "My dummy client"

Example: getting products with available quantity

To get the products with available quantity you can do a GET request at:

or a POST request at: with the appropriate body payload.

By doing so, you will get a response with all available products. Also, if you notice, there is a "query" parameter. This simulates more or less the behavior of an SQL query. For example (GET): like '%000%'

will fetch products with positive quantity that include the '000' anywhere in the ProductSKU field. The thing to note is the mv. prefix that needs to be added before the usual fields that you'll find in the syntax of each API call.

Example: get suppliers or clients

For the SupplierClientGet: like '%mag%'

will bring all suppliers/clients that include 'mag' in their name. You can also use an AND/OR: like '%mag%' AND mv.SupplierClientType = 2

(mv.SupplierClientType = 2 is for strictly clients, mv.SupplierClientType = 1 is for strictly suppliers, mv.SupplierClientType = 0 is for entities that are both suppliers and clients).

A general note

Most API functions have an Update call (such as SupplierClientUpdate) with an mvRecordAction parameter. This can either be mvRecordAction=insert (create/insert) or mvRecordAction=update.

The metadata definition (JSON) of the SalesOrderGet/SalesOrderUpdate is here:

To get the SalesOrderClientID one should first call the SupplierClientGet (with the name of the supplier/Client) and extract the id. Same with the SalesOrderInventoryLocationID. Alternatively, one can store ids locally upon an initial sync.

Did this answer your question?