API Error Codes

6 min

Who is this for: Developers troubleshooting failed MomentScience API requests who need to identify error causes and take corrective action.

Outcome: Identify HTTP status codes and error response formats returned by MomentScience APIs and implement appropriate error handling in their integration.

Overview

This document lists the HTTP status codes and error responses returned by the MomentScience Native Ads API. Use this reference to troubleshoot failed requests and understand how to handle different error scenarios.

HTTP Status Codes

The API uses standard HTTP status codes to indicate the result of a request:

Code	Meaning	Description
200 OK	Success	The request was successful and the response body contains the result.
400 Bad Request	Invalid input	The request was malformed or contains invalid parameters.
401 Unauthorized	Authentication required	Your API key is missing or invalid.
403 Forbidden	Access denied	Your API key does not have permission to access the resource.
404 Not Found	Resource not found	The requested endpoint or resource does not exist.
422 Unprocessable Entity	Validation failed	The request was well-formed but contained invalid data.

Error Response Format

When a request fails, the API usually returns a JSON response with information about the error. Some errors return only a status code: an invalid API key returns 401 with an empty body, and a request with no API key returns 401 with {"message": "No Publisher ID, SDK ID, or API Key found in request"}. Check the HTTP status code before parsing the response body.

Example 1: Invalid request parameters

{
  "statusCode": 400,
  "message": "Invalid request parameters"
}

Example 2: No results found

{
  "data": {},
  "status": "fail",
  "message": "No results found"
}

If you're encountering persistent issues or errors not listed above, contact the MomentScience support team at [email protected].