See https://github.com/alpacahq/alpaca-docs/blob/master/oas/broker/openapi.yaml#L2084

SENT_TO_CLEARING is now a status that the API returns and is not in the spec.

This one has been reported in a few places now, but opening this one for public visibility into tracking it as well.

Market data docs are missing references to the Bar models' n and vw fields.

CIP endpoints are missing in Broker Openapi YAML. Please see api-reference

Clicking on "See Orders page" under order lifecycle docs responds in a 404:

https://alpaca.markets/docs/api-references/trading-api/orders/#properties

Properties
Status
See Orders page

Dead URL:
https://alpaca.markets/trading-on-alpaca/orders/#order-lifecycle

Expected one of [ONBOARDING, SUBMITTED, RESUBMITTED, SUBMISSION_FAILED, ACTION_REQUIRED, EDITED, ACCOUNT_UPDATED, APPROVAL_PENDING, REAPPROVAL_PENDING, SIGNED_UP, KYC_SUBMITTED, LIMITED, AML_REVIEW, APPROVED, REJECTED, ACTIVE, DISABLED, DISABLE_PENDING, ACCOUNT_CLOSED, PAPER_ONLY
] but was INACTIVE at path $.crypto_status

Adding INACTIVE to the yaml file fixes the issue.

In Broker API /v1/journals/{journalId} returns "status": "correct" for some journals.

How is it different from executed status?
No documentation on this

Could the data points key letter "c" not contain different values

Under Trade Schema:

c =  trade condition

Under Quote Schema:

c = quote condition

Under Minute Bar Schema:

c = close price

I feel it would be ideal to not reuse these same key names for different values.
Saves me needing to do an if statement on the T key :)

Reference: https://alpaca.markets/docs/api-references/market-data-api/stock-pricing-data/realtime/#data-points

When supplying a non existing symbol (i.e. DOES/NOTEXIST) the Latest bars endpoint returns a missing location (which is misleading):

{
  "message": "Invalid location: loc"
}

Screenshot

It looks like TradeUpdateEvent has the TransferEvent content

Following the doc on this page, v2 endpoint returns an error:

{ "message": "endpoint not found." }

But using v1, things seem ok. An update to the docs is needed

See alpacahq/alpaca-py#233 for more details. It seems the trade_confirmation_json enum value is missing from documentation. If this is the case, I can make a PR fixing this.

When I try to pass a csv to this endpoint I got a 422. I think the docs here are wrong?

HTTP/1.1 422 Unprocessable Entity returned for "https://data.alpaca.markets/v1beta1/crypto/BTCUSD/quotes/latest?exchange=FTXU,ERSX,CBSE".
[
  "code" => 42210000
  "message" => "invalid exchange: FTXU,ERSX,CBSE"
]

It looks like the version at https://github.com/alpacahq/bkdocs/blob/master/assets/openapi.yaml has been deprecated. However, it appears to have updates that are not in the version in this repo.

Could you clarify which is the source of truth?

I just tested the Historical bars endpoint from your website. It offers the possibility to set a sort parameter. When doing so, the request becomes invalid and gives the following error message:

{
  "message": "Unexpected query parameter(s): sort"
}

Screenshot

The contact on the account model in the docs has a unit field:
https://alpaca.markets/docs/api-references/broker-api/accounts/accounts/#the-account-model

The openapi spec does not:
https://github.com/alpacahq/alpaca-docs/blob/master/oas/broker/openapi.yaml#L599

I cannot find any documentation on the trade updates websocket.

Both

• https://alpaca.markets/docs/api-documentation/api-v2/streaming/
• https://alpaca.markets/docs/api-references/market-data-api/#order-updates

are AWOL.

is missing NTA events:

https://alpaca.markets/docs/api-references/broker-api/events/#non-trading-activities-events

One of the things I noticed is that the data is not in the same format as a NonTradeActivity here:

https://alpaca.markets/docs/api-references/broker-api/accounts/account-activities/#the-non-trade-activity-nta-object

For example, activity_type in NTA is entry_type in NTA events. net_amount also switches between num and string.

is missing the activity type field:

https://alpaca.markets/docs/api-references/broker-api/accounts/account-activities/#attributes-1

Can you implement an endpoint to delete orders by client_order_id?
So inconvenient.
Why do you bother with client-defined id if you don't support all endpoints for it?

Generated the code with below command and get build error

npx openapi-generator-cli generate -i broker/openapi.yaml -g csharp-netcore -o build/csharp-netcore --additional-properties aspnetCoreVersion=3.1

Severity Code Description Project File Line Suppression State
Error CS0246 The type or namespace name 'Set' could not be found (are you missing a using directive or an assembly reference?) Org.OpenAPITools C:\alpaca-docs\oas\build\csharp-netcore\src\Org.OpenAPITools\Api\DocumentsApi.cs 86 Active

I was expeting to get an API error when trying to fetch historical bars for non-existing symbols (like DOES/NOTEXIST). Instead, I get returned an empty payload which is misleading:

{
  "bars": {},
  "next_page_token": null
}

Screenshot

Pretty much every URL path parameter, such as order_id in GET /v2/orders/{order_id}, is documented as Optional. This is obviously wrong.