Redmine
Redmine is a flexible open source project management web application written in Ruby on Rails that supports multiple projects, issue tracking, Gantt charts, wikis, forums, time tracking, and SCM integration. The Redmine REST API exposes JSON and XML endpoints for issues, projects, users, time entries, wiki pages, attachments, and more. Authentication is supported via HTTP Basic credentials or per-user API keys, with optional user impersonation for administrator accounts.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Redmine the way a machine reads it — 22 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Redmine scores 26.7/100 (emerging), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Redmine
Each block below is one kind of artifact we hold for Redmine. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Redmine REST API
REST API for Redmine providing JSON and XML access to issues, projects, users, time entries, wiki pages, attachments, versions, and other entities. Authentication uses HTTP Basi...
Redmine Attachments API
The Attachments API from Redmine — 1 operation(s) for attachments.
Redmine Custom Fields.json API
The Custom Fields.json API from Redmine — 1 operation(s) for custom fields.json.
Redmine Groups.json API
The Groups.json API from Redmine — 1 operation(s) for groups.json.
Redmine Issue Statuses.json API
The Issue Statuses.json API from Redmine — 1 operation(s) for issue statuses.json.
Redmine Issues API
The Issues API from Redmine — 1 operation(s) for issues.
Redmine Issues.json API
The Issues.json API from Redmine — 1 operation(s) for issues.json.
Redmine My API
The My API from Redmine — 1 operation(s) for my.
Redmine Projects API
The Projects API from Redmine — 1 operation(s) for projects.
Redmine Projects.json API
The Projects.json API from Redmine — 1 operation(s) for projects.json.
Redmine Roles.json API
The Roles.json API from Redmine — 1 operation(s) for roles.json.
Redmine Time Entries API
The Time Entries API from Redmine — 1 operation(s) for time entries.
Redmine Time Entries.json API
The Time Entries.json API from Redmine — 1 operation(s) for time entries.json.
Redmine Trackers.json API
The Trackers.json API from Redmine — 1 operation(s) for trackers.json.
Redmine Uploads.json API
The Uploads.json API from Redmine — 1 operation(s) for uploads.json.
Redmine Users API
The Users API from Redmine — 1 operation(s) for users.
Redmine Users.json API
The Users.json API from Redmine — 1 operation(s) for users.json.
Redmine Wiki Pages.json API
The Wiki Pages.json API from Redmine — 1 operation(s) for wiki pages.json.
Scroll within the panel for all 18 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Redmine REST API
OPEN COLLECTIONSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Redmine — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/redmine · machine-readable index on apis.io