APIMATIC API Transformer

Name: APIMATIC API Transformer API
Brand: APIMATIC API Transformer
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage RegistryapiKey, basic1 EndpointsREST

For Agents

Convert an API description from one format to another (OpenAPI, Swagger 2.0, RAML, API Blueprint, WSDL, Postman Collection) through one /transform call.

Quickstart

Get started with APIMATIC API Transformer in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"convert an api description format"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with APIMATIC API Transformer API.

Convert a Swagger 2.0 description into OpenAPI 3.0 in one POST /transform call

Translate a RAML 1.0 file to OpenAPI 3.0 for tooling that does not read RAML

Generate an OpenAPI description from a Postman Collection so it can be imported into spec-first tools

Output an APIMATIC-formatted description suitable for SDK generation downstream

GET STARTED

Start building with APIMATIC API Transformer API

Explore with Jentic

View OpenAPI Document

Use for: Convert a Swagger 2.0 file to OpenAPI 3.0, Translate a Postman Collection into an OpenAPI spec, Turn a RAML description into OpenAPI 3.0 so I can host it on Stoplight, Generate an APIMATIC format description from my OpenAPI file

Not supported: Does not host specs, generate SDKs, or run linting — use for one-shot conversion between API description formats only.

Jentic publishes the only available OpenAPI document for APIMATIC API Transformer, keeping it validated and agent-ready.

APIMATIC API Transformer is a single-endpoint service that converts API description files between formats such as OpenAPI, Swagger 2.0, RAML, API Blueprint, WSDL, Postman Collection, and APIMATIC's own format. The /transform endpoint accepts an input format identifier and the source file body, then returns the converted description. It is widely used in CI pipelines that need to keep multiple API description formats in sync from one canonical source. Authentication is by APIMATIC API key in the request or by HTTP basic credentials.

Use Cases

Patterns agents use APIMATIC API Transformer API for, with concrete tasks.

★ Spec format normalisation in CI

Run POST /transform as a CI step so that pushing a single canonical description automatically produces alternative formats for downstream consumers. Teams can keep an OpenAPI 3.0 source of truth and emit Postman, RAML, or APIMATIC descriptions with one HTTP call per target. This avoids drift between the canonical spec and the formats published to partners or developers.

POST /transform with input_format=APIMATIC, output_format=OpenApi3Json, and the canonical APIMATIC file as the body.

Migrating from Swagger 2.0 to OpenAPI 3.0

Migrate legacy Swagger 2.0 files to OpenAPI 3.0 in bulk by scripting the /transform endpoint over a directory of specs. The conversion handles structural differences such as parameters, requestBody, and components so engineering teams do not need to rewrite every spec by hand. The output is a clean OpenAPI 3.0 document ready to lint, render, and host.

POST /transform with input_format=Swagger20, output_format=OpenApi3Json, and the legacy file body, then save the response as the new spec.

Generating Postman Collections from OpenAPI

Produce an up-to-date Postman Collection from an OpenAPI 3.0 source as part of every release so QA engineers always test against the latest contract. /transform accepts OpenApi3Json or OpenApi3Yaml as input and emits Postman_2.1 as output. The result can be imported into a shared Postman workspace or attached to a release artefact.

POST /transform with input_format=OpenApi3Json, output_format=Postman_2.1, and the current spec, then upload the resulting collection to Postman.

Agent-driven format conversion

An agent integrating with a partner that only accepts a specific description format can transform whatever the user provides into that format on the fly through Jentic. The conversion is one call, the credentials sit in the Jentic vault, and the agent only needs to know which input and output formats are required. This removes a common friction point in agent-driven onboarding flows.

Through Jentic, search 'convert an api description format', load the apimatic.io /transform operation, and execute with input and output formats and the source file.

Key Endpoints

1 endpoints — apimatic api transformer is a single-endpoint service that converts api description files between formats such as openapi, swagger 2.

METHOD

PATH

DESCRIPTION

POST

/transform

Convert an API description from one format to another

POST

/transform

Convert an API description from one format to another

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your APIMATIC apikey or basic credentials are stored encrypted in the Jentic vault. Agents call /transform through a scoped Jentic token and the credential is applied at execution, so the raw value never enters the agent context.

Intent-based discovery

Agents search Jentic for 'convert an api description format' and Jentic returns the apimatic.io /transform operation with its input_format, output_format, and request-body schema.

Time to first call

Direct integration is straightforward but still requires writing the multipart upload and credential plumbing. Through Jentic the same conversion is callable in minutes via search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

SwaggerHub API

SmartBear platform that hosts and validates API specs in multiple formats.

Choose SwaggerHub when you need a hosted design surface, not just one-off format conversion.

Alternative

Stoplight

Spec-first design and docs hub with format support.

Choose Stoplight when interactive design and lint rules matter more than scripted conversion.

Complementary

GitHub API

Source-control surface where spec files live before conversion.

Use the GitHub API to read the canonical spec from a repo, then call /transform to emit alternate formats.

FAQs

Specific to using APIMATIC API Transformer API through Jentic.

What authentication does the APIMATIC API Transformer use?

The API supports two schemes: an apiKey credential and HTTP basic auth. Use whichever your APIMATIC plan provides. When called through Jentic, the chosen credential is held in the Jentic vault and applied to the request server-side.

Which input and output formats does /transform support?

The Transformer covers OpenAPI 3.0 (JSON and YAML), Swagger 2.0, Swagger 1.x, RAML 0.8 and 1.0, API Blueprint, WSDL, Postman Collection 1.0/2.0/2.1, and APIMATIC's own format. Pass the input_format and output_format identifiers in the request and the source as the body.

Can I convert OpenAPI 3.0 into a Postman Collection?

Yes. POST /transform with input_format=OpenApi3Json (or OpenApi3Yaml) and output_format=Postman_2.1, and supply the source spec as the body. The response is a Postman Collection 2.1 file.

How do I run a format conversion through Jentic?

Search Jentic for 'convert an api description format', load the apimatic.io /transform operation, and execute with input_format, output_format, and the source spec contents. Jentic returns the converted description without exposing the API key to the agent.

What are the rate limits for the API Transformer?

Rate limits are not declared in the OpenAPI spec and depend on your APIMATIC plan tier. Treat HTTP 429 responses as a back-off signal and check the APIMATIC dashboard for current quotas.