← Back to EcomCentral
NETO / MAROPOST COMMERCE CLOUD API

Neto / Maropost Commerce Cloud Setup Guide

Connect your Neto or Maropost Commerce Cloud store to EcomCentral using API key authentication.

About Neto / Maropost Commerce Cloud

Neto (now rebranded as Maropost Commerce Cloud) is an Australian e-commerce platform designed for retail, wholesale, and multi-channel selling. It is widely used by mid-market merchants across Australia and New Zealand and provides robust inventory, order, and fulfilment management capabilities.

ℹ️ EcomCentral connects to the Neto API — a single-endpoint, action-header-based REST API where all operations POST to /do/WS/NetoAPI with the operation name in the NETOAPI_ACTION request header (e.g. GetOrder, GetItem, UpdateOrder). JSON responses are returned when the Accept: application/json header is sent; otherwise the API replies in XML.

Prerequisites

Getting Your API Credentials

  1. Log in to your Neto / Maropost Commerce Cloud control panel
  2. Navigate to Settings → API
  3. Click Add API User (or select an existing API user)
  4. Note the NETOAPI_KEY — this is your api_key
  5. Note the username of the API user account — this is your username
  6. Note your store domain, e.g. mystore.neto.com.au — this is your domain
  7. In EcomCentral, add a new Neto connection and fill in all three fields
  8. Click ⚡ Test to verify the connection

Credentials Reference

KeyRequiredDescriptionExample
domain Required Your store domain without https://. EcomCentral auto-builds the /do/WS/NetoAPI endpoint. A full URL is also accepted. mystore.neto.com.au
api_key Required The NETOAPI_KEY value shown on the API user's settings page abc123xyz789…
username Required The NETOAPI_USERNAME — the login name of the API user account, not an email address api_user
✅ Alternative key names accepted: base_url or url for the domain; apiKey or key for the API key; user for the username. The domain field accepts a bare domain like mystore.neto.com.au or a full URL — EcomCentral detects and builds the correct /do/WS/NetoAPI endpoint automatically.

API Actions Used

All requests POST to https://{domain}/do/WS/NetoAPI with the action name in the NETOAPI_ACTION header. The JSON body is keyed on Filter for reads or the resource name (Order, Item) for writes.

ActionDirectionEcomCentral Operation
GetOrderReadList orders (paginated), test connection, single order detail
GetItemReadList products (paginated), single product detail by SKU
UpdateOrderWriteAttach tracking number and set order status to Dispatched
UpdateItemWriteSet warehouse stock quantity for a SKU
ℹ️ The Neto API requires an explicit OutputSelector list for each request — only fields listed in OutputSelector are returned in the response. EcomCentral requests all fields needed for display automatically.

Order Statuses

Neto uses named string statuses. EcomCentral displays them with colour-coded badges.

StatusBadge colourNotes
Dispatched GreenOrder shipped; tracking attached
Delivered GreenConfirmed delivery
Complete / Closed GreenFulfilled and closed
New BlueJust placed
Pick / Pack BlueWarehouse fulfilment stages
Pending / Processing / PartShip BlueIn progress; partial shipment
On Hold AmberAwaiting action
Backordered AmberStock unavailable
Cancelled RedOrder cancelled
Returned / Refunded RedPost-fulfilment reversal

Supported Features

FeatureSupportedNotes
View orders (paginated)✅Order ID, date, status, total + currency
View order detail✅Billing address, shipping address, line items (SKU / qty / price), tracking
Add tracking number✅Attaches tracking via UpdateOrder and sets status to Dispatched
View products (paginated)✅SKU, name, price, available stock quantity
View product detail✅Full product via GetItem by SKU — name, brand, price, RRP, barcodes, image, category, description
Update stock quantity✅Sets warehouse quantity via UpdateItem with Action: set
Test connection✅GetOrder with Limit=1 — a valid Ack: Success confirms credentials work

Troubleshooting

Ack: Error on all requests

The api_key or username is incorrect, or the API user does not have sufficient permissions. Verify both values in Settings → API and ensure the API user has read and write access to orders and products.

Domain not found / connection error

Enter the store domain without the https:// prefix — for example mystore.neto.com.au, not https://mystore.neto.com.au. EcomCentral adds the scheme and endpoint path automatically. A trailing slash is harmless and will be stripped.

Empty Order or Item array in response

The Neto API returns an empty array (not an error) when no records match the filter. For order detail, verify that the OrderID exists in the store. For product detail, verify the SKU matches exactly — Neto SKUs are case-sensitive.

Messages.Error in the response body

Even when Ack is Success, the API may include action-level error messages in Messages.Error. EcomCentral surfaces the first error message directly. Common causes: invalid OutputSelector field names, unknown OrderID or SKU, insufficient API user permissions for the requested action.

Tracking added but order not marked Dispatched

EcomCentral sets OrderStatus: Dispatched when submitting tracking via UpdateOrder. If the store has a workflow lock preventing status transitions, the API may return an error. Check the Messages.Error field in the response and review the order's current status in the control panel.

🔧 Quick sanity check — use a tool such as Postman or curl to POST to https://{domain}/do/WS/NetoAPI with headers NETOAPI_ACTION: GetOrder, NETOAPI_KEY: {your_key}, NETOAPI_USERNAME: {your_username}, and Accept: application/json, with body {"Filter":{"Limit":1,"OutputSelector":["OrderID"]}}. An Ack: Success response confirms credentials are correct.