[Secure Transfer] How to Use the API Function

Description

This article explains the procedure for using the Secure Transfer file and log data export API feature for customers who use the API feature.

Notes

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

Procedure

Pre-checks

The Secure Transfer API endpoints are as follows.

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

{version-number} specifies the version of the API you want 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 and check the Terms of Service, then click [Create].

   

4. The API key will be added, so copy and record 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 (external link)

* When calling any API, you must always 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 display the number of seconds until you can make another request.

• Example response header
After the number of seconds indicated by reset-after has passed, please retry the API request.

retry-after: 10

• Example response body

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

Translation Disclaimer
This article has been automatically translated from the original Japanese version for your convenience.While we strive to ensure accuracy, we cannot guarantee its reliability or completeness.
In the event of any discrepancies or questions regarding the content, the official Japanese version shall prevail.