Insta Check & Micro-Checks API

SignalX Insta Check and Micro-Checks APIs let you authenticate, upload files for microchecks, create and track orders, and fetch MSME and GST information in a structured way.

---

1. Authentication (RiskMaster login)

Authenticate the user and obtain a sessionID that will be used as a token for downstream APIs.

Endpoint

POST https://api.riskmaster.signalx.ai/query
Content-Type: application/json

GraphQL mutation

mutation Login($username: String!, $password: String!, $appId: Int) {
  login(username: $username, password: $password, appId: $appId) {
    message
    code
    sessionID
    __typename
  }
}

Variables

Variable	Type	Required	Description
username	String	Yes	Registered username (typically an email address).
password	String	Yes	Account password.
appId	Int	No	Application identifier, defaults to 10 for standard app.

Response fields

Field	Type	Description
message	String	Human‑readable message describing the result.
code	String	Status or error code for the outcome of authentication.
sessionID	String	Session token; use as auth_token cookie or Bearer token for other APIs.

Notes

• Do not hardcode credentials.
• Store sessionID securely; each token is typically valid for 24 hours.

---

2. Microchecks & Orders

2.1 Analyze microchecks

Submit an Excel file for microcheck analysis (for example, MSME checks).

Endpoint

POST https://micro.signalx.ai/micro-check-api/microchecks/analyze
Content-Type: multipart/form-data

Headers

