FTB API Policy

Over the last few months, we have restructured our infrastructure, and with that have come changes to how you can programmatically get our Modpacks.

We are no longer using the ModpacksCH API to power our app; instead, this has been replaced by our own Modpack API.

Although we expect to rewrite a number of endpoints starting with v2, we have maintained schema compatibility with ModpacksCH for now. Our endpoints remain the same; you just need to change the URL root.

Where you previously used the prefix https://api.modpacks.ch/, you should now use https://api.feed-the-beast.com/v1/modpacks/. You can see FTB Evolution’s manifest here:
https://api.feed-the-beast.com/v1/modpacks/public/modpack/125

We are currently working on properly documenting these endpoints, and the documentation will be available on our docs site soon.

Our previous announcement about modpacks once again being available on CurseForge has prompted us to reconsider other third-party launchers’ use of our API. We previously asked these launchers to remove our content. Although our stance is still that we’d prefer users download our content first through the FTB App—and secondly via CurseForge—we are now allowing third-party launchers to re-integrate our API with the understanding that we will not revoke this access.

We ask that you use a custom User-Agent for your requests so we can contact you if we notice any issues with your usage.