Partner v4 request behavior
Authentication, errors and report traversal for account administration.
Authenticate JSON requests
Create a partner Security Key with v4 API permissions. Send it in Authorization and use Content-Type: application/json. These account-administration credentials differ from Sign-Up OAuth.
Interpret responses
A 200 includes a result; a 204 succeeds without a response body. Errors include type and message; inspect them even for HTTP 500. Status Meaning 400 Malformed request 401 Missing or invalid key 404 Unknown resource 405 Method unsupported 406 Not acceptable 415 Invalid content type or JSON 500 Server error; may include invalid_field details 503 Service unavailable
Traverse reports and searches
Use the returned links for paging, retaining Authorization on every request. maxResults controls supported page sizes; hasMore becomes false at completion. This report-link pattern differs from REST customer cursors and Sign-Up page numbers. GET /api/v4/merchants/reports/123?offset=50&maxResults=50 HTTP/1.1 Host: sandbox.nmi.com Authorization: <YOUR_V4_API_KEY> Content-Type: application/json