Header	Value	Description
token	<jwt_token>	Required. Authentication token (JWT).
accept	application/json, text/plain, */*	Accepted response formats.

Form-data body

Field	Example	Required	Description
file	new.xlsx	Yes	Excel file to be analyzed.
type	MSME	Yes	Type of check (e.g. MSME).
sub_type	NORMAL_CHECKS	Yes	Sub-type of check (e.g. NORMAL_CHECKS).

---

2.2 Create order (Micro-Checks v2)

Create a new micro-check order for vendor verification.

Endpoint

POST https://micro.signalx.ai/micro-check-api/microchecks/v2/create_order
Content-Type: multipart/form-data
Authorization: Bearer <your_jwt_token>

Form-data body

Field	Type	Required	Description
order_name	String	Yes	Human‑readable name for the order.
type	String	Yes	Category, e.g. MSME.
sub_type	String	Yes	Sub-category, e.g. NORMAL_CHECKS.
duplicate_vendors	Integer	Yes	Count of duplicates (use 0 if none).
invalid_vendors	Integer	Yes	Count of invalid vendors (use 0 if none).
file	File	Yes	Vendor data upload (.csv / .xlsx).

---

2.3 User list orders (order status)

Retrieve order status for a specific order.

Endpoint

GET https://micro.signalx.ai/micro-check-api/microchecks/v2/dashboard/user_list_orders
Authorization: Bearer <your_jwt_token>

Query parameters

Parameter	Type	Required	Description
order_id	String	Yes	Unique identifier of the order

Example response

{
  "status_code": 200,
  "data": {
    "status": "PENDING",
    "sub_type": "NORMAL_CHECKS"
  },
  "message": "Success",
  "total_count": null,
  "completed": null,
  "pending": null
}

---

3. MSME verification APIs

3.1 Get MSME verification data

Retrieve paginated MSME verification data indicating whether entities are registered under Udyam/Udyog or not registered.

Endpoint

GET https://micro.signalx.ai/micro-check-api/msme/v2/get_msme_verification_data
Authorization: Bearer <your_jwt_token>

Query parameters

Parameter	Type	Required	Description
order_id	String	Yes	Unique identifier of order.
page	Integer	Yes	Page number (1‑indexed).
page_size	Integer	Yes	Records per page.

Example item

{
  "Pan": "AAAAC0268P",
  "Status": "Not Registered"
}

Possible Status values: Not Registered, Udyog Registered, Udyam Registered.

---

3.2 Get MSME detailed data

Retrieve enriched MSME registration data including PAN, GSTIN, legal/trade names, and registration attributes.

Endpoint

GET https://micro.signalx.ai/micro-check-api/msme/v2/get_msme_data
Authorization: Bearer <your_jwt_token>

Query parameters

Parameter	Type	Required	Description
order_id	String	Yes	Unique identifier of the order.
page	Integer	Yes	Page number (1‑indexed).
page_size	Integer	Yes	Number of records per page.

Example fields per item

• pan
• gstin
• legal_name
• trade_name
• udyam_number
• uan_number
• enterprise_type
• major_activity
• social_category
• state
• date_of_commencement
• date_of_classification
• classification_year

---

4. GST overview & detailed APIs

4.1 Get GST overview data

Retrieve paginated GST registration info for each GSTIN associated with an order.

Endpoint

GET https://micro.signalx.ai/micro-check-api/gst/v2/get_gst_overview_data
Authorization: Bearer <your_jwt_token>

Query parameters

Parameter	Type	Required	Description	Example
order_id	String	Yes	Unique identifier of the order	3d73bea2-ec1c...
page	Integer	Yes	Page number	1
page_size	Integer	Yes	Records per page	5

Key response fields (per item)

Field	Type	Description
gstin	String	GST Identification Number
legal_name_of_business	String	Legal name of the registered business
trade_name	String	Trade name of the business
effective_date_of_registration	String	Date when GST registration became effective
constitution_of_business	String	Entity type (e.g. Proprietorship)
gstin_uin_status	String	Status (e.g. Active, Cancelled)
whether_aadhaar_authenticated	Boolean	Aadhaar authentication completion status
whether_e_kyc_verified	Boolean	e‑KYC verification completion status
goods / services	Array	List of HSN codes and descriptions

---

4.2 Get GST detailed data

Fetch comprehensive Goods and Services Tax information, including filings and filing frequency history.

Endpoint

GET https://micro.signalx.ai/micro-check-api/gst/v2/get_gst_detailed_data
Authorization: Bearer <JWT_TOKEN>

Query parameters

Parameter	Type	Required	Description
order_id	String	Yes	Unique UUID of the order.
page	Integer	Yes	Page number (starting at 1).
page_size	Integer	Yes	Number of records per page.

Top-level metadata

• status_code – e.g. 200 for success
• total – total records available
• total_pages – total pages based on page_size
• data[] – array of detailed GSTIN objects

A. Overview object (per GSTIN)

Field	Description
legal_name_of_business	Official registered legal name.
constitution_of_business	Entity type (e.g. Private Limited, Proprietor).
gstin_uin_status	Current status (Active, Cancelled, etc.).
nature_of_core_business_activity	Primary role (e.g. Manufacturer).
principal_place_of_business	Primary address.
whether_aadhaar_authenticated	true / false.
goods	Array with hsn and description entries.

B. Filings array

Each filing object typically includes:

• filing_type – e.g. GSTR1, GSTR3B
• tax_period – month of the return (e.g. January)
• date_of_filing – timestamp when the return was submitted
• status – typically Filed or Not Filed

C. Filing frequency history

• financial_year – e.g. 2026
• preference – MONTHLY or QUARTERLY
• tax_period_start / tax_period_end – date range for the preference

Example snippet

{
  "gstin": "27AAOCP1545L1ZY",
  "overview": {
    "legal_name_of_business": "PARMAR TECHNOFORGE PRIVATE LIMITED",
    "nature_of_core_business_activity": "Manufacturer",
    "gstin_uin_status": "Active",
    "goods": [
      { "hsn": 73072100, "description": "FLANGES" }
    ]
  },
  "filings": [
    {
      "filing_type": "GSTR1",
      "tax_period": "January",
      "date_of_filing": "2026-02-06T00:00:00",
      "status": "Filed"
    }
  ],
  "filing_frequency_history": [
    {
      "financial_year": 2026,
      "preference": "MONTHLY"
    }
  ]
}

---

Tech team notes

• Pagination: Always honor total_pages and related metadata to avoid loading thousands of records at once.
• Token expiry: APIs use the sessionID from the RiskMaster login as a JWT; refresh or re‑login if a 401 Unauthorized is returned.