Improved

[Important] API Path Format and Error Handling Checks


Dear developers,

This is the Upbit Developer Center team.

The API Path format requirements specified in the Upbit API documentation are now in effect. Please ensure that your API requests follow the required Path format.

If you currently use error.message to identify or handle API errors, please update your implementation to use error.name instead.

To avoid disruptions to your API integration, please review your request Paths and error-handling logic and make any necessary changes.

1.Schedule

  • Effective Date: October 28, 2026 (Wednesday)
  • Applicable Regions: Singapore, Indonesia, Thailand

2.Key Details

1) API Request Path Format

API request Paths must follow the requirements below.

  • Path Start and Separators: Exactly one / at the beginning and between Path segments.
  • Path End: A trailing / is not allowed.

Valid Path

/v1/orders

Invalid Paths

//v1/orders
/v1//orders
/v1/orders//

Requests containing unnecessary slashes (/), as shown above, will result in an error.

2) API Error Handling

Since error.message may change, if you currently use it to identify or handle API errors, please use error.name instead.

{
  "error": {
    "name": "ERROR_CODE",
    "message": "ERROR_MESSAGE" → Not recommended for error handling 
  }
}

3.API Integration Checklist

Please review the following items in your current API integration.

  • Ensure there are no duplicate slashes (//) at the beginning or within the Path, and no trailing slash (/).
  • Ensure no duplicate slashes are introduced when combining BASE_URL and PATH.
  • Ensure API errors are handled based on error.name.

For example, the following configuration may result in a duplicate slash in the request URL.

ItemIncorrect (Duplicate Slash)Correct
BASE_URLhttps://sg-api.upbit.com/https://sg-api.upbit.com
PATH/v1/orders/v1/orders
Request URLhttps://sg-api.upbit.com//v1/ordershttps://sg-api.upbit.com/v1/orders

The same Path format requirements apply to the Singapore (sg), Indonesia(id), and Thailand(th) API endpoints.

4.Important Notes

  • The required API Path format is in effect across all applicable regions.
  • If you operate an API-integrated service or automated system, please review and test your request Paths and error-handling logic to prevent service disruptions.

Please ensure that your API integration follows the updated requirements and make any necessary changes.


If you have any inquiries, please contact us at [email protected].

We will respond as soon as possible.

Thank you.

Upbit Developer Center