Community APIs
The AINative Studio Community APIs provide everything you need to build social, collaborative experiences on top of the AINative platform. These APIs power user relationships, community events, comments, and content discovery across your tenant.
What's included
| API surface | Description |
|---|---|
| Social Graph | Follow/unfollow, friend requests, blocks, ignores, follower lists |
| Community Events | Create, RSVP, browse, and export community events |
| Comments | Thread comments on any content type (videos, articles, tutorials) |
| Search | Unified search across users, posts, groups, and events |
Base URL
All Community API endpoints are served through the Kong gateway:
https://api.ainative.studio
Endpoint prefixes by surface:
| Surface | Path prefix |
|---|---|
| Social Graph | /api/v1/social/ |
| Community Events | /api/v1/community-events/ |
| Comments | /api/v1/community/ |
| Search | /api/v1/community/search/ |
Authentication
All endpoints (except the public comments read endpoint) require a Bearer token:
Authorization: Bearer <your_api_key>
Obtain an API key from the AINative dashboard.
Tenant scoping
All community data is scoped to your tenant. Users must be associated with a tenant or organization — requests from users without a tenant association will return 400 Bad Request.
Pagination
List endpoints use offset/limit pagination. All paginated responses include:
{
"total": 142,
"offset": 0,
"limit": 20,
"has_more": true
}
Common error codes
| Code | Meaning |
|---|---|
400 | Invalid input or missing tenant association |
403 | Authenticated but not authorized (wrong owner, blocked, etc.) |
404 | Resource not found or outside your tenant |
409 | Conflict (duplicate follow, duplicate friend request, etc.) |
Guides
- Social Graph API — build follow graphs and friend networks
- Community Events API — manage event RSVP and discovery
- PAI Palooza Advertising API — run ad campaigns on event pages