Changelog

Added

• Developer and Pro monthly API plans are now available from the pricing page.
• Paid plans include account API keys, higher rate limits, and access to key management.
• Subscribers can create, name, rotate, and revoke API keys from the account area.
• Billing, invoices, plan changes, and cancellations can be managed through Stripe.

Security

• API keys are shown only once after creation.
• Lost or exposed keys can be revoked and replaced from the account area.

No existing public API response schemas were changed.

Added

• Public Arma Reforger mods browser, now available at /mods/, powered by the public API, with search, sorting, pagination, mod detail pages, copy-mod-ID and copy-JSON actions, and correct handling of 202 Accepted refreshes.
• Config.json tools for server admins: a config validator with local, in-browser JSON and structure checks, a config generator with a form editor, live JSON preview, import/export, and a mod manager for the game.mods array with name resolution, reordering, duplicate detection, and dependency suggestions.
• Shared working config across tools. Add to Config in the mod browser, the mod manager, and the config generator all edit the same browser-only draft.
• API quickstart page and new guides for config.json, adding mods, troubleshooting, running server mods, API integration, and refresh jobs.
• API documentation now includes client identity guidance, conditional request examples, and complete code examples in curl, JavaScript, and Go.
• Inline Workshop mod search inside the config generator and mod manager.
• JSON syntax highlighting in the config validator editor and generator live preview.

Changed

• Homepage now presents both the API and the server-admin tools.
• Site navigation includes the tools and guides sections.
• Tool pages use a full-width desktop layout with refreshed colors and spacing.
• Common mod lists, searches, and mod detail pages load more reliably from cache.

No API endpoint, response-schema, or integration changes. The deprecated unversioned API aliases remain untouched.

Fixed

• Resolved Workshop image, mod, dependency, and scenario URLs through the Workshop base URL so both relative paths and absolute upstream URLs are handled correctly.
• Preserved absolute CDN or Workshop URLs instead of prefixing them with the Workshop host.

No API endpoint, response-schema, or integration changes are required.

Fixed

• Mods with scenarios missing scenario IDs.
• Mods with scenarios missing scenario player counts.

No API endpoint, response-schema, or integration changes are required.

Fixed

• Improved handling for unexpected Workshop scenario data during refreshes.
• Refresh failures now return clearer errors without interrupting unrelated API requests.

No API endpoint, response-schema, or integration changes are required.

Improved reliability when Arma Reforger Workshop pages are slow or temporarily unavailable.

Changed

• Cached API responses now return immediately where possible.
• Stale cached data can be served while the API refreshes it in the background.
• Uncached requests may return 202 Accepted while fresh Workshop data is being prepared.
• Added refresh-job status URLs for integrations that want to show loading progress.
• Added clearer cache, retry, and rate-limit response headers.

Integration Note

Clients should continue handling normal 200 OK responses as before. When an uncached resource returns 202 Accepted, wait for Retry-After and retry the original URL. Polling the Location job URL is optional.

Fixed

• API requests no longer wait for a full upstream Workshop scrape before responding.

v1.0.0 marks the public return of reforgermods.net and the Reforger Mods API after a period offline.

Earlier iterations of the project are retired and are not compatible with this release. This version establishes the current API foundation and public documentation.

Included

• Read-only versioned /v1 API routes for health checks, mod lists, search, and mod details.
• Cached metadata sourced from publicly accessible Arma Reforger Workshop pages.
• Anonymous public rate limiting.
• Stale-cache fallback for safe read endpoints when upstream Workshop pages are slow or temporarily unavailable.
• Controlled JSON error envelopes with request IDs for support and debugging.
• Public documentation for API routes, caching behavior, limits, and supported usage.

Notes

• This is an independent, unofficial project and is not affiliated with or endorsed by Bohemia Interactive.
• Workshop data is cached and may not always reflect the latest upstream changes immediately.
• New integrations should use the versioned /v1 routes.