Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

# [Unreleased]

## Documentation

- **README:** Add troubleshooting entry for OpenAPI error code 202203 (`call inner interface error`). Explains that this error indicates a backend internal service failure (authentication is not the issue), the most common cause is missing OpenAPI-specific permissions (separate from mobile app permissions), and instructs users to provide the `trace_id` from the exception when contacting support.

# [4.0.6]

## Added
Expand Down
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,10 @@ https://longbridge.github.io/openapi
- Authentication errors (401/403)
- Verify `LONGBRIDGE_APP_KEY`, `LONGBRIDGE_APP_SECRET`, `LONGBRIDGE_ACCESS_TOKEN` are correct and not expired.
- Ensure your OpenAPI app has the required permissions.
- OpenAPI error code 202203 (`call inner interface error`)
- Authentication succeeded, but the backend gateway failed to reach an internal service (e.g. the asset query service).
- **Most common cause:** your OpenAPI application does not have the required permission enabled. OpenAPI permissions are managed separately from your mobile app — go to [open.longbridge.com](https://open.longbridge.com) → App Management → Permissions, and enable the permission for the API you are calling (e.g. "Account Balance").
- If permissions are already enabled, provide the `trace_id` from the exception to Longbridge support so they can trace the internal call.
- Network / connection errors
- Check firewall/proxy rules for HTTPS/WSS.
- If you use a custom endpoint, set `LONGBRIDGE_HTTP_URL`, `LONGBRIDGE_QUOTE_WS_URL`, `LONGBRIDGE_TRADE_WS_URL`.
Expand Down
Loading