Skip to main content
Connector Studio helps you design and generate API connectors. A connector is an integration component that translates requests and responses between two API specifications. One specification belongs to your requesting side and one to your responding side. Grand Central can be the requester or the responder. With Connector Studio, you:
  • Upload API specifications in OpenAPI or Web Services Description Language (WSDL) format.
  • Create a connector project that links a requester organization to a responder organization.
  • Map endpoints and fields, with help from AI suggestions or by hand.
  • Generate JOLT or XSLT transformations from your approved mappings.
  • Design Camel routes in Route Builder from templates, the canvas, or the Route Builder agent.
Connector Studio is part of the Grand Central integration platform. Use it for a guided interface or for an integrated development environment (IDE) workflow through Model Context Protocol (MCP). Both paths take you from vendor specifications to generated transformations and routes without writing every mapping by hand.

​
Workflow at a glance

You build a connector in six stages, in this order:
  1. Upload API specifications. Register each vendor and upload its specifications. Wait until each specification reaches the Indexed status.
  2. Create a project. Link the requester organization to the responder organization.
  3. Map endpoints. Match each source API operation to a target operation. AI suggests the matches, and you approve them. You can also map endpoints by hand.
  4. Map schemas. Match the fields inside each operation. AI suggests the matches, and you review them. You can also map fields by hand.
  5. Generate transformations. Connector Studio produces JOLT or XSLT files from your approved mappings.
  6. Design routes. In Route Builder, scaffold routes, start from a template, edit on the canvas or with the agent, then download Java or YAML.

​
What is Route Builder?

Route Builder is where you design the Camel route for each operation: the path from an inbound API call through the vendor call and transformation to the response. Mapping Workspace covers field mappings. Route Builder covers the runtime flow. For more information, see Design routes with Route Builder. After step 5, download the transformation files from the project. After step 6, export the route design.

​
Rules to follow

  • A responder needs at least one Indexed specification before you can create a valid project.
  • Map endpoints before you map schemas. Match which API calls align before you match the fields inside them.
  • Map schemas only after you approve or receive a suggestion for at least one endpoint pair.
  • You can map endpoints and schemas by hand, not only through AI suggestions.

​
Who this documentation is for

These pages are for connector creators, builders, and administrators who already have access to Grand Central. The pages describe how the product behaves in your installation. They don’t describe how to register for an account.