Update Event Status

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://docs.maddenanalytics.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "Madden Analytics API MCP server": {
    "url": "https://docs.maddenanalytics.com/mcp"
  }
}

Close
PATCH /v2/api/events

Set event status to completed or failed. Only pending events (with both completed_at and failed_at NULL) can be updated. When setting status to 'completed', completed_at is set and failed_at is cleared. When setting status to 'failed', failed_at is set and completed_at is cleared. This is a once-only operation - events cannot be re-processed once marked as completed or failed. Returns 409 Conflict if event is already processed, 404 Not Found if event doesn't exist.

application/json

Body Required

Status update with id and status. Status must be 'completed' or 'failed'

  • id string
  • status string

    Values are completed or failed.

Responses

  • 200 application/json

    Returns id and updated:true when event was successfully updated

    Hide response attributes Show response attributes object
    • id string
    • updated boolean
  • 404 application/json

    Event not found

    Hide response attributes Show response attributes object
    • error string
    • message string
    • statusCode integer
  • 409 application/json

    Event already processed

    Hide response attributes Show response attributes object
    • error string
    • message string
    • statusCode integer
  • default application/json

    All errors will return the same object with a describing code & message

    Hide response attributes Show response attributes object
    • error string
    • message string
    • statusCode integer
PATCH /v2/api/events
curl \
 --request PATCH 'https://api.maddenanalytics.com/v2/api/events' \
 --header "Authorization: $API_KEY" \
 --header "Content-Type: application/json" \
 --data '{"id":"string","status":"completed"}'
Request examples
{
  "id": "string",
  "status": "completed"
}
Response examples (200)
{
  "id": "string",
  "updated": true
}
Response examples (404)
{
  "error": "Error Type (if any)",
  "message": "Message describing the error",
  "statusCode": 400
}
Response examples (409)
{
  "error": "Error Type (if any)",
  "message": "Message describing the error",
  "statusCode": 400
}
Response examples (default)
{
  "error": "Error Type (if any)",
  "message": "Message describing the error",
  "statusCode": 400
}