Update Site Inspection

Updates the site inspection section of an existing merchant application. Site inspection data captures physical location details — including inventory storage type, zoning classification, square footage, lease or ownership status, and four compliance screening questions — used by underwriters to verify the legitimacy and operational status of the merchant's business location.

Endpoint

POST /api/v1/merchant/siteInspection

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Call this endpoint to correct or update site inspection information after the initial merchant submission. This is commonly needed when a merchant moves to a new location, when the original inspection details were incomplete, or when an underwriter requests clarification on location-specific compliance questions. Accurate site inspection data is required before the application can advance through underwriting.

Request Body

{
  "id": 10482,
  "siteInspection": {
    "inventoryMaintainedType": "OnSite",
    "question1": false,
    "question2": false,
    "question3": false,
    "question4": false,
    "zoning": "Comml",
    "squareFootageType": "From_1001_To_2000",
    "merchant": "Leases",
    "nameAddressLandlord": "Peachtree Properties Inc, 800 Corporate Blvd, Atlanta GA 30303"
  }
}

Response

200 OK

{
  "data": {},
  "status": "OK",
  "error": null,
  "warning": null,
  "validationResults": [],
  "requestId": 47813
}

Error Codes

Common Mistakes

• Setting inventoryMaintainedType to FulfillmentCenter without providing fulfillmentCenterNameAndAddress — underwriters will flag this as incomplete.
• Setting merchant to Leases without providing nameAddressLandlord — this information is required for compliance.
• Answering true to any compliance question without providing the corresponding explanation field — always supply questionNExplanation when questionN is true.
• Using incorrect enum values (e.g., "Commercial" instead of "Comml") returns a 400 validation error.

Related Endpoints

• POST /api/v1/merchant/parameters — Update business and owner information.
• POST /api/v1/merchant/account — Update sales and business profile.
• POST /api/v1/merchant/attachment — Upload site inspection validation documents.

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/merchant/siteInspection \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 10482,
    "siteInspection": {
      "inventoryMaintainedType": "OnSite",
      "question1": false,
      "question2": false,
      "question3": false,
      "question4": false,
      "zoning": "Comml",
      "squareFootageType": "From_1001_To_2000",
      "merchant": "Leases",
      "nameAddressLandlord": "Peachtree Properties Inc, 800 Corporate Blvd, Atlanta GA 30303"
    }
  }'