This was a community REST API based on Uma Musume: Pretty Derby's meta and master.mdb files that was read from a MariaDB database. This was based on the Swagger UI/OpenAPI specification. I was using MariaDB instead of MySQL for the sake of keeping as much of this as open-source as possible.

I had written a loader app that allowed you to load the meta and master.mdb's data from the DMM version of this game into a MySQL/MariaDB database.

This project was retired on October 29, 2025, and the hosted API and its supporting apps have been shut down. I worked with Katboi from UmaViewer beforehand, so that app wasn't affected.

I had been meaning to step away from maintaining this project. By the time I retired it, I hadn't played the game in over three years, but I've always enjoyed this community and wanted to provide some kind of support for as long as I could. I open-sourced everything except the CI/CD, which was a very simple setup, so anyone who wants to pick up where I left off is welcome to fork it.

This API not only has endpoints to the tables, but I've created views for basic info for frequently used tables. I've even implemented stored procedures for a few particular calculations like parent compatibility and recommendations.

The overall endpoint structure is:

• Raw table data (imported straight from the meta and master.mdb files)
• Basic indexing of frequently used tables (endpoints prefixed with Basic)
• Condensed data of foreign keys to allow easier reporting (endpoints prefixed with Condensed)
• Nicely displayed data of frequently used info (endpoints prefixed with Nice)
• Stored procedures (endpoints prefixed with Sp)

The stored procedures are:

• SpSuccessionGrandparentRecommendation
  • This is the recommended grandparents based on the child's parent
• SpSuccessionParentRecommendation
  • This is the recommended parents based on the child
• SpSuccessionPointSum
  • This is the overall calculation based on the child's compatibility with the proposed parents and grandparents

Under UmaMusumeAPI/Properties/launchSettings.json, set the MARIA_CONNECTION_STRING environment variable to your MariaDB database for "development" and on the hosting site's config variables section for "release".

Simplified launchSettings.json Example:

"profiles": {
  "IIS Express": {
    "environmentVariables": {
      "ASPNETCORE_ENVIRONMENT": "Development",
      "MARIA_CONNECTION_STRING": "user id=;password=;host=;database=;character set=utf8mb4"
    }
  }
}

Use the scripts in UmaMusumeAPI/SqlScripts to generate everything you need for the database. As mentioned before, if you want to load all of the data from the DMM version of this game, use my loader app and point the connection string to your new database.

Make sure the MariaDB database and all of its objects have the character set of utf8mb4 and collation of utf8mb4_general_ci as that is the official UTF-8 specification. There are not only so many articles on this topic, but the devs from the Pomelo.EntityFrameworkCore.MySql project recommends this personally and in this issue. I'm using their EF Core library to help scaffold the models and controllers since it's far more active and stable than the Oracle equivalent.

In case if you need to scaffold anything, here are some commands that may be useful

This is a single-line command using the "Package Manager Console" in Visual Studio that allows you to generate ALL of the models and the DbContext class.

Scaffold-DbContext 'User Id=;Password=;Host=;Database=;Character Set=utf8mb4' Pomelo.EntityFrameworkCore.MySql -OutputDir Models -ContextDir Context

If you only need the model and context of a SINGLE table, here's the single-line command for that.

Scaffold-DbContext 'User Id=;Password=;Host=;Database=;Character Set=utf8mb4' Pomelo.EntityFrameworkCore.MySql -OutputDir Models -ContextDir Context -T <TABLE_NAME_HERE>