RestAPI instructions for importing documents into Microix

Creation date: 10/9/2025 1:36 PM    Updated: 10/9/2025 1:57 PM   import restapi

Overview

This article provides detailed instructions for securely integrating with the Microix Workflow Modules Modern System via our REST API.
Use this guide to properly authenticate, structure requests, and understand response behaviors when submitting transaction data.


📡 API Endpoint

Method:POST
URL: (use Workflow Modules Modern to generate the URL for the endpoint)

This endpoint allows you to submit one or more transaction records for import into the Microix system.


🔐 Authentication

To ensure security, each request must include a valid TokenID in the JSON body.

Token Requirements

  • The TokenID must be registered in advance with Microix.

  • Tokens are validated against our system before processing any data.

Example JSON Field

"TokenID":"Token is issued within the Workflow Modules Application"

📤 Request Format

Header:

Content-Type: application/json

Sample JSON Payload:


{
  "TokenID": "t+C+eNfq5ztOGq+....",
  "Items": [
    {
      "sDocType": "INV",
      "sVendID": "VEND001",
      "sDescription": "Office Supplies",
      "sUser_ID": "jdoe",
      "sDept_ID": "DEPT01",
      "Status": "Pending",
      "sItemID": "ITEM001",
      "sItem_UnitDesc": "Box of Pens",
      "sItem_UnitType": "Each",
      "sItem_NumUnits": 5,
      "sItem_UnitCost": 12.50,
      "dtmPostTo": "2025-06-11",
      "sVendorItemID": "VPEN001",
      "GLAcct": "4000-Office"
    }
  ]

}

✅ Response Codes

CodeMeaning
200✅ Success – Data inserted successfully
401❌ Unauthorized – Invalid token
400⚠️ Bad Request – Malformed payload
500🧯 Server Error – Internal processing issue

📋 Field Reference

Field

Required

Type

Notes

TokenID

string

Must match a registered token

sDocType

string

Document type (ENC - Purchase Order, API - Invoice>

sVendID

string

Vendor ID (Should match with MIP's Vendor ID

sDescription

string

Line description

sUser_ID

string

Requestor (Must match a valid Microix User Account

sDept_ID

string

Microix Workflow ID

Status

string

Document Workflow Status (e.g., value between 0 and 10)

sItemID

string

Product/Item Number (User N/A if not available)

sItem_UnitDesc

string

Line Item Description

sItem_UnitType

string

Unit of Measure (e.g., "Box", "Each")

sItem_NumUnits

decimal

Quantity

sItem_UnitCost

decimal

Unit Cost

dtmPostTo

datetime

Transaction date

GLAcct

string

GL account should match MIP's Account


🛠 Example Use Case

If your third-party system exports purchase orders, invoices, or other transactional data that needs to be processed in Microix and MIP, you can automate the submission process by:

  1. Generating a valid token from the Workflow Modules app.

  2. Formatting the invoice data as per the sample JSON.

  3. Sending the payload to the /transactions/import endpoint.

  4. Handling the response for confirmation or error logging.