Feature Support

What the AyakaMods API supports today, mapped against the AyakaMods SDK feature surface (for anyone porting a AyakaMods-style integration).

info

AyakaMods is a XenForo-native platform. Its API covers the mod catalog and submission fully. The client-side mod-manager loop (subscribe -> auto-install/update) is not yet exposed as an API - see the gaps below.

Supported today

Capability	Endpoint
List / browse mods (filters, sort, pagination)	GET mods/
Get a mod	GET mods/{id}/
Mods by author	GET mods/?creator_id=
Game info	GET mod-games/, mod-games/{id}/
Categories / tags	GET mod-categories/ (+ flattened)
Versions	GET mods/{id}/versions/, mod-versions/{id}/
File download	GET mod-versions/{id}/download
Updates (changelog)	GET mods/{id}/updates/
Reviews (read)	GET mods/{id}/reviews/
Comments	GET mod-comments/
Submit / edit / delete a mod	POST mods/, POST mods/{id}/, DELETE mods/{id}/
Publish a new version	POST mod-versions/

Not yet supported (roadmap)

Capability	Status
Subscriptions + auto install/update loop	Not in API. The core of a Vortex-style manager; needs a subscriptions endpoint set on the AyakaMods side.
Dependencies / load order	Not implemented (metadata stub only).
Mod collections	Exist on-site, not exposed via API.
Report content	Not in API.
In-SDK auth (Steam/console/OAuth SSO)	AyakaMods uses XF-Api-Key (+ optional XF-Api-User), not platform SSO.
Monetization (wallet / purchase / entitlements)	AyakaMods uses external purchase URLs only.
Metrics, multiplayer, user follow/mute	Not applicable.

What this means for porting a AyakaMods SDK

• A catalog + submission client (browse, download, upload) maps cleanly onto the API today.
• An auto-installing mod manager needs the subscription/install endpoints added first.
• The transport differences (single host, /api base path, XF-Api-Key header instead of ?api_key=) are already handled in the AyakaMods SDK fork - see Custom Engine / C++ SDK.