Webull OpenAPI

Setup

Wiring Webull OpenAPI by hand means sending both its app_key and a computed sign header on every request and handling retries yourself. Through Jentic you install once, import Webull OpenAPI from the API Directory, store the keys once, and your agent calls it.

Permission scoping

Webull carries account and order details in the request body rather than in the path, so limit the agent to the operations it needs, such as listing accounts or reading balances and positions. You choose the operations it may call, so trade actions like placing, cancelling, or replacing an order are not included unless you add them.

Credential isolation

Your Webull app key and signing key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list my accounts' or 'get my positions', and Jentic returns the matching Webull operation with its input schema so the agent calls the right endpoint without browsing the reference docs.