How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Remberg

Remberg tickets API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

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.2.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.2.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.

TicketCfaCategoryChildResponseDto
object
3 properties 3 required
TicketCfaCategoryResponseDto
object
3 properties 3 required
TicketCfaConversationActivityHeaderResponseDto
object
4 properties
PartWithQuantityResponseDto
object
2 properties 2 required
AssetInfoCfaResponseDto
object
3 properties 3 required
CustomPropertyValueCreateCfaBodyDto
object
2 properties 2 required
OrganizationInfoCfaResponseDto
object
3 properties 2 required
CustomPropertyValueCfaResponseDto
object
3 properties 2 required
TicketCfaConversationActivityResponseDto
object
6 properties 4 required
TicketCfaConversationResponseDto
object
1 property 1 required
CustomPropertyValueUpdateCfaBodyDto
object
2 properties 2 required
TicketCfaResponseDto
object
23 properties 12 required
TicketsCfaUpdateOneBodyDto
object
11 properties
TicketCfaCategoriesResponseDto
object
1 property
PartWithQuantityBodyDto
object
2 properties 2 required
TicketsCfaFindManyResponseDto
object
2 properties 2 required
ContactInfoCfaResponseDto
object
4 properties 1 required
TicketsCfaCreateOneBodyDto
object
12 properties 1 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
AE Profile APIs.io
Remberg asset-status-signals API
AE Profile APIs.io
Remberg asset-types API
AE Profile APIs.io
Remberg assets API
AE Profile APIs.io
Remberg contacts API
AE Profile APIs.io
Remberg failure-types API
AE Profile APIs.io
Remberg files API
AE Profile APIs.io
Remberg forms API
AE Profile APIs.io
Remberg inventories API
AE Profile APIs.io
Remberg organizations API
AE Profile APIs.io
Remberg part-stock-changes API
AE Profile APIs.io
Remberg parts API
AE Profile APIs.io
#Tickets
← Back to R APIs
API Details
ID
remberg:remberg-tickets-api
Base URL
https://api.remberg.de
Docs
https://developers.remberg.de/reference
Provider
Remberg
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=remberg-tickets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/remberg-tickets-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Remberg tickets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.