canonical: https://jentic.com/apis/webull.com/webull

# Webull OpenAPI

Webull OpenAPI provides programmatic access to trading, account management, and market data on the Webull platform. Supports stock, options, futures, and crypto trading. Authentication uses app_key and app_secret with HMAC signing. The API exposes 13 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get account list, get account balance. Covers 13 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Get account list
- Place an order
- Cancel an order
- Replace/modify an order
- Monitor Webull OpenAPI operational status and events

## Use cases

### CRM Operations

Use the Webull OpenAPI to perform crm operations programmatically. The API provides 13 endpoints covering core functionality including get account list, get account balance, get account positions.

Example prompt: Call GET `/openapi/account/list` to get account list

### Automated Accounts Management

Automate accounts operations by combining multiple Webull OpenAPI endpoints. Agents can get account balance and then get account positions in a single workflow.

Example prompt: Call GET `/openapi/assets/balance` to get account balance, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Webull OpenAPI endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get account list', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/openapi/account/list` | Get account list |
| GET | `/openapi/assets/balance` | Get account balance |
| GET | `/openapi/assets/positions` | Get account positions |
| POST | `/openapi/trade/order/place` | Place an order |
| POST | `/openapi/trade/order/cancel` | Cancel an order |
| POST | `/openapi/trade/order/replace` | Replace/modify an order |
| GET | `/openapi/trade/order/list` | Get order list |
| GET | `/openapi/trade/order/detail` | Get order detail |

## Key resources

- **Accounts** — Operations related to Accounts
- **Market Data** — Operations related to Market Data
- **Trading** — Operations related to Trading
- **Transfers** — Operations related to Transfers

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 64 / 100
- **View full report:** https://jentic.com/apis/webull.com/webull/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Webull OpenAPI use?

The Webull OpenAPI uses an API key passed in the `app_key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get account list with the Webull OpenAPI?

Yes. Use the GET `/openapi/account/list` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Webull OpenAPI?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get account list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account list'. Jentic returns the matching Webull OpenAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Webull OpenAPI have?

The Webull OpenAPI exposes 13 endpoints covering accounts, market data, trading operations.

### Can I limit what my agent is allowed to do with the Webull OpenAPI?

Yes. Because you run Jentic One yourself, you decide which Webull operations the agent can call, so you can grant read-only access to GET `/openapi/account/list`, GET `/openapi/assets/balance`, and GET `/openapi/assets/positions` while withholding everything else. Webull carries account and order details in the request body rather than the path, so trade actions such as POST `/openapi/trade/order/place`, /cancel, and /replace stay unavailable unless you deliberately add them. Your app key and signing key are stored encrypted by your own instance and injected only for the operations you allow, so the agent never sees raw secrets or reaches endpoints outside its scope.