Integration endpoints

This page covers the MatchZy settings you use when integrating a CS2 server with MatchZy Auto Tournament (or any external controller).

MatchZy loads a match by fetching JSON from a URL:

• Command: matchzy_loadmatch_url <url> [header_key header_value]

The URL should point to a match JSON document (typically hosted by MatchZy Auto Tournament).

If your match JSON endpoint requires a header (for example a bearer token):

MatchZy sends match events (webhooks) to your platform.

MatchZy Auto Tournament accepts events on:

• POST /api/events

• POST /api/events/:matchSlugOrServerId

• Set endpoint: matchzy_remote_log_url "<url>"

• Optional header:

  • matchzy_remote_log_header_key "<key>"
  • matchzy_remote_log_header_value "<value>"

In MAT-style setups, these values are typically configured by the platform via RCON when a match is allocated:

• matchzy_remote_log_url "https://mat.example.com/api/events/<matchSlug>"
• matchzy_remote_log_header_key "X-MatchZy-Token"
• matchzy_remote_log_header_value "<serverToken>"

If you record demos, MatchZy can upload them after each map:

• Endpoint: matchzy_demo_upload_url "<url>"
• Optional header:
  • matchzy_demo_upload_header_key "<key>"
  • matchzy_demo_upload_header_value "<value>"

MatchZy Auto Tournament accepts demo uploads on:

• POST /api/demos/:matchSlug/upload

Related settings:

• matchzy_demo_recording_enabled
• matchzy_demo_path
• matchzy_demo_name_format

MatchZy can upload a match report payload to your platform:

• matchzy_report_endpoint "<url>"
• matchzy_report_token "<token>"
• matchzy_report_server_id "<server_id>"

MatchZy Auto Tournament accepts match reports on:

• POST /api/events/report

You can also generate a report snapshot on demand:

• matchzy_match_report

These values help a controller understand what the server is doing:

• matchzy_server_id
• matchzy_tournament_status
• matchzy_tournament_match
• matchzy_tournament_next_match
• matchzy_tournament_updated