ConnectHub API Overview
The ConnectHub REST API enables you to programmatically access data, manage users, post content, and integrate our social features directly into your applications.
api.connecthub.com. The legacy endpoints are deprecated as of March 2025.
Base URL
https://api.connecthub.com/v2
Authentication
ConnectHub uses OAuth 2.0 and API Keys for authentication. All requests must include an Authorization header. For most use cases, we recommend using Bearer tokens.
curl -X GET https://api.connecthub.com/v2/users/me \ -H "Authorization: Bearer $CONNECTHUB_ACCESS_TOKEN" \ -H "Content-Type: application/json"
Endpoints
The API is organized around REST principles. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
| Method | Endpoint | Description |
|---|---|---|
| GET | /v2/users |
List all users based on filters. |
| POST | /v2/posts |
Create a new post with media and metadata. |
| PATCH | /v2/posts/{id} |
Update an existing post. |
| DELETE | /v2/posts/{id} |
Soft delete a post. |
Response Format
All successful responses return JSON with a standard envelope structure containing status, data, and optionally pagination.
{
"status": "success",
"data": {
"id": "usr_8392a1",
"username": "sarah_designs",
"followers_count": 12450,
"is_verified": true,
"created_at": "2024-01-15T08:30:00Z"
},
"meta": {
"request_id": "req_9928310",
"timestamp": "2025-03-12T14:20:11Z"
}
}
Common Errors
429 Too Many Requests status.
| Code | Message | Description |
|---|---|---|
400 |
Bad Request | The request body is malformed or missing required fields. |
401 |
Unauthorized | Invalid or missing authentication token. |
403 |
Forbidden | You do not have permission to access this resource. |
429 |
Too Many Requests | You have exceeded the rate limit. |