Introduction
Welcome to the ParseForge API documentation. Our API provides a simple and powerful way to integrate advanced functionality into your applications.
https://api.parseforge.dev/v1
Key Features
- RESTful API design
- JSON request and response format
- HTTP status codes for error handling
- Rate limiting: 1000 requests per hour
- HTTPS encryption for all endpoints
Authentication
All API requests require authentication using an API key. Include your API key in the request header:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Getting Your API Key
- Create an account at ParseForge Dashboard
- Navigate to the API Keys section
- Click "Generate New Key"
- Copy and securely store your key
Quick Start
Make your first API call in just a few minutes:
Example Request
curl -X GET https://api.parseforge.dev/v1/users/123 \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json"
Response
{
"id": "123",
"name": "Sample User",
"email": "user@example.com",
"created": "2026-02-28T10:00:00Z"
}
Users API
Manage user data with our Users API endpoints.
/users/:id
Retrieve a specific user by ID.
Parameters
| Parameter | Type | Description |
|---|---|---|
id |
string | The unique identifier of the user |
/users
Create a new user account.
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
email |
string | Yes | User's email address |
name |
string | Yes | User's full name |
role |
string | No | User role (admin, user, guest) |
Example Request
{
"email": "john@example.com",
"name": "John Doe",
"role": "user"
}
Response (201 Created)
{
"id": "usr_abc123",
"email": "john@example.com",
"name": "John Doe",
"role": "user",
"created_at": "2026-03-02T10:30:00Z"
}
/users/:id
Update an existing user.
URL Parameters
| Parameter | Description |
|---|---|
id |
The user ID |
Request Body (partial)
{
"name": "John Smith",
"role": "admin"
}
/users/:id
Delete a user account.
Response (204 No Content)
Returns an empty response with status code 204.
Webhooks
Receive real-time notifications when events occur in your account.
Setting Up Webhooks
- Go to your Dashboard
- Navigate to Settings → Webhooks
- Add a webhook endpoint URL
- Select the events you want to receive
Webhook Payload
{
"event": "user.created",
"data": {
"id": "usr_abc123",
"email": "john@example.com",
"name": "John Doe"
},
"timestamp": "2026-03-02T10:30:00Z"
}
Event Types
| Event | Description |
|---|---|
user.created |
A new user was created |
user.updated |
A user was updated |
user.deleted |
A user was deleted |
data.created |
New data was submitted |
Verifying Webhook Signatures
Each webhook request includes a signature in the X-Webhook-Signature header. Verify this signature to ensure the request came from ParseForge:
const crypto = require('crypto');
const signature = request.headers['x-webhook-signature'];
const payload = JSON.stringify(request.body);
const secret = 'your_webhook_secret';
const expectedSignature = crypto
.createHmac('sha256', secret)
.update(payload)
.digest('hex');
if (signature === expectedSignature) {
// Valid webhook
}
Error Handling
The API uses standard HTTP response codes to indicate success or failure.
HTTP Status Codes
| Code | Status | Description |
|---|---|---|
200 |
OK | Request succeeded |
201 |
Created | Resource successfully created |
204 |
No Content | Request succeeded, no content returned |
400 |
Bad Request | Invalid request parameters |
401 |
Unauthorized | Invalid or missing API key |
403 |
Forbidden | Not permitted to access resource |
404 |
Not Found | Resource not found |
429 |
Too Many Requests | Rate limit exceeded |
500 |
Internal Server Error | Something went wrong on our end |
Error Response Format
{
"error": {
"code": "invalid_parameter",
"message": "The 'email' parameter is required",
"param": "email",
"type": "validation_error"
}
}
Rate Limiting
API requests are subject to rate limits based on your plan:
| Plan | Rate Limit |
|---|---|
| Starter | 100 requests/minute |
| Professional | 1,000 requests/minute |
| Enterprise | Custom limits |
Rate Limit Headers
Each API response includes rate limit information in the headers:
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 987
X-RateLimit-Reset: 1709380800
X-RateLimit-Remaining header to avoid hitting rate limits.
Pagination
List endpoints return paginated results. Use query parameters to control pagination:
| Parameter | Default | Description |
|---|---|---|
limit |
10 | Number of items per page (max: 100) |
offset |
0 | Number of items to skip |
cursor |
- | Cursor for cursor-based pagination |
Example Request
GET /api/users?limit=20&offset=40
Paginated Response
{
"data": [...],
"pagination": {
"total": 150,
"limit": 20,
"offset": 40,
"has_more": true
}
}
API Reference
Detailed documentation for all API endpoints.
/users
List all users with pagination support.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
limit |
integer | No | Number of results (default: 10) |
offset |
integer | No | Skip records (default: 0) |
role |
string | No | Filter by role |
/users/:id
Get a specific user by ID.
Response (200 OK)
{
"id": "usr_abc123",
"email": "john@example.com",
"name": "John Doe",
"role": "user",
"created_at": "2026-03-01T10:30:00Z",
"updated_at": "2026-03-02T14:20:00Z"
}
/data
Submit data to the API.
Request Body
{
"name": "Example",
"value": "Sample data"
}
Client Libraries
Official SDKs to integrate ParseForge into your applications:
📦 Node.js
npm install parseforge-sdk
🐍 Python
pip install parseforge
💎 Ruby
gem install parseforge
☕ Java
implementation 'com.parseforge:sdk:1.0'