Versioning

This page helps you understand the differences between both the Classic Version and Enhanced Version so you can choose the right version for your integration — or plan a migration if you are on the Classic Version.

Overview

Both Classic and Enhanced Version support the same use cases and the same authentication mechanism. The core difference is the API design — the Enhanced Version delivers the same business capabilities through a modernized endpoint structure.

API architecture

The Enhanced Version introduces a redesigned API architecture with new endpoint paths, request/response structures, and naming conventions. The business use cases remain the same — only the technical surface has changed.

Endpoint naming

The most visible difference is how endpoints are named and organized. For example:
Key differences in naming convention:
  • Path structure — Classic uses a deep, operation-oriented path. Enhanced uses a shallow, resource-oriented path.
  • Resource naming — Classic uses lowercase action verbs (e.g.
    inquiryAccount
    ). Enhanced uses PascalCase resource names with action verbs (e.g.
    globalAccounts/query
    ).
  • Versioning prefix — Classic uses
    /amsin/api/v1/...
    . Enhanced uses
    /api/open/v1/...
    .
Refer to the API Reference for the complete list of Enhanced Version endpoints.

Authentication

Both versions use the same authentication mechanism: key-pair-based asymmetric RSA signing.
How authentication works:
  1. Generate an RSA public/private key pair
  2. Upload your public key to the Developer Center
  3. Sign every outbound API request with your private key
  4. WorldFirst verifies the signature using your uploaded public key
Refer to the Generate Key Pair guide for step-by-step instructions.

Application lifecycle

Both versions follow the same 4-stage application lifecycle in the Developer Center:
Refer to Getting started to learn the detailed process of application.

Choosing a version

Use the Enhanced Version if:
  • You are starting a new integration
  • You want the latest API design and endpoint structure
  • You want the version that is actively developed and will receive new features
Use the Classic Version if:
  • You have an existing Classic Version integration that you are not ready to migrate
  • The Enhanced Version does not yet support a specific API your integration requires

Migration considerations

If you are on the Classic Version and considering a migration to the Enhanced Version, note the following:
  • API endpoints must be updated.
    The Enhanced Version uses completely different endpoint paths and request/response structures. You will need to update all API calls in your integration code.
  • Authentication stays the same
    Both versions use RSA key-pair signing, so your existing key management and request signing logic does not need to change.
  • Testing tools work the same way
    Mock Rules, Test Cases, and the Webhook Simulator are available in both versions.
  • Create a new application
    The API version cannot be changed on an existing application. You will need to create a new Enhanced Version application and migrate your integration to it.
  • Both versions can run in parallel
    You can run a Classic Version application alongside a new Enhanced Version application during your migration period.

For migration assistance, contact WorldFirst Technical Support.