[Bug] .assets().getV2Assets fails to parse attribute "has_options" (expects "options_enabled")

[ramonchu]

Hi 👋

When calling .assets().getV2Assets using the current alpaca-java client, the deserialization of asset attributes fails.

Problem
The enum AttributesEnum defines the value OPTIONS_ENABLED with the JSON mapping "options_enabled".
However, Alpaca’s API v2 actually returns the field as "has_options".
This mismatch causes a parsing error when retrieving assets with options enabled.

var assets = alpacaAPI.trader().assets().getV2Assets();

If the response includes "has_options": true, the client fails because "options_enabled" is expected.

Expected behavior
The client should map "has_options" correctly to the corresponding enum value.

Proposed fix
• Update AttributesEnum to use "has_options" instead of "options_enabled".
• Alternatively, support both values for backwards compatibility.

Environment
• alpaca-java: [version you’re using]
• JDK: [e.g. 17]
• OS: [e.g. MacOS 14.5]

Thanks for maintaining this library 🙏

[Petersoj]

Thanks for the report. It's been a while since I've maintained this library so your issue may very well be a bug. I'm hoping to get this library up-to-date by the end of Q1 2026 at the latest. Thanks for your patience. Apologies for the delays.