Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Capmo Project Tickets API

The Project Tickets API from Capmo — 2 operation(s) for project tickets.

Capmo Project Tickets API is one of 23 APIs that Capmo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Project Tickets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against a single base URL, https://api.capmo.de.

5 operations 2 paths 5 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Base URL
https://api.capmo.de/api/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Capmo Project Tickets API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (CapmoAuth).

  • CapmoAuth — For authentication, use the custom prefix followed by a space and then your API key. Example: "Capmo YOURAPIKEY".

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Project Tickets 5
GET
/api/v1/projects/{projectId}/tickets
This can be used to list all project tickets in a paginated response.
getProjectTicketsPaginated 6 params → 200400401403404409500
POST
/api/v1/projects/{projectId}/tickets
This can be used to create a new project ticket. Please note: - Project ticket categories, tags, types, etc. have their own endpoints to be managed. They can be added on ticket creation if they alrea…
createProjectTicket 2 params body → 201400401403404409500
GET
/api/v1/projects/{projectId}/tickets/{ticketId}
This can be used to get a specific project ticket by its id.
getProjectTicket 3 params → 200400401403404409500
PATCH
/api/v1/projects/{projectId}/tickets/{ticketId}
This can be used to update a specific project ticket by its ID.
updateProjectTicket 3 params body → 200400401403404409500
DELETE
/api/v1/projects/{projectId}/tickets/{ticketId}
This can be used to delete a specific project ticket by its ID.
deleteProjectTicket 3 params → 200400401403404409500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ReadProjectTicketDto (26 properties), UpdateProjectTicketDto (12 properties), CreateProjectTicketDto (12 properties), PaginatedOutputDto (3 properties). Each schema is shown below with its type and property counts.

PaginatedOutputDto
object
3 properties 3 required
CreateProjectTicketDto
object
12 properties
ReadProjectTicketDto
object
26 properties 25 required
UpdateProjectTicketDto
object
12 properties
TicketStatus
string
The status of the ticket.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

capmo-project-tickets-api-openapi.yml Raw ↑

Other APIs Capmo publishes across the network.

Capmo Organisation Companies API
Capmo Organisation Memberships API
Capmo Organisation People API
Capmo Organisation Projects API
Capmo Other API
Capmo Project Change Orders API
Capmo Project Companies API
Capmo Project Documents API
Capmo Project Memberships API
Capmo Project People API
Capmo Project Permission Sets API
Capmo Project Plans API