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

Remberg tickets API

The tickets API from Remberg — 4 operation(s) for tickets.

Remberg tickets API is one of 19 APIs that Remberg publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include tickets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 4 paths, and defines 18 schemas. It is described by OpenAPI 3.0.0, at version v1.

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

7 operations 4 paths 18 schemas 1 DELETE4 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Remberg tickets API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (authorization).

Paths & Operations 7

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

tickets 7
GET
/v2/tickets/categories
Get the available ticket categories as a tree structure
/v2/tickets/categories_get → 200400403
GET
/v2/tickets
Get a list of Tickets
/v2/tickets_get 14 params → 200400403
POST
/v2/tickets
Create a new Ticket
/v2/tickets_post body → 201400403
GET
/v2/tickets/{id}/conversations
Get a Ticket's conversations by its Ticket's internal ID
/v2/tickets/{id}/conversations_get 1 param → 200403404
GET
/v2/tickets/{id}
Get a Ticket by its internal ID
/v2/tickets/{id}_get 2 params → 200403404
PATCH
/v2/tickets/{id}
Update a Ticket by its internal ID
/v2/tickets/{id}_patch 1 param body → 204400403404
DELETE
/v2/tickets/{id}
Delete a Ticket by its internal ID
/v2/tickets/{id}_delete 1 param → 204400403404

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are TicketCfaResponseDto (23 properties), TicketsCfaCreateOneBodyDto (12 properties), TicketsCfaUpdateOneBodyDto (11 properties), TicketCfaConversationActivityResponseDto (6 properties). Each schema is shown below with its type and property counts.

CustomPropertyValueCreateCfaBodyDto
object
2 properties 2 required
CustomPropertyValueCfaResponseDto
object
3 properties 2 required
ContactInfoCfaResponseDto
object
4 properties 1 required
TicketCfaCategoryChildResponseDto
object
3 properties 3 required
TicketsCfaUpdateOneBodyDto
object
11 properties
TicketCfaResponseDto
object
23 properties 12 required
TicketCfaCategoryResponseDto
object
3 properties 3 required
CustomPropertyValueUpdateCfaBodyDto
object
2 properties 2 required
TicketCfaConversationResponseDto
object
1 property 1 required
TicketCfaCategoriesResponseDto
object
1 property
AssetInfoCfaResponseDto
object
3 properties 3 required
TicketCfaConversationActivityHeaderResponseDto
object
4 properties
OrganizationInfoCfaResponseDto
object
3 properties 2 required
TicketsCfaFindManyResponseDto
object
2 properties 2 required
PartWithQuantityResponseDto
object
2 properties 2 required
TicketCfaConversationActivityResponseDto
object
6 properties 4 required
TicketsCfaCreateOneBodyDto
object
12 properties 1 required
PartWithQuantityBodyDto
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

remberg-tickets-api-openapi.yml Raw ↑

Other APIs Remberg publishes across the network.

Remberg ai-chat API
Remberg asset-status-signals API
Remberg asset-types API
Remberg assets API
Remberg contacts API
Remberg failure-types API
Remberg files API
Remberg forms API
Remberg inventories API
Remberg organizations API
Remberg part-stock-changes API
Remberg parts API