com.aditus.developers/developer-portal

ADITUS Developer Portal MCP

Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.

1.0.0
Version
remote
Transport
5
Tools

Security review

Review passed

Reviewed Jan 1, 2000.

  • tools: 5 tools scanned
  • metadata: scanned

No findings.

Tools (5)

  • search_docs

    Full-text search across API modules, endpoints (name, path, description) and the integration guides (Shop Micro Frontend, Guidelines, Webhooks). The reference is English; German search terms are understood as well (a generated language layer maps them onto the English vocabulary, e.g. 'aussteller' → exhibitor, 'gutschein' → voucher). Returns ranked hits with ids usable in get_endpoint / get_guide.

  • list_modules

    All top-level ADITUS API modules with direction (inbound = your systems call ADITUS, outbound = ADITUS data into your systems), endpoint counts and documentation URLs. Also lists the integration guides.

  • list_endpoints

    Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.

  • get_endpoint

    Full contract of one endpoint: method, URL, auth, query and header parameters, request body example, example responses (large bodies truncated, full text on the docs page). Accepts the endpoint id from search/list, or 'METHOD /path'. Path parameters may use any name or spelling (':cart', '{cartId}', a concrete value); a leading '/api' or '/v1' is ignored. Some routes are recorded several times with different query parameters: a reference without query string resolves to the recording without query parameters, a reference with a query string (e.g. '?$expand=All') to the recording with exactly (or at least) those keys. If that still leaves several recordings, the result is { ambiguous: true, candidates: [{ id, name, method, path }] } instead of the contract — call again with one of the candidate ids. When nothing matches, the error lists the nearest endpoints of that method.

  • get_guide

    Markdown of an integration guide. 'micro-frontend' is the Shop Micro Frontend contract (mounting, sessions, styling, Web Component, lifecycle, security); module guides such as 'guidelines' or 'webhooks' come from the API reference. Pass a section heading to fetch only that section.