API Reference
Complete API documentation for the Pixelated Empathy platform
API Reference
The Pixelated Empathy API provides a comprehensive set of endpoints for integrating with our platform. This documentation will help you understand how to authenticate, make requests, and work with responses from our API.
Authentication
All API requests must be authenticated. You can authenticate using either:
- Platform API keys obtained from the developer dashboard
- OAuth tokens from your Pixelated Empathy application
API keys should be included in the Authorization header:
Authorization: Bearer YOUR_PLATFORM_API_KEYFor application-based authentication, use OAuth 2.0 flows as documented in the authentication guides.
Never share your API keys publicly or commit them to version control. Use environment variables or a secure key management system to store your API keys.
Base URL
All API requests should be made to the following public gateway URL:
https://api.pixelated.dev/api/v1This gateway provides access to all Pixelated Empathy services through a unified interface. Only the public gateway is accessible for security and compliance.
For example, to access the search endpoint, your full URL would be:https://api.pixelated.dev/api/v1/search
Request Format
The API accepts requests with Content-Type: application/json for POST, PUT, and PATCH requests. GET requests should include query parameters in the URL.
Response Format
All responses are returned as JSON. Successful responses include a data field containing the requested information. Error responses include an error field with details about the error.
Successful Response Example
{
"data": {
"id": "mem_123",
"content": "User reported feeling anxious about work presentation",
"metadata": {
"category": "therapeutic_insight",
"timestamp": "2023-01-01T10:30:00Z"
}
}
}Error Response Example
{
"error": {
"code": "invalid_request",
"message": "Invalid user ID provided",
"status": 400
}
}Rate Limiting
API requests are subject to rate limiting to ensure fair usage. The current rate limits are:
- 100 requests per minute per API key
- 5,000 requests per day per API key
Rate limit information is included in the response headers:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1620000000Available Endpoints
User management endpoints
Session management endpoints
Analytics and reporting endpoints
Webhook configuration and events
SDKs and Libraries
We provide official SDKs for several programming languages to make integrating with our API easier:
Versioning
The API uses semantic versioning and is versioned through the URL path (e.g., /api/v1/users). We maintain backward compatibility within the same major version and will notify you of any breaking changes before they occur.
Version History
| Version | Status | Released | Sunset Date |
|---|---|---|---|
| v1 | Current | April 2025 | No planned sunset |
| Legacy (no version) | Deprecated | January 2025 | October 2025 |
API Versioning Guidelines
- Always include the version in your API requests to ensure stability
- Non-versioned endpoints automatically redirect to the current version but will be deprecated in the future
- We will maintain API compatibility within the same major version
- Minor version updates (e.g., new features) will be added in a backward-compatible manner
- Major version updates may contain breaking changes
Legacy unversioned endpoints (e.g., /api/search) are currently redirected to their v1 counterparts but will be removed in October 2025. Please update your integration to use the versioned endpoints.
Support
If you encounter any issues or have questions about our API, please contact our support team: