Before you begin

This tutorial uses the Market Registry API to find the markets Chainlink resolves and follow their progress. By the end, you will have listed the markets for one competition and read the status of each event.

The Market Registry API is read-only. It returns the catalog: events, their markets, each market's resolution criteria, and each event's status. Outcomes reach your platform separately, as agreed with Chainlink; see Outcome delivery.

The tutorial path

Step	You do	You end with
1. List markets	Find a competition in coverage and fetch its upcoming events	Each market's slug, question, and resolution criteria
2. Track event status	Poll the same date window and read each event's status	A view of which events are open, resolving, or done

Both steps use the same example: Major League Baseball games, grouping mlb.

Prerequisites

A Market Registry API key. Request one from the Chainlink team. The key belongs to your organization and must have Prediction Markets access enabled.
curl and jq in a terminal.

Set your API key

Set the base URL and your key. Run every command in this tutorial in the same terminal.

export MARKETS_API_URL='https://markets.api.chain.link/user/v1'
export MARKETS_API_KEY='YOUR_API_KEY'

For this tutorial, keep the key in your terminal session only. Do not ship it in a trader-facing app.

Confirm the key works:

curl --silent --show-error --output /dev/null --write-out '%{http_code}\n' \
  --header "Authorization: ApiKey ${MARKETS_API_KEY}" \
  "${MARKETS_API_URL}/taxonomies"

The command prints 200. A 401 or 403 means the key is missing, invalid, or not enabled for Prediction Markets; contact the Chainlink team.

Next step

1. List markets

Please note, this repo contains community examples only — these are not Chainlink products or services and are not supported or maintained by Chainlink. This code represents an example of using a Chainlink product or service, and is intended for demonstration and educational purposes only. It is provided “AS IS” and “AS AVAILABLE” without warranties of any kind, may not have been audited, and may omit checks or error handling. Each party intending to use this example code does so entirely at their own risk and must perform its own audits, security and code review, key management, and testing before any production deployment and ensure the operation and performance of such code matches expectations. Neither Chainlink Labs nor the Chainlink Foundation deploys, operates, monitors, maintains or endorses any deployment of this code. Note that this is not a Chainlink product, feature or service, and there are no commitments made with respect to the code, including compatibility with future Chainlink releases. You should not rely on this code without first conducting your own technical, engineering, and security review. This code is also outside the scope of any Chainlink bug bounty programs. Neither Chainlink Labs, the Chainlink Foundation, nor Chainlink node operators are responsible for outcomes due to errors in this example or how it is deployed or operated, or liable for any resulting claims or damages. Use of the Chainlink Network is subject to the Chainlink Foundation Terms of Service, which provides important information and disclosures. By using this code, you acknowledge and agree to these terms.

Before you begin

The tutorial path

Prerequisites

Set your API key

Next step

Get the latest Chainlink content straight to your inbox.