Skip to content

OpenAPI Designer

The Talisman OpenAPI Designer is a visual workspace for architecting RESTful APIs. It allows developers to model HTTP interactions, define strict data contracts, and configure security schemes using a component-first approach.

Unlike the centralized AsyncAPI model, the OpenAPI Designer maintains a dedicated openapi.json specification file for each project, serving as the definitive contract for that specific microservice.

image

Architecture Overview

The design process follows a 3-phase workflow: Configuration → Contract → Generation.

Configuration

Before defining endpoints, you define the reusable building blocks. This ensures consistency across your API and reduces duplication.

Servers

Define the environments where this API will be hosted.

  • Action: Add URLs for Development, Staging, and Production.
  • Variables: Support variable substitution (e.g., {port}) for dynamic environments.

Data Types

Define the shape of your domain objects.

image

Generate Request Bodies, Responses, Paths and Default Operation if required.

image

  • Purpose: Ensures strict typing for requests and responses.
  • Example: User, OrderDetails.

Request Bodies & Responses

Create standard payloads and return states.

image

  • Request Bodies: Reusable inputs (e.g., CreateUserRequest using the User Data Type).
  • Responses: Standard HTTP outcomes (e.g., 200 OK, 404 Not Found, 500 Error).

Security & Tags

  • Security Requirements: Define authentication mechanisms (e.g., BearerAuth, ApiKey).
  • Tags: Organize your API endpoints into logical groups (e.g., "Admin", "Public").

Contract

Once the components exist, you assemble them into actual API endpoints.

Paths

Define the URL structure of your resource.

  • Action: Create paths like /users or /users/{id}.
  • Parameters: Define dynamic path variables (e.g., {id}) or query parameters.

Operations

Define the HTTP actions (verbs) available on those paths.

image

  • Action: Add GET, POST, PUT, DELETE operations.
  • Link: Associate the Request Bodies and Responses created in Configuration phase to these operations.
  • Security: Apply specific Security Requirements (e.g., "Only Admin can DELETE").

Generation

The final phase transforms your REST contract into executable Camel routes.

Routes

Talisman generates the Apache Camel Route with direct:{{operationId}} for each Operation

image

  • Output: Creates Camel route files (e.g., direct-{{operationId}}.camel.yaml) inside the project.
  • Direct Integration: Each operation (e.g., GET /users with operationId==getUsers) is linked to a direct consumer(e.g., direct:getUsers) where the business logic is implemented.

Operations TryOut

Talisman features TryOut, a powerful, built-in testing interface similar to Postman. This allows engineers to validate APIs against the live environment without leaving the browser.

When viewing the details of an Operation, click the TryOut button. This opens the interactive testing console for that specific endpoint.

image

For details on configuring requests and environments, please refer to the TryOut page.

Runtime Observability

When the API is running, Talisman provides deep insights into traffic patterns directly on the project topology. Integration engineers can visualize the complete flow of the REST API in a single graph. The central OpenAPI Definition connects to all the specific Camel routes that implement its operations.

image

  • Traffic Monitoring: Real-time metrics are overlaid on the graph nodes.
  • Metric Counters: Observe the exact count of messages Received, Failed, and Inflight for the main API entry point and each individual operation route.
  • Drill-Down: Click into any route node (e.g., Direct Add Pet) to investigate specific logic or performance bottlenecks.