Admin API

​

About the Admin API

​

Base URL

https://api.mn.co/admin

​

Authentication

​

Getting Started

​

Core Resources

​

Networks

​

Members

• List and search members
• View member profiles and activity
• Update member information
• Manage member permissions and roles

​

Content & Posts

• Create, read, update, and delete posts
• Manage comments and reactions
• Moderate content
• Work with rich media attachments

​

Events

• Create and manage events
• Track RSVPs and attendance
• Update event details

​

Spaces

• Manage network spaces
• Configure space settings
• Control space membership

​

Webhooks

​

How It Works

1. You configure a webhook endpoint URL in your network settings
2. You select which events you want to receive
3. When an event occurs, Mighty Networks sends an HTTP POST request to your URL
4. Your server processes the webhook and responds with any 2xx status code (200, 201, 202, 204, etc.)

​

Webhook Delivery Format

POST /your-webhook-endpoint
Host: your-domain.com
Content-Type: application/json
Accept: application/json
Authorization: Bearer YOUR_CONFIGURED_API_KEY

{
  "event_id": "abc123-uuid",
  "event_timestamp": "2024-01-15T10:30:00Z",
  "event_type": "PostCreated",
  "payload": {
    "id": 12345,
    "title": "Example post title",
    "author": {
      "id": 67890,
      "email": "user@example.com",
      "first_name": "John"
    },
    "space_id": 111,
    "created_at": "2024-01-15T10:30:00Z"
  }
}

​

Available Events

​

Security

• HTTPS Required: Webhook endpoints must use HTTPS in production
• Authentication: Configure an API key that will be included as a Bearer token in the Authorization header
• Verify the source: Always validate the Authorization header matches your configured key

​

Best Practices

​

Expected Responses

​

Circuit breaker

• Trips on repeated failures: When deliveries to your endpoint fail multiple consecutive times (any non-2xx response, a timeout, or a connection error), the circuit breaker opens and delivery is paused.
• Delivery is paused temporarily: While the circuit is open, new webhooks for that endpoint are not delivered. This protects both your service and ours from wasted retries against a failing endpoint.
• Automatic recovery: After a cooldown period, we probe your endpoint again. Once it responds successfully, the circuit closes and normal delivery resumes automatically—no manual intervention required.

​

Rate Limit and Quota

​

Error Handling

{
  "error": "unauthorized",
  "message": "Invalid API token",
  "status": 401
}

​

Pagination

• page: Page number (default: 1)
• per_page: Items per page (default: 25, max: 100)

{
  "data": [...],
  "meta": {
    "current_page": 1,
    "total_pages": 10,
    "total_count": 250,
    "per_page": 25
  }
}

​

Quick Reference

​

Common Operations

• List Resources - GET /networks/{id}/members
• Get Resource - GET /networks/{id}/members/{member_id}
• Create Resource - POST /networks/{id}/posts
• Update Resource - PATCH /networks/{id}/members/{member_id}
• Delete Resource - DELETE /networks/{id}/spaces/{space_id}/members/{user_id}

​

Request Format

curl https://api.mn.co/admin/v1/networks/{network_id}/endpoint \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "User-Agent: my-app/1.0 (+https://example.com)"

​

Response Format

{
  "items": [...],
  "links": {
    "self": "current_page_url",
    "next": "next_page_url"
  }
}

​

Best Practices

1. Store tokens securely - Never expose API tokens in client-side code or public repositories
2. Handle rate limits - Implement exponential backoff when hitting rate limits
3. Use pagination - Always paginate through large result sets
4. Validate input - Validate data before sending to the API
5. Monitor errors - Log and monitor API errors for debugging

​

Support