Response Format
Developer guides & examples
- Overview
- Features
- Authentication
-
API EndpointsInspector
- GET SSL Health Inspector
- GET Security Headers Inspector
- GET Email Inspector
- GET User Agent Inspector
- GET IP Geolocation
- GET DNS Lookup
- GET Redirect Tracer
- GET Meta Tag Extractor
- GET Link Checker
- GET Robots.txt Parser
- GET Favicon Fetcher
- GET URL Validator
- GET Email Auth Validator
- POST JWT Decoder
- POST Text Analyzer
- POST Image Metadata Extractor
- GET Website Performance Analyzer
- GET My IP Address
- GET HTTP Status Code Lookup
- GET Cron Expression Parser
- POST JSON Diff / Compare
- POST Regex Tester
- GET CORS Checker
- GET Sitemap Parser
- GET Structured Data Validator
- GET Mixed Content Checker
Converter- POST HTML to PDF Converter
- POST Markdown to HTML
- POST JSON Formatter & Validator
- POST JSON to CSV
- POST Base64 Encode/Decode
- GET Phone Number Formatter
- POST JSON Schema Validator
- POST Hash Generator
- GET Color Converter
- GET Timestamp Converter
- POST URL Encoder/Decoder
- POST CSV to JSON Converter
- POST HTML to Markdown Converter
- POST YAML to JSON Converter
- POST XML to JSON Converter
- POST JSON to XML Converter
- POST Markdown to PDF Converter
- POST JSON to YAML Converter
GeneratorLookup - Response Format
- Code Examples
- OpenAPI Docs
Share Your Feedback
Suggest a micro‑API
Get a free API key and start in minutes.
Free tier is for development & small projects.
API Response Format
All Apixies API endpoints return consistent JSON responses with standard HTTP status codes. This guide explains the response structure, error handling, and status codes you can expect.
All responses share the same envelope:
Success Example
{
"status": "success",
"http_code": 200,
"code": "INSPECT_EMAIL_OK",
"message": "Email inspection successful",
"data": { /* … */ }
}Error Example
{
"status": "error",
"http_code": 422,
"code": "VALIDATION_FAILED",
"message": "Invalid email address",
"errors": { "email": ["The email must be valid."] }
}