Components API

A component is one application a project is made of: the web app, the API, a mobile app, a background service, an integration, a database or the platform itself. Environments name the component they run, stories and requirements will tag the components they touch, and a release will carry a version per component; the slug is what a version string names the component by (web@1.4.0), so it is unique within the project and stays while the row exists.

The reads here see the components of the projects the token may see. A component outside that set is a 404 RESOURCE_NOT_FOUND, never a 403, so the API cannot be used to learn that a component exists. Every write runs the same action the Components page runs, under the project permissions (the team owner, then the person's project role, then their team role), and announces itself as a component.* event.

EndpointsCopy Anchor Link

Related

Projects APIThe project a component belongs to.Environments APIWhere a component runs.Activity APIWhat changed on a component and who did it.component.* eventsThe lifecycle of a project's components: creation, edits, archiving, restoring and deletion.