Skip to main content

​
Getting Started with MOOD MNKY APIs

This guide provides a quick introduction to working with MOOD MNKY APIs, helping you understand the key concepts and get up and running quickly.

​
API Ecosystem Overview

MOOD MNKY offers several categories of APIs:
  1. Platform APIs - Core functionality and e-commerce capabilities
  2. AI & Workflow APIs - AI model hosting, workflow automation, and agent integration
  3. Integration APIs - Connectivity with third-party services like Notion and Bungie

​
Authentication

Most MOOD MNKY APIs require authentication. The standard authentication method is JWT bearer tokens: 
curl -X GET "https://api.moodmnky.com/endpoint" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
To obtain an access token, you’ll typically need to:
  1. Register an application in the MOOD MNKY Developer Portal
  2. Use your client credentials to request an access token
  3. Include the token in your API requests
For detailed authentication instructions, see the Authentication Guide.

​
Making Your First API Request

Here’s a simple example of making a request to the Core API: 
// Using fetch
fetch('https://api.moodmnky.com/v1/users/me', {
  headers: {
    'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
    'Content-Type': 'application/json'
  }
})
.then(response => response.json())
.then(data => console.log(data));

​
Using the SDKs

For easier integration, we offer SDKs for popular programming languages: 
// Install: npm install @moodmnky/sdk
import { MoodMnkyClient } from '@moodmnky/sdk';

const client = new MoodMnkyClient({
  apiKey: 'YOUR_API_KEY'
});

const userProfile = await client.users.getProfile();
console.log(userProfile);
For more information about our SDKs, see:

​
API References & Playgrounds

Each API includes interactive documentation where you can:
  • Explore available endpoints
  • Test API calls directly in your browser
  • See request and response examples
Visit the API References section to access these interactive tools.

​
Common Concepts

​
Rate Limiting

API requests are subject to rate limiting to ensure fair usage. Rate limits are typically applied per API key and reset hourly. When a rate limit is exceeded, the API returns a 429 Too Many Requests status code. See Rate Limiting for details.

​
Pagination

List endpoints support pagination for large result sets: 
GET /v1/resources?limit=10&offset=20
Pagination parameters:
  • limit - Number of items to return (default: 20, max: 100)
  • offset - Number of items to skip (for offset-based pagination)
  • cursor - Cursor for cursor-based pagination (when available)

​
Error Handling

API errors follow a consistent format: 
{
  "error": {
    "code": "resource_not_found",
    "message": "The requested resource was not found",
    "status": 404,
    "details": {
      "resource_id": "123",
      "resource_type": "user"
    }
  }
}
See Error Handling for all error codes and resolution strategies.

​
Next Steps

Now that you understand the basics, you can:
  1. Explore the specific API documentation for your use case
  2. Set up proper authentication for your application
  3. Try out the interactive API playgrounds
  4. Check out our API standards to understand our API design principles
For any questions or issues, contact developer support or join our Discord community.