Build with 150+ REST API Endpoints
REST APIs Reference Guide for Developers
Use PixLab REST APIs for image processing, DOCSCAN ID scanning, document conversion, background removal, media analysis, and vision workflows. This guide covers access, authentication, response codes, and where to find each endpoint.
Used by developers and businesses building production media and document workflows
The PixLab REST API Reference Guide is the main entry point for developers integrating media processing, document intelligence, ID scanning, and vision workflows into web apps, mobile products, and internal tooling. It covers the request model, authentication, response handling, and the main directories you need to start shipping against the API with less guesswork.
For hands-on implementation, start with the API Portal or follow the REST API Tutorial. For product-specific workflows, refer to the ID Scan & Extract API, the Vision Platform, and the PDF Generation APIs. The API Endpoints Directory covers Media Analysis, Content Moderation, Image Processing, Document Conversion, Face Recognition, and many other specialized API endpoints →
- Features of the PixLab REST APIs
- API Access URL
- Authentication & API Keys
- Response Status Codes
- API Endpoints Categories →
- API Endpoints Reference Guide →
- Your First API Call →
- Explore Further
Features of the PixLab REST APIs
The PixLab REST API is built on HTTP/TLS and standard RESTful principles ↗. It is designed to stay predictable across image, media, document, and ID workflows. Key characteristics include:
-
Simple HTTP request patterns for parameters, authentication, and output handling.
-
Standard HTTP response codes with clear failure handling and easier debugging.
-
Language-agnostic integration with
JSONresponses and optionalBLOBoutput for media endpoints. -
More than 150 API endpoints spanning media, vision, document, identity, and creative workflows.
-
Specialized products including the ID Scan & Extract API, the Vision Platform, and the Rich-PDF Generation APIs.
-
Organized endpoint categories for Media Analysis, Content Moderation, Background Removal, and more.
-
IPv4 and IPv6 support across modern network environments.
-
Browser tools built on the API include APP UX Mobile Code Generator, Convert Box, AI Photo Editor, Bulk Image Background Removal, and more.
-
Reference documentation, tutorials, code samples, and supporting open-source resources.
API Access URL
-
The main PixLab API base URL is
https://api.pixlab.io/. For Vision Language Model endpoints exposed through the Vision Platform with an OpenAI-compatible interface, usehttps://llm.pixlab.io/. -
API requests follow the structure
https://api.pixlab.io/endpoint?param=val¶m2=val2, whereendpointis the API endpoint you want to call. Query parameters vary by endpoint. Common examples include:- DOCSCAN: ID Cards & Passport scanning.
- QUERY: Receive natural language responses to image-related queries.
- BGREMOVE: Bulk image background removal.
- PDFTOIMG: Convert PDF to images.
- DESCRIBE: Generate natural language descriptions of image or video frame contents.
- CHAT: OpenAI-compatible LLM interaction API endpoint.
- MOGRIFY: Partial blurring, such as of faces.
- NSFW: Nudity and Adult content detection.
- SCREENCAPTURE: Website Screenshots extraction.
- Plus hundreds more API Endpoints →
-
Most endpoints support both
GETandPOST, which keeps integration flexible across web apps, mobile clients, and backend services. Request style stays consistent across the wider endpoint set. -
A dedicated Health & Status Dashboard ↗ offers real-time monitoring to ensure reliable service.
Summary
| Access Point URL | api.pixlab.ioOR llm.pixlab.io |
| API Health Monitoring Endpoint | api.pixlab.io/status OR status.pixlab.io |
| Architecture | RESTful |
| HTTP & TLS Protocols Version | 1.3 |
| Authentication | Key-Based |
| Network | Cloudflare, AWS, & OVH |
| HTTP Response MIME Type | application/json or BLOBs |
| HTTP Status & Error Codes | Listed Below ↓ |
| API Endpoints | Documented here → |
Authentication
When you sign up ↗ for a PixLab account, you receive a unique API key. This key is required for authenticating requests to the PixLab API. You can create and manage keys from the API Keys section of the PixLab Console ↗.
Authentication Methods
Authenticate to the PixLab API either with an HTTP header or by passing the API key as a query parameter. Choose the approach that fits your stack and deployment model.
| HTTP Header |
Send your API key in the WWW-Authenticate HTTP header. Example: |
| Query Parameter |
You can also include the API key directly in a |
Responses, Status & Errors Codes
PixLab API endpoints return consistent HTTP status codes with all responses formatted as application/json, regardless of success or failure. For endpoints returning binary content (e.g., image BLOBs), set blob=true to receive binary output on success.
200 |
Success - API Call (e.g., DOCSCAN, BGREMOVE etc.) successfully completed. |
400 |
Bad Request - Missing or invalid parameters. |
401 |
Unauthorized - Invalid or missing API Key ↗. |
404 |
No Such Endpoint - Resource does not exist. |
405 |
Method Not Allowed - HTTP method not supported by the target API Endpoint. |
415 |
Unsupported Media Type - File format not supported. |
429 |
Too Many Requests - Rate limit exceeded. |
500 |
Internal Server Error - Temporary server-side issue. |
Explore Further
Once you understand the request model, authentication flow, and response patterns, the next step is the endpoint catalog. Use the links below to move into the full PixLab API endpoint directory, practical code samples, the ID Scan & Extract API, and the Vision Platform.