Skip to main content

API and OpenAPI Documentation

Mind Your Now provides a comprehensive REST API with full OpenAPI specification. You can explore all endpoints through our interactive Swagger UI documentation or integrate directly using the JSON schema.

API Base URL

Production API: https://api.mindyournow.com

Interactive Documentation

🔗 Explore Mind Your Now API →

Our Swagger UI provides:

  • Interactive Testing: Test API endpoints directly from the browser
  • Request/Response Examples: See real data formats and expected parameters
  • Authentication Flows: Understand how to authenticate your requests
  • Complete Schema: Download OpenAPI JSON at https://api.mindyournow.com/v3/api-docs

Authentication

Most endpoints require an API key.

  • Header: X-API-KEY: <your_api_key>
  • Optional (not recommended): query parameter x-api-key=<your_api_key>

Generate and manage your keys from your account settings (API Keys).

Example

curl -H "X-API-KEY: YOUR_API_KEY" \
"https://api.mindyournow.com/api/tasks"

Refer to the Swagger UI for request/response schemas, parameters, and example payloads.

Calendar Meeting Actions

Control your calendar meetings programmatically with our meeting action endpoints.

Skip Meeting

POST /api/v2/calendar/events/{eventId}/skip

Description: Skip a meeting without sending external notifications. This is a personal preference that doesn't affect the calendar event or notify other attendees.

Parameters:

  • eventId (path, required): The calendar event ID

Request Body:

{
"meetingId": "string",
"skipReason": "string (optional)"
}

Response: MeetingActionResponseDTO

{
"success": true,
"message": "Meeting marked as skipped",
"meetingId": "string",
"action": "skip"
}

Use Cases:

  • Skip optional recurring meetings
  • Mark meetings as not attending without formal decline
  • Personal time management without external notifications

Decline Meeting

POST /api/v2/calendar/events/{eventId}/decline

Description: Decline a calendar invitation. This sends a decline notification through your connected calendar (Google Calendar or Microsoft Outlook) to the organizer and attendees.

Parameters:

  • eventId (path, required): The calendar event ID

Request Body:

{
"eventId": "string",
"declineReason": "string (optional)"
}

Response: MeetingActionResponseDTO

Requirements:

  • User must be an attendee (not the organizer)
  • Connected calendar account required (Google or Microsoft)

Use Cases:

  • Formally decline meeting invitations
  • Respond to double-bookings
  • Communicate schedule conflicts professionally

Cancel Meeting

POST /api/v2/calendar/events/{eventId}/cancel

Description: Cancel an entire meeting (organizer only). This sends cancellation notifications through your connected calendar to all attendees.

Parameters:

  • eventId (path, required): The calendar event ID

Request Body:

{
"eventId": "string",
"cancellationReason": "string (optional)"
}

Response: MeetingActionResponseDTO

Requirements:

  • User must be the meeting organizer
  • Connected calendar account required (Google or Microsoft)

Use Cases:

  • Cancel meetings you organized
  • Notify all attendees professionally
  • Free up calendar time for all participants

Authentication Notes

All calendar meeting action endpoints require:

  • JWT Authentication: Valid user session token
  • Calendar Connection: Active Google Calendar or Microsoft Outlook integration
  • Permissions: Appropriate permissions for the calendar event (attendee for decline, organizer for cancel)

Error Responses

All endpoints return standard error responses:

400 Bad Request: Invalid request parameters

{
"success": false,
"message": "Invalid request parameters",
"action": "decline"
}

401 Unauthorized: Missing or invalid authentication

{
"error": "Unauthorized",
"message": "Valid authentication required"
}

403 Forbidden: Insufficient permissions

{
"success": false,
"message": "Only meeting organizers can cancel meetings",
"action": "cancel"
}

404 Not Found: Event not found

{
"success": false,
"message": "Calendar event not found",
"action": "skip"
}

500 Internal Server Error: Server-side failure

{
"success": false,
"message": "Internal server error while processing meeting action",
"action": "decline"
}

For complete API documentation including all endpoints, schemas, and interactive testing, visit our Swagger UI.