Skip to main content

About the Admin API

The Mighty Networks Admin API provides programmatic access to manage and automate your network operations. With the Admin API, you can manage members, content, events, and more.

Base URL

All API requests should be made to:
https://api.mn.co/admin

Authentication

The Admin API uses Bearer token authentication. All requests must include a valid API token.

Authentication Guide

Learn how to generate tokens, authenticate requests, and implement security best practices.

Getting Started

Core Resources

The Admin API provides access to the following resources:

Networks

Manage network settings, information, and configuration.

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

Rate Limit and Quota

These are stand-in numbers and do not represent real API rate limits upon its release
The Admin API implements a 200 requests per minute rate limiting to ensure fair usage. Each plan includes a specific number of requests, and a price-per-request for requests past your plan’s permitted volume:
PlanIncluded API RequestsExtra API Requests
Growth50,000 / month$0.002 / request
Mighty Pro Basic50,000 / month$0.002 / request
Mighty Pro Essential300,000 / month$0.001 / request
Mighty Pro Complete600,000 / month$0.0005 / request

Error Handling

The API uses standard HTTP status codes:
Status CodeDescription
200Success
201Created
400Bad Request - Invalid parameters
401Unauthorized - Invalid or missing API token
403Forbidden - Insufficient permissions
404Not Found - Resource doesn’t exist
429Too Many Requests - Rate limit exceeded
500Internal Server Error
Error responses include a JSON body with details:
{
  "error": "unauthorized",
  "message": "Invalid API token",
  "status": 401
}

Pagination

List endpoints support pagination using the following query parameters:
  • page: Page number (default: 1)
  • per_page: Items per page (default: 25, max: 100)
Pagination metadata is included in the response:
{
  "data": [...],
  "meta": {
    "current_page": 1,
    "total_pages": 10,
    "total_count": 250,
    "per_page": 25
  }
}

Webhooks

Coming Soon

Webhook support for real-time event notifications is coming soon.

Quick Reference

Common Operations

All API operations are scoped to a specific network:
  • 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

All requests require authentication and use standard REST conventions:
curl https://api.mn.co/admin/v1/networks/{network_id}/endpoint \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json"

Response Format

Successful list endpoints return paginated data:
{
  "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

Need help with the Admin API?