[Secure Transfer] How to Use the API Function

Target

• Customers using Secure Transfer

Purpose

• This article explains the procedure for using the API feature of Secure Transfer.

Notes

1. The content of this article is based on the product specifications as of June 2026 and is subject to change without notice.
2. Administrator privileges for Secure Transfer are required to use this feature.
3. The Secure Transfer API is available to customers subscribed to the HENNGE One Pro plan.
4. For information on how to access Secure Transfer, please refer to the following article.
   [Secure Transfer] Login Procedure
5. A rate limit is set for the Secure Transfer API.
   For details, please refer to About Rate Limits.
6. For details on each endpoint, please refer to the Developer Site.
   https://developers.hennge.com/

Procedure

Pre-checks

The endpoint for the Secure Transfer API is as follows.

https://api.transfer.hennge.com/{version_number}/

Replace {version-number} with the version of the API you wish to use.
For example, to use version v1 of the API, specify it as https://api.transfer.hennge.com/v1/.

Issuing an Authentication Client

1. From the Secure Transfer Administration, go to [System Settings] – [API Keys].

   

2. Click [Create API Key] at the top right of the screen.

   

3. Set the API Key name, description, and scopes, review the Terms of Service, check the box, and click [Create].

   

    

    

    

    

    

    

    

4. The API Key will be added, so copy and save it.
   * The key is only displayed at the time of issuance and cannot be displayed again after closing the dialog.
   If you close the dialog without saving the key, please delete the API Key and issue a new one.
   * The key is valid for one year from issuance.

   

Requesting Endpoints

For details on each Secure Transfer API endpoint, please refer to the Developer Site.
Secure Transfer API Quick Start

* When calling any API, you must include the API Key in the header.

About Rate Limits

A rate limit is set for the Secure Transfer API.

If you exceed the rate limit, a 429 error will be returned.
The response header will also indicate the number of seconds until you can make another request.

• Example response header
Retry the API request after the number of seconds indicated by reset-after has passed.

retry-after: 10

• Example response body

{
"error": {
"type": "too_many_requests",
"msg": "Too many requests"
}
}