@alpaca-open-api/core 0.1.0-rc.0

package/dist/generated/broker/client.d.ts

@@ -0,0 +1,3825 @@
+/**
+ * Generated by orval v8.18.0 🍺
+ * Do not edit manually.
+ * Broker API
+ * Open brokerage accounts, enable stock, options and crypto trading. Manage the ongoing user experience and brokerage customer lifecycle with the Alpaca Broker API
+ * OpenAPI spec version: 1.1.1
+ */
+import type { ACHRelationship, Account, AccountConfigurations, AccountCreationRequest, AccountDocument, AccountExtended, AccountLimit, AccountStatusEvent, AccountTradingLimit, AccountUpdateRequest, Activity, ActivityEventV2, AdminActionLegacyNote, AdminActionLiquidation, AdminActionTransactionCancel, AggregatePositionResponse, Announcement, Asset, AssetEntryRequirements, AuthorizeOAuthTokenResponse, BadRequestResponse, Bank, BatchCreateFundingWalletRequest, BatchCreateFundingWalletResponse, BatchJournalRequest, BatchJournalResponse, CIPInfo, CalendarParams, ClockParams, ClockResp, CloseAllPositionsForAccountParams, ClosePositionForAccountBySymbolParams, CorrespondentLimit, CountryInfos, CreateACHRelationshipRequest, CreateBankRequest, CreateCryptoTransferRequest, CreateFundingWalletRecipientBankBody, CreateFundingWalletWithdrawalRequest, CreateIFTransferRequest, CreateJITSettlementRequest, CreateJournalRequest, CreateOrderRequest, CreateSettlementRequest, CreateTransferRequest, CreateWatchlistRequest, CreateWhitelistedAddressBody, CryptoTransfer, CryptoWallet, DailyTradingLimit, DemoFundingTransfer, DoNotExerciseRequest, DoNotExerciseResponse, EoDCashInterestReportResponse, Error, ExerciseRequest, ExerciseResponse, FPSLAnalyticsLoansResponse, FPSLError, FPSLTier, ForbiddenResponse, FundingWallet, FundingWalletRecipientBank, FundingWalletTransfer, GetAccountACHRelationshipsParams, GetAccountActivitiesByTypeParams, GetAccountActivitiesParams, GetAllAccountsParams, GetAllJournalsParams, GetAllOrdersForAccountParams, GetAssetEntryRequirementsParams, GetAssetsParams, GetCorporateAnnouncementsParams, GetCryptoTransferEstimate200, GetCryptoTransferEstimateParams, GetDocsForAccountParams, GetOAuthClientParams, GetOptionsContracts200, GetOptionsContractsParams, GetOrderByClientOrderIdForAccountParams, GetRecipientBanksParams, GetTokenizationRequestsBrokerParams, GetTransfersForAccountParams, GetV1AccountsAccountIdOnfidoSdkTokens200, GetV1AccountsAccountIdOnfidoSdkTokensParams, GetV1AccountsPositions200, GetV1AccountsPositionsParams, GetV1EventsNtaParams, GetV1FpslAnalyticsAccountLoansParams, GetV1GetEodCashInterestReportParams, GetV1InstantFundingAccountLimitsParams, GetV1InstantFundingListParams, GetV1InstantFundingReportsParams, GetV1InstantFundingSettlementsParams, GetV1JitSettlementsParams, GetV1ListFpslLoansParams, GetV1RebalancingPortfoliosParams, GetV1RebalancingRunsParams, GetV1RebalancingSubscriptions200, GetV1RebalancingSubscriptionsParams, GetV1ReportingEodAggregatePositionsParams, GetV1ReportingEodPositions200, GetV1ReportingEodPositionsParams, GetV1TradingAccountsAccountIdAccountPortfolioHistoryParams, GetV1TradingAccountsAccountIdOrdersEstimationBody, GetV1TransfersJitLedgerIdBalances200, GetV1TransfersJitLedgerIdBalancesParams, GetV1TransfersJitReportsParams, GetV1beta1LogosSymbolParams, IPOEvent, IPOOfferingListResponse, IPOOfferingResponse, InstantFunding, IssueOAuthTokenResponse, JITLedgerAccount, JITReport, JITReportDownloadURL, Journal, JournalStatusEvent, JournalStatusEventV2, LegacyCalendarParams, LegacyClock, LegacyPublicCalendarResp, ListAPRTiersResponse, ListCryptoFundingWalletsParams, ListFPSLLoansResponse, ListFundingDetails, ListFundingDetailsParams, ListIPOOfferingsParams, ListTransfersResponse, N400Response, N401Response, N403Response, N429Response, N500Response, NonTradeActivityEvent, NotAuthorizedResponse, NotFoundResponse, OAuthTokenRequest, OathClientResponse, OptionContract, OptionsApprovalRequest, OptionsApprovalResponse, OptionsApprovalsList, Order, OrderClosedResponse, OvercontributedIRAAccount, OwnerDocumentUploadRequest, PDTRemoval, PDTStatus, PatchV1AccountsAccountIdOnfidoSdkBody, PatchV1RebalancingPortfoliosPortfolioIdBody, Portfolio, PortfolioHistory, PortfolioRun, PortfolioSubscription, Position, PositionClosedResponse, PostV1RebalancingPortfoliosBody, PostV1RebalancingRunsBody, PostV1RebalancingSubscriptionsBody, PostV1TradingAccountsAccountIdWatchlistsWatchlistIdBody, PublicCalendarResp, ReportsResponse, RequestListOptionsApprovalsParams, ReverseBatchJournalRequest, SettlementResponse, SettlementsResponse, StatusFundingEvent, SubscribeToActivitiesSSEParams, SubscribeToAdminActionSSEParams, SubscribeToFundingStatusSSEParams, SubscribeToIPOEventsSSEParams, SubscribeToJournalStatusSSEParams, SubscribeToJournalStatusV2SSEParams, SubscribeToSystemEventV2SSEParams, SubscribeToTradeSSEParams, SubscribeToTradeV2SSEParams, SubscribeToTransferStatusSSEParams, SuscribeToAccountStatusSSEParams, SystemEventV2, TokenizationMintCallback, TokenizationMintRequest, TokenizationMintResponse, TokenizationRedeemRequest, TokenizationRedeemResponse, TokenizationRequest, TradeAccount, TradeUpdateEvent, TradeUpdateEventV2, Transfer, TransferStatusEvent, UpdateOrderRequest, UsCorporatesParams, UsCorporatesResp, UsTreasuriesParams, UsTreasuriesResp, Watchlist, WatchlistWithoutAsset, WhitelistedAddress } from './model/index.js';
+export type HTTPStatusCode1xx = 100 | 101 | 102 | 103;
+export type HTTPStatusCode2xx = 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207;
+export type HTTPStatusCode3xx = 300 | 301 | 302 | 303 | 304 | 305 | 307 | 308;
+export type HTTPStatusCode4xx = 400 | 401 | 402 | 403 | 404 | 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 | 420 | 421 | 422 | 423 | 424 | 426 | 428 | 429 | 431 | 451;
+export type HTTPStatusCode5xx = 500 | 501 | 502 | 503 | 504 | 505 | 507 | 511;
+export type HTTPStatusCodes = HTTPStatusCode1xx | HTTPStatusCode2xx | HTTPStatusCode3xx | HTTPStatusCode4xx | HTTPStatusCode5xx;
+export type getFundingWalletResponse200 = {
+    data: FundingWallet;
+    status: 200;
+};
+export type getFundingWalletResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getFundingWalletResponseSuccess = (getFundingWalletResponse200) & {
+    headers: Headers;
+};
+export type getFundingWalletResponseError = (getFundingWalletResponseDefault) & {
+    headers: Headers;
+};
+export type getFundingWalletResponse = (getFundingWalletResponseSuccess | getFundingWalletResponseError);
+export declare const getGetFundingWalletUrl: (accountId: string) => string;
+/**
+ * Returns the funding wallet for the specified account. Responds with 404 if the account has not been onboarded to funding wallets or a wallet has not been created.
+ * @summary Retrieve funding wallet
+ */
+export declare const getFundingWallet: (accountId: string, options?: RequestInit) => Promise<getFundingWalletResponse>;
+export type createFundingWalletResponse200 = {
+    data: FundingWallet;
+    status: 200;
+};
+export type createFundingWalletResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type createFundingWalletResponseSuccess = (createFundingWalletResponse200) & {
+    headers: Headers;
+};
+export type createFundingWalletResponseError = (createFundingWalletResponseDefault) & {
+    headers: Headers;
+};
+export type createFundingWalletResponse = (createFundingWalletResponseSuccess | createFundingWalletResponseError);
+export declare const getCreateFundingWalletUrl: (accountId: string) => string;
+/**
+ * Creates a funding wallet for the specified account. The request is rejected if the account already has a funding wallet.
+ * @summary Creates a funding wallet
+ */
+export declare const createFundingWallet: (accountId: string, options?: RequestInit) => Promise<createFundingWalletResponse>;
+export type listFundingDetailsResponse200 = {
+    data: ListFundingDetails[];
+    status: 200;
+};
+export type listFundingDetailsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listFundingDetailsResponseSuccess = (listFundingDetailsResponse200) & {
+    headers: Headers;
+};
+export type listFundingDetailsResponseError = (listFundingDetailsResponseDefault) & {
+    headers: Headers;
+};
+export type listFundingDetailsResponse = (listFundingDetailsResponseSuccess | listFundingDetailsResponseError);
+export declare const getListFundingDetailsUrl: (accountId: string, params?: ListFundingDetailsParams) => string;
+/**
+ * Returns a list of funding details if it exists. Query parameters must be passed to create a new funding details object if none exist.
+ * @summary Retrieve funding details
+ */
+export declare const listFundingDetails: (accountId: string, params?: ListFundingDetailsParams, options?: RequestInit) => Promise<listFundingDetailsResponse>;
+export type deleteFundingWalletRecipientBankResponse200 = {
+    data: void;
+    status: 200;
+};
+export type deleteFundingWalletRecipientBankResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type deleteFundingWalletRecipientBankResponseSuccess = (deleteFundingWalletRecipientBankResponse200) & {
+    headers: Headers;
+};
+export type deleteFundingWalletRecipientBankResponseError = (deleteFundingWalletRecipientBankResponseDefault) & {
+    headers: Headers;
+};
+export type deleteFundingWalletRecipientBankResponse = (deleteFundingWalletRecipientBankResponseSuccess | deleteFundingWalletRecipientBankResponseError);
+export declare const getDeleteFundingWalletRecipientBankUrl: (accountId: string) => string;
+/**
+ * deletes a recipient bank.
+ * @summary Delete a recipient bank
+ */
+export declare const deleteFundingWalletRecipientBank: (accountId: string, options?: RequestInit) => Promise<deleteFundingWalletRecipientBankResponse>;
+export type getFundingWalletRecipientBankResponse200 = {
+    data: void;
+    status: 200;
+};
+export type getFundingWalletRecipientBankResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getFundingWalletRecipientBankResponseSuccess = (getFundingWalletRecipientBankResponse200) & {
+    headers: Headers;
+};
+export type getFundingWalletRecipientBankResponseError = (getFundingWalletRecipientBankResponseDefault) & {
+    headers: Headers;
+};
+export type getFundingWalletRecipientBankResponse = (getFundingWalletRecipientBankResponseSuccess | getFundingWalletRecipientBankResponseError);
+export declare const getGetFundingWalletRecipientBankUrl: (accountId: string) => string;
+/**
+ * Returns the recipient bank registered against the specified account's funding wallet. Responds with 404 if no recipient bank has been registered for the account.
+ * @summary Retrieve recipient bank
+ */
+export declare const getFundingWalletRecipientBank: (accountId: string, options?: RequestInit) => Promise<getFundingWalletRecipientBankResponse>;
+export type createFundingWalletRecipientBankResponse200 = {
+    data: FundingWalletRecipientBank;
+    status: 200;
+};
+export type createFundingWalletRecipientBankResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type createFundingWalletRecipientBankResponseSuccess = (createFundingWalletRecipientBankResponse200) & {
+    headers: Headers;
+};
+export type createFundingWalletRecipientBankResponseError = (createFundingWalletRecipientBankResponseDefault) & {
+    headers: Headers;
+};
+export type createFundingWalletRecipientBankResponse = (createFundingWalletRecipientBankResponseSuccess | createFundingWalletRecipientBankResponseError);
+export declare const getCreateFundingWalletRecipientBankUrl: (accountId: string) => string;
+/**
+ * Creates a new recipient bank. Returns the new recipient bank entity on success. entity.
+ * @summary Create a recipient bank
+ */
+export declare const createFundingWalletRecipientBank: (accountId: string, createFundingWalletRecipientBankBody?: CreateFundingWalletRecipientBankBody, options?: RequestInit) => Promise<createFundingWalletRecipientBankResponse>;
+export type getFundingWalletTransfersResponse200 = {
+    data: ListTransfersResponse;
+    status: 200;
+};
+export type getFundingWalletTransfersResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getFundingWalletTransfersResponseSuccess = (getFundingWalletTransfersResponse200) & {
+    headers: Headers;
+};
+export type getFundingWalletTransfersResponseError = (getFundingWalletTransfersResponseDefault) & {
+    headers: Headers;
+};
+export type getFundingWalletTransfersResponse = (getFundingWalletTransfersResponseSuccess | getFundingWalletTransfersResponseError);
+export declare const getGetFundingWalletTransfersUrl: (accountId: string) => string;
+/**
+ * Returns all funding wallet transfers (deposits and withdrawals) associated with the specified account.
+ * @summary Retrieve funding wallet transfers
+ */
+export declare const getFundingWalletTransfers: (accountId: string, options?: RequestInit) => Promise<getFundingWalletTransfersResponse>;
+export type getFundingWalletTransferByIDResponse200 = {
+    data: FundingWalletTransfer;
+    status: 200;
+};
+export type getFundingWalletTransferByIDResponse404 = {
+    data: void;
+    status: 404;
+};
+export type getFundingWalletTransferByIDResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200 | 404>;
+};
+export type getFundingWalletTransferByIDResponseSuccess = (getFundingWalletTransferByIDResponse200) & {
+    headers: Headers;
+};
+export type getFundingWalletTransferByIDResponseError = (getFundingWalletTransferByIDResponse404 | getFundingWalletTransferByIDResponseDefault) & {
+    headers: Headers;
+};
+export type getFundingWalletTransferByIDResponse = (getFundingWalletTransferByIDResponseSuccess | getFundingWalletTransferByIDResponseError);
+export declare const getGetFundingWalletTransferByIDUrl: (accountId: string, transferId: string) => string;
+/**
+ * Returns a single funding wallet transfer for the specified account by `transfer_id`. Responds with 404 if no matching transfer exists for the account.
+ * @summary Retrieve funding wallet transfer by ID
+ */
+export declare const getFundingWalletTransferByID: (accountId: string, transferId: string, options?: RequestInit) => Promise<getFundingWalletTransferByIDResponse>;
+export type createFundingWalletWithdrawalResponse200 = {
+    data: FundingWalletTransfer;
+    status: 200;
+};
+export type createFundingWalletWithdrawalResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type createFundingWalletWithdrawalResponseSuccess = (createFundingWalletWithdrawalResponse200) & {
+    headers: Headers;
+};
+export type createFundingWalletWithdrawalResponseError = (createFundingWalletWithdrawalResponseDefault) & {
+    headers: Headers;
+};
+export type createFundingWalletWithdrawalResponse = (createFundingWalletWithdrawalResponseSuccess | createFundingWalletWithdrawalResponseError);
+export declare const getCreateFundingWalletWithdrawalUrl: (accountId: string) => string;
+/**
+ * Creates a withdrawal
+ * @summary Create a withdrawal
+ */
+export declare const createFundingWalletWithdrawal: (accountId: string, createFundingWalletWithdrawalRequest: CreateFundingWalletWithdrawalRequest, options?: RequestInit) => Promise<createFundingWalletWithdrawalResponse>;
+export type batchCreateFundingWalletsResponse200 = {
+    data: BatchCreateFundingWalletResponse;
+    status: 200;
+};
+export type batchCreateFundingWalletsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type batchCreateFundingWalletsResponseSuccess = (batchCreateFundingWalletsResponse200) & {
+    headers: Headers;
+};
+export type batchCreateFundingWalletsResponseError = (batchCreateFundingWalletsResponseDefault) & {
+    headers: Headers;
+};
+export type batchCreateFundingWalletsResponse = (batchCreateFundingWalletsResponseSuccess | batchCreateFundingWalletsResponseError);
+export declare const getBatchCreateFundingWalletsUrl: () => string;
+/**
+ * Creates funding wallets for a list of accounts in a single request. Every `account_id` in the request must belong to your firm, and the request is rejected if a funding wallet already exists for any of the supplied accounts.
+ * @summary Batch create funding wallets
+ */
+export declare const batchCreateFundingWallets: (batchCreateFundingWalletRequest: BatchCreateFundingWalletRequest, options?: RequestInit) => Promise<batchCreateFundingWalletsResponse>;
+export type demoDepositFundingResponse200 = {
+    data: DemoFundingTransfer;
+    status: 200;
+};
+export type demoDepositFundingResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type demoDepositFundingResponseSuccess = (demoDepositFundingResponse200) & {
+    headers: Headers;
+};
+export type demoDepositFundingResponseError = (demoDepositFundingResponseDefault) & {
+    headers: Headers;
+};
+export type demoDepositFundingResponse = (demoDepositFundingResponseSuccess | demoDepositFundingResponseError);
+export declare const getDemoDepositFundingUrl: () => string;
+/**
+ * Simulates an inbound deposit into an account's funding wallet for end-to-end testing of the deposit flow.
+ *
+ * The transfer can only credit accounts that belong to your firm. Available in non-production (sandbox) environments only.
+ * @summary Create sandbox deposit transfer
+ */
+export declare const demoDepositFunding: (demoFundingTransfer: DemoFundingTransfer, options?: RequestInit) => Promise<demoDepositFundingResponse>;
+export type getV1beta1LogosSymbolResponse200 = {
+    data: void;
+    status: 200;
+};
+export type getV1beta1LogosSymbolResponseSuccess = (getV1beta1LogosSymbolResponse200) & {
+    headers: Headers;
+};
+export type getV1beta1LogosSymbolResponse = (getV1beta1LogosSymbolResponseSuccess);
+export declare const getGetV1beta1LogosSymbolUrl: (symbol: string, params?: GetV1beta1LogosSymbolParams) => string;
+/**
+ * Alpaca's Logo API serves uniform logo images for select stock and crypto symbols.
+ *
+ * Note: For Logo API pricing details, reach out to sales@alpaca.markets
+ *
+ * The API response will return the raw image as a binary
+ * @summary Get Logo
+ */
+export declare const getV1beta1LogosSymbol: (symbol: string, params?: GetV1beta1LogosSymbolParams, options?: RequestInit) => Promise<getV1beta1LogosSymbolResponse>;
+export type getAllAccountsResponse200 = {
+    data: AccountExtended[];
+    status: 200;
+};
+export type getAllAccountsResponseSuccess = (getAllAccountsResponse200) & {
+    headers: Headers;
+};
+export type getAllAccountsResponse = (getAllAccountsResponseSuccess);
+export declare const getGetAllAccountsUrl: (params?: GetAllAccountsParams) => string;
+/**
+ * Retrieves the first 1000 accounts that match the query parameters.
+ * Sorting is based on creation time.
+ * The created_after/created_before query parameters can be used to paginate the results.
+ * To further limit the size of the response, the entities query parameter can be used to specify which properties are included in the response.
+ * @summary Get All Accounts
+ */
+export declare const getAllAccounts: (params?: GetAllAccountsParams, options?: RequestInit) => Promise<getAllAccountsResponse>;
+export type createAccountResponse200 = {
+    data: Account;
+    status: 200;
+};
+export type createAccountResponse400 = {
+    data: string;
+    status: 400;
+};
+export type createAccountResponse409 = {
+    data: void;
+    status: 409;
+};
+export type createAccountResponse422 = {
+    data: string;
+    status: 422;
+};
+export type createAccountResponseSuccess = (createAccountResponse200) & {
+    headers: Headers;
+};
+export type createAccountResponseError = (createAccountResponse400 | createAccountResponse409 | createAccountResponse422) & {
+    headers: Headers;
+};
+export type createAccountResponse = (createAccountResponseSuccess | createAccountResponseError);
+export declare const getCreateAccountUrl: () => string;
+/**
+ * Submit an account application with KYC information. This will create a trading account for the end user. The account status may or may not be ACTIVE immediately and you will receive account status updates on the event API.
+ *
+ * **Multi-Live Accounts (MLA)**: To open an additional account for an existing account holder, supply `primary_account_holder_id` at the top level instead of `contact`/`identity` data. In that case, supplying `contact` or `identity` returns HTTP 400. Only `account_type` of `trading` and `ira` are supported via this flow.
+ * @summary Create an Account
+ */
+export declare const createAccount: (accountCreationRequest: AccountCreationRequest, options?: RequestInit) => Promise<createAccountResponse>;
+export type getAccountResponse200 = {
+    data: AccountExtended;
+    status: 200;
+};
+export type getAccountResponseSuccess = (getAccountResponse200) & {
+    headers: Headers;
+};
+export type getAccountResponse = (getAccountResponseSuccess);
+export declare const getGetAccountUrl: (accountId: string) => string;
+/**
+ * You can query a specific account that you submitted to Alpaca by passing into the query the account_id associated with the account you're retrieving.
+ * @summary Get An Account by ID
+ */
+export declare const getAccount: (accountId: string, options?: RequestInit) => Promise<getAccountResponse>;
+export type patchAccountResponse200 = {
+    data: AccountExtended;
+    status: 200;
+};
+export type patchAccountResponse400 = {
+    data: string;
+    status: 400;
+};
+export type patchAccountResponse422 = {
+    data: string;
+    status: 422;
+};
+export type patchAccountResponseSuccess = (patchAccountResponse200) & {
+    headers: Headers;
+};
+export type patchAccountResponseError = (patchAccountResponse400 | patchAccountResponse422) & {
+    headers: Headers;
+};
+export type patchAccountResponse = (patchAccountResponseSuccess | patchAccountResponseError);
+export declare const getPatchAccountUrl: (accountId: string) => string;
+/**
+ * This operation updates account information.
+ *
+ * If all parameters are valid and updates have been made, it returns with status code 200. The response is the account model.
+ *
+ * **Multi-Live Accounts (MLA)**: The `primary_account_holder_id` field is read-only after the account is created. Omitting it or supplying the value already associated with the account is a no-op; supplying a different value returns HTTP 400.
+ * @summary Update an Account
+ */
+export declare const patchAccount: (accountId: string, accountUpdateRequest: AccountUpdateRequest, options?: RequestInit) => Promise<patchAccountResponse>;
+export type getAccountACHRelationshipsResponse200 = {
+    data: ACHRelationship[];
+    status: 200;
+};
+export type getAccountACHRelationshipsResponseSuccess = (getAccountACHRelationshipsResponse200) & {
+    headers: Headers;
+};
+export type getAccountACHRelationshipsResponse = (getAccountACHRelationshipsResponseSuccess);
+export declare const getGetAccountACHRelationshipsUrl: (accountId: string, params?: GetAccountACHRelationshipsParams) => string;
+/**
+ * Returns a list of ACH Relationships for an account
+ * @summary Retrieve ACH Relationships for an account
+ */
+export declare const getAccountACHRelationships: (accountId: string, params?: GetAccountACHRelationshipsParams, options?: RequestInit) => Promise<getAccountACHRelationshipsResponse>;
+export type createACHRelationshipForAccountResponse200 = {
+    data: ACHRelationship;
+    status: 200;
+};
+export type createACHRelationshipForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type createACHRelationshipForAccountResponse401 = {
+    data: NotAuthorizedResponse;
+    status: 401;
+};
+export type createACHRelationshipForAccountResponse409 = {
+    data: Error;
+    status: 409;
+};
+export type createACHRelationshipForAccountResponseSuccess = (createACHRelationshipForAccountResponse200) & {
+    headers: Headers;
+};
+export type createACHRelationshipForAccountResponseError = (createACHRelationshipForAccountResponse400 | createACHRelationshipForAccountResponse401 | createACHRelationshipForAccountResponse409) & {
+    headers: Headers;
+};
+export type createACHRelationshipForAccountResponse = (createACHRelationshipForAccountResponseSuccess | createACHRelationshipForAccountResponseError);
+export declare const getCreateACHRelationshipForAccountUrl: (accountId: string) => string;
+/**
+ * Create a new ACHRelationship for an account
+ *
+ * If successful, will return 200 code with a newly created ACH Relationship entity.
+ * @summary Create an ACH Relationship
+ */
+export declare const createACHRelationshipForAccount: (accountId: string, createACHRelationshipRequest: CreateACHRelationshipRequest, options?: RequestInit) => Promise<createACHRelationshipForAccountResponse>;
+export type deleteACHRelationshipFromAccountResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteACHRelationshipFromAccountResponse400 = {
+    data: void;
+    status: 400;
+};
+export type deleteACHRelationshipFromAccountResponse404 = {
+    data: void;
+    status: 404;
+};
+export type deleteACHRelationshipFromAccountResponseSuccess = (deleteACHRelationshipFromAccountResponse204) & {
+    headers: Headers;
+};
+export type deleteACHRelationshipFromAccountResponseError = (deleteACHRelationshipFromAccountResponse400 | deleteACHRelationshipFromAccountResponse404) & {
+    headers: Headers;
+};
+export type deleteACHRelationshipFromAccountResponse = (deleteACHRelationshipFromAccountResponseSuccess | deleteACHRelationshipFromAccountResponseError);
+export declare const getDeleteACHRelationshipFromAccountUrl: (accountId: string, achRelationshipId: string) => string;
+/**
+ * Delete an existing ACH relationship for an account
+ * @summary Delete an existing ACH relationship
+ */
+export declare const deleteACHRelationshipFromAccount: (accountId: string, achRelationshipId: string, options?: RequestInit) => Promise<deleteACHRelationshipFromAccountResponse>;
+export type postV1AccountsAccountIdActionsCloseResponse204 = {
+    data: void;
+    status: 204;
+};
+export type postV1AccountsAccountIdActionsCloseResponse404 = {
+    data: void;
+    status: 404;
+};
+export type postV1AccountsAccountIdActionsCloseResponseSuccess = (postV1AccountsAccountIdActionsCloseResponse204) & {
+    headers: Headers;
+};
+export type postV1AccountsAccountIdActionsCloseResponseError = (postV1AccountsAccountIdActionsCloseResponse404) & {
+    headers: Headers;
+};
+export type postV1AccountsAccountIdActionsCloseResponse = (postV1AccountsAccountIdActionsCloseResponseSuccess | postV1AccountsAccountIdActionsCloseResponseError);
+export declare const getPostV1AccountsAccountIdActionsCloseUrl: (accountId: string) => string;
+/**
+ * This operation closes an active account. The underlying records and information of the account are not deleted by this operation.
+ *
+ * **Before closing an account, you are responsible for closing all the positions and withdrawing all the money associated with that account. Learn more in the Positions Documentation.**
+ * @summary Close an Account
+ */
+export declare const postV1AccountsAccountIdActionsClose: (accountId: string, options?: RequestInit) => Promise<postV1AccountsAccountIdActionsCloseResponse>;
+export type getV1AccountsAccountIdCipResponse200 = {
+    data: CIPInfo;
+    status: 200;
+};
+export type getV1AccountsAccountIdCipResponseSuccess = (getV1AccountsAccountIdCipResponse200) & {
+    headers: Headers;
+};
+export type getV1AccountsAccountIdCipResponse = (getV1AccountsAccountIdCipResponseSuccess);
+export declare const getGetV1AccountsAccountIdCipUrl: (accountId: string) => string;
+/**
+ * You can retrieve the CIP information you've submitted for a given account.
+ * @summary Retrieve CIP information
+ */
+export declare const getV1AccountsAccountIdCip: (accountId: string, options?: RequestInit) => Promise<getV1AccountsAccountIdCipResponse>;
+export type postV1AccountsAccountIdCipResponse200 = {
+    data: void;
+    status: 200;
+};
+export type postV1AccountsAccountIdCipResponseSuccess = (postV1AccountsAccountIdCipResponse200) & {
+    headers: Headers;
+};
+export type postV1AccountsAccountIdCipResponse = (postV1AccountsAccountIdCipResponseSuccess);
+export declare const getPostV1AccountsAccountIdCipUrl: (accountId: string) => string;
+/**
+ * The customer identification program (CIP) API allows you to submit the CIP results received from your KYC provider.
+ *
+ * The minimum requirements to open an individual financial account are delimited and you must verify the true identity of the account holder at account opening:
+ *
+ * Name
+ * Date of birth
+ * Address
+ * Identification number (for a U.S. citizen, a taxpayer identification number)
+ * @summary Upload CIP information
+ */
+export declare const postV1AccountsAccountIdCip: (accountId: string, cIPInfo?: CIPInfo, options?: RequestInit) => Promise<postV1AccountsAccountIdCipResponse>;
+export type getDocsForAccountResponse200 = {
+    data: AccountDocument[];
+    status: 200;
+};
+export type getDocsForAccountResponse404 = {
+    data: string;
+    status: 404;
+};
+export type getDocsForAccountResponseSuccess = (getDocsForAccountResponse200) & {
+    headers: Headers;
+};
+export type getDocsForAccountResponseError = (getDocsForAccountResponse404) & {
+    headers: Headers;
+};
+export type getDocsForAccountResponse = (getDocsForAccountResponseSuccess | getDocsForAccountResponseError);
+export declare const getGetDocsForAccountUrl: (accountId: string, params?: GetDocsForAccountParams) => string;
+/**
+ * This endpoint allows you to query all the account document based on an account ID. You can filter by date, or type of document.
+ *
+ * These account documents are tax statements, trade confirmations, etc, generated by the Alpaca system. They are distinct from the owner documents you upload and later access via the account object's documents property.
+ * @summary Retrieve a List of Account Documents
+ */
+export declare const getDocsForAccount: (accountId: string, params?: GetDocsForAccountParams, options?: RequestInit) => Promise<getDocsForAccountResponse>;
+export type downloadDocFromAccountResponse301 = {
+    data: void;
+    status: 301;
+};
+export type downloadDocFromAccountResponse404 = {
+    data: void;
+    status: 404;
+};
+export type downloadDocFromAccountResponseError = (downloadDocFromAccountResponse301 | downloadDocFromAccountResponse404) & {
+    headers: Headers;
+};
+export type downloadDocFromAccountResponse = (downloadDocFromAccountResponseError);
+export declare const getDownloadDocFromAccountUrl: (accountId: string, documentId: string) => string;
+/**
+ * This endpoint downloads an account document based on the document ID. The document will be in PDF format.
+ *
+ * The operation returns a pre-signed downloadable link as a redirect with HTTP status code 301 if one is found.
+ *
+ * You can retrieve a JSON version of a monthly statement by passing in the header accept: application/json header.
+ *
+ * These account documents are tax statements, trade confirmations, etc, generated by the Alpaca system. They are distinct from the owner documents you upload and later access via the account object's documents property.
+ * @summary Download an Account Document
+ */
+export declare const downloadDocFromAccount: (accountId: string, documentId: string, options?: RequestInit) => Promise<downloadDocFromAccountResponse>;
+export type uploadDocToAccountResponse204 = {
+    data: void;
+    status: 204;
+};
+export type uploadDocToAccountResponse400 = {
+    data: string;
+    status: 400;
+};
+export type uploadDocToAccountResponse404 = {
+    data: string;
+    status: 404;
+};
+export type uploadDocToAccountResponseSuccess = (uploadDocToAccountResponse204) & {
+    headers: Headers;
+};
+export type uploadDocToAccountResponseError = (uploadDocToAccountResponse400 | uploadDocToAccountResponse404) & {
+    headers: Headers;
+};
+export type uploadDocToAccountResponse = (uploadDocToAccountResponseSuccess | uploadDocToAccountResponseError);
+export declare const getUploadDocToAccountUrl: (accountId: string) => string;
+/**
+ * Upload documents for the primary account owner of an account.
+ *
+ * Documents are binary objects whose contents are encoded in base64. Each encoded content size is limited to 10MB if you use Alpaca for KYCaaS. If you perform your own KYC there are no document size limitations.
+ *
+ * As a convenience, documents of type w8ben may be uploaded as a JSON object using the content_data request property. The Alpaca system will then generate a formatted W-8 BEN document for subsequent downloads.
+ *
+ * Note that these owner documents are distinct from the account documents generated by Alpaca, such as tax statements and trade confirmations.
+ * @summary Upload Owner Documents for an Existing Account
+ */
+export declare const uploadDocToAccount: (accountId: string, ownerDocumentUploadRequest: OwnerDocumentUploadRequest[], options?: RequestInit) => Promise<uploadDocToAccountResponse>;
+export type getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponse301 = {
+    data: void;
+    status: 301;
+};
+export type getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponse404 = {
+    data: void;
+    status: 404;
+};
+export type getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponseError = (getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponse301 | getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponse404) & {
+    headers: Headers;
+};
+export type getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponse = (getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponseError);
+export declare const getGetV1AccountsAccountIdDocumentsW8benDocumentIdDownloadUrl: (accountId: string, documentId: string) => string;
+/**
+ * This endpoint allows you to download a W-8 BEN document for the primary owner of an account based on the document_id passed as a path parameter. The returned document is in PDF format.
+ *
+ * For certain individuals, a W-8 BEN form should be submitted at onboarding. If the individual is not a registered U.S. taxpayer (not subject to a W-9), the W-8 BEN form may need to be submitted. The IRS explains which individuals this applies to and provides instructions on completing the form. Every three years, in addition to the calendar year it was signed, a new W-8 BEN form must be submitted.
+ *
+ * The form can be submitted in JSON, JSONC, PNG, JPEG or PDF. If submitting it in JSON, please see the W-8 BEN completed with the corresponding field names for the API here.
+ *
+ * Note: The dates collected on the form are in a slightly different format than how they need to be submitted via Accounts API. It is requested by the user on the form in MM-DD-YYYY, but should be submitted as YYYY-MM-DD.
+ * @summary Download the W8BEN document for the primary owner of an account
+ */
+export declare const getV1AccountsAccountIdDocumentsW8benDocumentIdDownload: (accountId: string, documentId: string, options?: RequestInit) => Promise<getV1AccountsAccountIdDocumentsW8benDocumentIdDownloadResponse>;
+export type patchV1AccountsAccountIdOnfidoSdkResponse200 = {
+    data: void;
+    status: 200;
+};
+export type patchV1AccountsAccountIdOnfidoSdkResponse404 = {
+    data: void;
+    status: 404;
+};
+export type patchV1AccountsAccountIdOnfidoSdkResponse422 = {
+    data: void;
+    status: 422;
+};
+export type patchV1AccountsAccountIdOnfidoSdkResponseSuccess = (patchV1AccountsAccountIdOnfidoSdkResponse200) & {
+    headers: Headers;
+};
+export type patchV1AccountsAccountIdOnfidoSdkResponseError = (patchV1AccountsAccountIdOnfidoSdkResponse404 | patchV1AccountsAccountIdOnfidoSdkResponse422) & {
+    headers: Headers;
+};
+export type patchV1AccountsAccountIdOnfidoSdkResponse = (patchV1AccountsAccountIdOnfidoSdkResponseSuccess | patchV1AccountsAccountIdOnfidoSdkResponseError);
+export declare const getPatchV1AccountsAccountIdOnfidoSdkUrl: (accountId: string) => string;
+/**
+ * This request allows you to send Alpaca the result of the Onfido SDK flow in your app. A notification of a successful outcome is required for Alpaca to continue the KYC process.
+ * @summary Update the Onfido SDK Outcome
+ */
+export declare const patchV1AccountsAccountIdOnfidoSdk: (accountId: string, patchV1AccountsAccountIdOnfidoSdkBody?: PatchV1AccountsAccountIdOnfidoSdkBody, options?: RequestInit) => Promise<patchV1AccountsAccountIdOnfidoSdkResponse>;
+export type getV1AccountsAccountIdOnfidoSdkTokensResponse200 = {
+    data: GetV1AccountsAccountIdOnfidoSdkTokens200;
+    status: 200;
+};
+export type getV1AccountsAccountIdOnfidoSdkTokensResponse422 = {
+    data: void;
+    status: 422;
+};
+export type getV1AccountsAccountIdOnfidoSdkTokensResponseSuccess = (getV1AccountsAccountIdOnfidoSdkTokensResponse200) & {
+    headers: Headers;
+};
+export type getV1AccountsAccountIdOnfidoSdkTokensResponseError = (getV1AccountsAccountIdOnfidoSdkTokensResponse422) & {
+    headers: Headers;
+};
+export type getV1AccountsAccountIdOnfidoSdkTokensResponse = (getV1AccountsAccountIdOnfidoSdkTokensResponseSuccess | getV1AccountsAccountIdOnfidoSdkTokensResponseError);
+export declare const getGetV1AccountsAccountIdOnfidoSdkTokensUrl: (accountId: string, params?: GetV1AccountsAccountIdOnfidoSdkTokensParams) => string;
+/**
+ * Get an SDK token to activate the Onfido SDK flow within your app. You will have to keep track of the SDK token so you can pass it back when you upload the SDK outcome. We recommend storing the token in memory rather than persistent storage to reduce any unnecessary overhead in your app.
+ * @summary Retrieve an Onfido SDK Token
+ */
+export declare const getV1AccountsAccountIdOnfidoSdkTokens: (accountId: string, params?: GetV1AccountsAccountIdOnfidoSdkTokensParams, options?: RequestInit) => Promise<getV1AccountsAccountIdOnfidoSdkTokensResponse>;
+export type requestOptionsForAccountResponse200 = {
+    data: OptionsApprovalResponse;
+    status: 200;
+};
+export type requestOptionsForAccountResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type requestOptionsForAccountResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type requestOptionsForAccountResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type requestOptionsForAccountResponseSuccess = (requestOptionsForAccountResponse200) & {
+    headers: Headers;
+};
+export type requestOptionsForAccountResponseError = (requestOptionsForAccountResponse400 | requestOptionsForAccountResponse401 | requestOptionsForAccountResponse422) & {
+    headers: Headers;
+};
+export type requestOptionsForAccountResponse = (requestOptionsForAccountResponseSuccess | requestOptionsForAccountResponseError);
+export declare const getRequestOptionsForAccountUrl: (accountId: string) => string;
+/**
+ * This endpoint requests options trading for an account.
+ * Following submission, an assigned administrator will review the request.
+ * Upon approval, the account's options_approved_level parameter will be modified, granting the account the ability to participate in options trading.
+ * Note: This endpoint is only available for partners who have been enabled for Options BETA.
+ * @summary Request options trading for an account (BETA)
+ */
+export declare const requestOptionsForAccount: (accountId: string, optionsApprovalRequest: OptionsApprovalRequest, options?: RequestInit) => Promise<requestOptionsForAccountResponse>;
+export type getRecipientBanksResponse200 = {
+    data: Bank[];
+    status: 200;
+};
+export type getRecipientBanksResponse400 = {
+    data: void;
+    status: 400;
+};
+export type getRecipientBanksResponseSuccess = (getRecipientBanksResponse200) & {
+    headers: Headers;
+};
+export type getRecipientBanksResponseError = (getRecipientBanksResponse400) & {
+    headers: Headers;
+};
+export type getRecipientBanksResponse = (getRecipientBanksResponseSuccess | getRecipientBanksResponseError);
+export declare const getGetRecipientBanksUrl: (accountId: string, params?: GetRecipientBanksParams) => string;
+/**
+ * Retrieves Bank Relationships for an account
+ * @summary Retrieve Bank Relationships for an Account
+ */
+export declare const getRecipientBanks: (accountId: string, params?: GetRecipientBanksParams, options?: RequestInit) => Promise<getRecipientBanksResponse>;
+export type createRecipientBankResponse200 = {
+    data: Bank;
+    status: 200;
+};
+export type createRecipientBankResponse400 = {
+    data: void;
+    status: 400;
+};
+export type createRecipientBankResponse409 = {
+    data: void;
+    status: 409;
+};
+export type createRecipientBankResponseSuccess = (createRecipientBankResponse200) & {
+    headers: Headers;
+};
+export type createRecipientBankResponseError = (createRecipientBankResponse400 | createRecipientBankResponse409) & {
+    headers: Headers;
+};
+export type createRecipientBankResponse = (createRecipientBankResponseSuccess | createRecipientBankResponseError);
+export declare const getCreateRecipientBankUrl: (accountId: string) => string;
+/**
+ * If successful, retrieves Bank Relationships for an account
+ * @summary Create a Bank Relationship for an Account
+ */
+export declare const createRecipientBank: (accountId: string, createBankRequest: CreateBankRequest, options?: RequestInit) => Promise<createRecipientBankResponse>;
+export type deleteRecipientBankResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteRecipientBankResponse400 = {
+    data: void;
+    status: 400;
+};
+export type deleteRecipientBankResponse404 = {
+    data: void;
+    status: 404;
+};
+export type deleteRecipientBankResponseSuccess = (deleteRecipientBankResponse204) & {
+    headers: Headers;
+};
+export type deleteRecipientBankResponseError = (deleteRecipientBankResponse400 | deleteRecipientBankResponse404) & {
+    headers: Headers;
+};
+export type deleteRecipientBankResponse = (deleteRecipientBankResponseSuccess | deleteRecipientBankResponseError);
+export declare const getDeleteRecipientBankUrl: (accountId: string, bankId: string) => string;
+/**
+ * If successful, deletes Bank Relationship for an account
+ * @summary Delete a Bank Relationship for an Account
+ */
+export declare const deleteRecipientBank: (accountId: string, bankId: string, options?: RequestInit) => Promise<deleteRecipientBankResponse>;
+export type postTokenizationCallbackMintResponse200 = {
+    data: TokenizationRequest;
+    status: 200;
+};
+export type postTokenizationCallbackMintResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type postTokenizationCallbackMintResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type postTokenizationCallbackMintResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type postTokenizationCallbackMintResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type postTokenizationCallbackMintResponseSuccess = (postTokenizationCallbackMintResponse200) & {
+    headers: Headers;
+};
+export type postTokenizationCallbackMintResponseError = (postTokenizationCallbackMintResponse400 | postTokenizationCallbackMintResponse401 | postTokenizationCallbackMintResponse403 | postTokenizationCallbackMintResponse422) & {
+    headers: Headers;
+};
+export type postTokenizationCallbackMintResponse = (postTokenizationCallbackMintResponseSuccess | postTokenizationCallbackMintResponseError);
+export declare const getPostTokenizationCallbackMintUrl: (accountId: string) => string;
+/**
+ * This endpoint is used by the issuer to confirm the minting of tokenized assets previously requested by the Authorized Participant.
+ * @summary Confirm Tokenized Asset Minted
+ */
+export declare const postTokenizationCallbackMint: (accountId: string, tokenizationMintCallback: TokenizationMintCallback, options?: RequestInit) => Promise<postTokenizationCallbackMintResponse>;
+export type postTokenizationRedeemResponse200 = {
+    data: TokenizationRedeemResponse;
+    status: 200;
+};
+export type postTokenizationRedeemResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type postTokenizationRedeemResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type postTokenizationRedeemResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type postTokenizationRedeemResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type postTokenizationRedeemResponseSuccess = (postTokenizationRedeemResponse200) & {
+    headers: Headers;
+};
+export type postTokenizationRedeemResponseError = (postTokenizationRedeemResponse400 | postTokenizationRedeemResponse401 | postTokenizationRedeemResponse403 | postTokenizationRedeemResponse422) & {
+    headers: Headers;
+};
+export type postTokenizationRedeemResponse = (postTokenizationRedeemResponseSuccess | postTokenizationRedeemResponseError);
+export declare const getPostTokenizationRedeemUrl: (accountId: string) => string;
+/**
+ * This endpoint is used by the tokenized asset issuer to confirm the redemption of tokens previously held in the Authorized Participant's wallet. When the issuer invokes this endpoint, Alpaca will  initiate a journal of the underlying asset into the Authorized Participant's account.
+ * @summary Redeem a Tokenized Asset
+ */
+export declare const postTokenizationRedeem: (accountId: string, tokenizationRedeemRequest: TokenizationRedeemRequest, options?: RequestInit) => Promise<postTokenizationRedeemResponse>;
+export type postTokenizationMintBrokerResponse200 = {
+    data: TokenizationMintResponse;
+    status: 200;
+};
+export type postTokenizationMintBrokerResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type postTokenizationMintBrokerResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type postTokenizationMintBrokerResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type postTokenizationMintBrokerResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type postTokenizationMintBrokerResponseSuccess = (postTokenizationMintBrokerResponse200) & {
+    headers: Headers;
+};
+export type postTokenizationMintBrokerResponseError = (postTokenizationMintBrokerResponse400 | postTokenizationMintBrokerResponse401 | postTokenizationMintBrokerResponse403 | postTokenizationMintBrokerResponse422) & {
+    headers: Headers;
+};
+export type postTokenizationMintBrokerResponse = (postTokenizationMintBrokerResponseSuccess | postTokenizationMintBrokerResponseError);
+export declare const getPostTokenizationMintBrokerUrl: (accountId: string) => string;
+/**
+ * This endpoint is used by an Authorized Participant to request the minting of a tokenized asset. Alpaca will initiate a journal of the underlying asset from the Authorized Participant's account to the issuer's account.
+ * @summary Mint a Tokenized Asset
+ */
+export declare const postTokenizationMintBroker: (accountId: string, tokenizationMintRequest: TokenizationMintRequest, options?: RequestInit) => Promise<postTokenizationMintBrokerResponse>;
+export type getTokenizationRequestsBrokerResponse200 = {
+    data: TokenizationRequest[];
+    status: 200;
+};
+export type getTokenizationRequestsBrokerResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type getTokenizationRequestsBrokerResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type getTokenizationRequestsBrokerResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type getTokenizationRequestsBrokerResponseSuccess = (getTokenizationRequestsBrokerResponse200) & {
+    headers: Headers;
+};
+export type getTokenizationRequestsBrokerResponseError = (getTokenizationRequestsBrokerResponse401 | getTokenizationRequestsBrokerResponse403 | getTokenizationRequestsBrokerResponse422) & {
+    headers: Headers;
+};
+export type getTokenizationRequestsBrokerResponse = (getTokenizationRequestsBrokerResponseSuccess | getTokenizationRequestsBrokerResponseError);
+export declare const getGetTokenizationRequestsBrokerUrl: (accountId: string, params?: GetTokenizationRequestsBrokerParams) => string;
+/**
+ * Retrieve tokenization requests for the account. This endpoint may be used by the tokenized asset issuer or by an Authorized Participant (AP). The list can contain both mint and redeem requests.
+ * @summary List Tokenization Requests
+ */
+export declare const getTokenizationRequestsBroker: (accountId: string, params?: GetTokenizationRequestsBrokerParams, options?: RequestInit) => Promise<getTokenizationRequestsBrokerResponse>;
+export type getTransfersForAccountResponse200 = {
+    data: Transfer[];
+    status: 200;
+};
+export type getTransfersForAccountResponseSuccess = (getTransfersForAccountResponse200) & {
+    headers: Headers;
+};
+export type getTransfersForAccountResponse = (getTransfersForAccountResponseSuccess);
+export declare const getGetTransfersForAccountUrl: (accountId: string, params?: GetTransfersForAccountParams) => string;
+/**
+ * You can query a list of transfers for an account.
+ *
+ *
+ * You can filter requested transfers by values such as direction and status.
+ *
+ * Returns a list of transfer entities ordered by created_at
+ * @summary Retrieve List of Transfers for an Account.
+ */
+export declare const getTransfersForAccount: (accountId: string, params?: GetTransfersForAccountParams, options?: RequestInit) => Promise<getTransfersForAccountResponse>;
+export type createTransferForAccountResponse200 = {
+    data: Transfer;
+    status: 200;
+};
+export type createTransferForAccountResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type createTransferForAccountResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type createTransferForAccountResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type createTransferForAccountResponseSuccess = (createTransferForAccountResponse200) & {
+    headers: Headers;
+};
+export type createTransferForAccountResponseError = (createTransferForAccountResponse400 | createTransferForAccountResponse403 | createTransferForAccountResponse422) & {
+    headers: Headers;
+};
+export type createTransferForAccountResponse = (createTransferForAccountResponseSuccess | createTransferForAccountResponseError);
+export declare const getCreateTransferForAccountUrl: (accountId: string) => string;
+/**
+ * Create a new transfer to deposit money into or withdraw money from an account.
+ *
+ * Two `transfer_type` values are accepted, and both are available in sandbox and production:
+ *
+ * - **`ach`** — supports both `INCOMING` (deposit) and `OUTGOING` (withdrawal) directions. A `relationship_id` from a previously created [ACH Relationship](https://docs.alpaca.markets/reference/createachrelationshipforaccount) is required.
+ * - **`wire`** — supports the `OUTGOING` (withdrawal) direction only. Incoming wires cannot be initiated through this endpoint; they are pushed in by the sending bank and recorded automatically. A `bank_id` from a previously created [Bank Relationship](https://docs.alpaca.markets/reference/createrecipientbank) is required, and the bank must be in `APPROVED` status before the transfer will progress past `QUEUED`.
+ *
+ * In the sandbox environment, ACH deposits and withdrawals settle instantly against virtual funds. Outgoing wire withdrawals are accepted and simulated end-to-end — no funds are transmitted to a bank, but the transfer progresses to `COMPLETE` and the account is debited against virtual funds. Sandbox wire withdrawals are asynchronous (not instant) and auto-complete on weekdays only; transfers submitted on a weekend will not progress until Monday. For more on funding accounts in sandbox, see [this tutorial](https://alpaca.markets/learn/fund-broker-api/).
+ * @summary Request a New Transfer
+ */
+export declare const createTransferForAccount: (accountId: string, createTransferRequest: CreateTransferRequest, options?: RequestInit) => Promise<createTransferForAccountResponse>;
+export type deleteTransferResponse200 = {
+    data: void;
+    status: 200;
+};
+export type deleteTransferResponse404 = {
+    data: void;
+    status: 404;
+};
+export type deleteTransferResponseSuccess = (deleteTransferResponse200) & {
+    headers: Headers;
+};
+export type deleteTransferResponseError = (deleteTransferResponse404) & {
+    headers: Headers;
+};
+export type deleteTransferResponse = (deleteTransferResponseSuccess | deleteTransferResponseError);
+export declare const getDeleteTransferUrl: (accountId: string, transferId: string) => string;
+/**
+ * Request to close a transfer
+ * @summary Request to Close a Transfer
+ */
+export declare const deleteTransfer: (accountId: string, transferId: string, options?: RequestInit) => Promise<deleteTransferResponse>;
+export type listCryptoFundingWalletsResponse200 = {
+    data: CryptoWallet;
+    status: 200;
+};
+export type listCryptoFundingWalletsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listCryptoFundingWalletsResponseSuccess = (listCryptoFundingWalletsResponse200) & {
+    headers: Headers;
+};
+export type listCryptoFundingWalletsResponseError = (listCryptoFundingWalletsResponseDefault) & {
+    headers: Headers;
+};
+export type listCryptoFundingWalletsResponse = (listCryptoFundingWalletsResponseSuccess | listCryptoFundingWalletsResponseError);
+export declare const getListCryptoFundingWalletsUrl: (accountId: string, params?: ListCryptoFundingWalletsParams) => string;
+/**
+ * Lists wallets for the account given in the path parameter. If an asset is specified and no wallet for the account and asset pair exists one will be created. If no asset is specified only existing wallets will be listed for the account. An account may have at most one wallet per asset.
+ * @summary Retrieve Crypto Funding Wallets
+ */
+export declare const listCryptoFundingWallets: (accountId: string, params?: ListCryptoFundingWalletsParams, options?: RequestInit) => Promise<listCryptoFundingWalletsResponse>;
+export type listCryptoFundingTransfersResponse200 = {
+    data: CryptoTransfer;
+    status: 200;
+};
+export type listCryptoFundingTransfersResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listCryptoFundingTransfersResponseSuccess = (listCryptoFundingTransfersResponse200) & {
+    headers: Headers;
+};
+export type listCryptoFundingTransfersResponseError = (listCryptoFundingTransfersResponseDefault) & {
+    headers: Headers;
+};
+export type listCryptoFundingTransfersResponse = (listCryptoFundingTransfersResponseSuccess | listCryptoFundingTransfersResponseError);
+export declare const getListCryptoFundingTransfersUrl: (accountId: string) => string;
+/**
+ * Returns an array of all transfers associated with the given account across all wallets.
+ * @summary Retrieve Crypto Funding Transfers
+ */
+export declare const listCryptoFundingTransfers: (accountId: string, options?: RequestInit) => Promise<listCryptoFundingTransfersResponse>;
+export type createCryptoTransferForAccountResponse200 = {
+    data: CryptoTransfer;
+    status: 200;
+};
+export type createCryptoTransferForAccountResponseSuccess = (createCryptoTransferForAccountResponse200) & {
+    headers: Headers;
+};
+export type createCryptoTransferForAccountResponse = (createCryptoTransferForAccountResponseSuccess);
+export declare const getCreateCryptoTransferForAccountUrl: (accountId: string) => string;
+/**
+ * Creates a withdrawal request. Note that outgoing withdrawals must be sent to a whitelisted address and you must whitelist addresses at least 24 hours in advance. If you attempt to withdraw funds to a non-whitelisted address then the transfer will be rejected.
+ * @summary Request a New Withdrawal
+ */
+export declare const createCryptoTransferForAccount: (accountId: string, createCryptoTransferRequest: CreateCryptoTransferRequest, options?: RequestInit) => Promise<createCryptoTransferForAccountResponse>;
+export type getCryptoFundingTransferResponse200 = {
+    data: CryptoTransfer;
+    status: 200;
+};
+export type getCryptoFundingTransferResponseSuccess = (getCryptoFundingTransferResponse200) & {
+    headers: Headers;
+};
+export type getCryptoFundingTransferResponse = (getCryptoFundingTransferResponseSuccess);
+export declare const getGetCryptoFundingTransferUrl: (accountId: string, transferId: string) => string;
+/**
+ * Returns a specific wallet transfer by passing into the query the transfer_id.
+ * @summary Retrieve a Crypto Funding Transfer
+ */
+export declare const getCryptoFundingTransfer: (accountId: string, transferId: string, options?: RequestInit) => Promise<getCryptoFundingTransferResponse>;
+export type listWhitelistedAddressResponse200 = {
+    data: WhitelistedAddress;
+    status: 200;
+};
+export type listWhitelistedAddressResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listWhitelistedAddressResponseSuccess = (listWhitelistedAddressResponse200) & {
+    headers: Headers;
+};
+export type listWhitelistedAddressResponseError = (listWhitelistedAddressResponseDefault) & {
+    headers: Headers;
+};
+export type listWhitelistedAddressResponse = (listWhitelistedAddressResponseSuccess | listWhitelistedAddressResponseError);
+export declare const getListWhitelistedAddressUrl: (accountId: string) => string;
+/**
+ * Returns the list of whitelisted withdrawal addresses for the specified account.
+ * @summary An array of whitelisted addresses
+ */
+export declare const listWhitelistedAddress: (accountId: string, options?: RequestInit) => Promise<listWhitelistedAddressResponse>;
+export type createWhitelistedAddressResponse200 = {
+    data: WhitelistedAddress;
+    status: 200;
+};
+export type createWhitelistedAddressResponseSuccess = (createWhitelistedAddressResponse200) & {
+    headers: Headers;
+};
+export type createWhitelistedAddressResponse = (createWhitelistedAddressResponseSuccess);
+export declare const getCreateWhitelistedAddressUrl: (accountId: string) => string;
+/**
+ * Submits a new whitelisted withdrawal address for the specified account. The chain is derived from the supplied asset symbol and address, and the same address cannot be whitelisted twice on the same chain.
+ *
+ * Where travel rule reporting applies to the account, address details are validated against the travel rule provider before being persisted.
+ *
+ * Note that whitelisted addresses must wait at least 24 hours before they can be used as a withdrawal destination.
+ * @summary Request a new whitelisted address
+ */
+export declare const createWhitelistedAddress: (accountId: string, createWhitelistedAddressBody: CreateWhitelistedAddressBody, options?: RequestInit) => Promise<createWhitelistedAddressResponse>;
+export type deleteWhitelistedAddressResponse200 = {
+    data: void;
+    status: 200;
+};
+export type deleteWhitelistedAddressResponseSuccess = (deleteWhitelistedAddressResponse200) & {
+    headers: Headers;
+};
+export type deleteWhitelistedAddressResponse = (deleteWhitelistedAddressResponseSuccess);
+export declare const getDeleteWhitelistedAddressUrl: (accountId: string, whitelistedAddressId: string) => string;
+/**
+ * Deletes a whitelisted withdrawal address from the specified account by ID. Subsequent withdrawals targeting the deleted address will be rejected.
+ * @summary Delete a whitelisted address
+ */
+export declare const deleteWhitelistedAddress: (accountId: string, whitelistedAddressId: string, options?: RequestInit) => Promise<deleteWhitelistedAddressResponse>;
+export type getAccountActivitiesResponse200 = {
+    data: Activity[];
+    status: 200;
+};
+export type getAccountActivitiesResponseSuccess = (getAccountActivitiesResponse200) & {
+    headers: Headers;
+};
+export type getAccountActivitiesResponse = (getAccountActivitiesResponseSuccess);
+export declare const getGetAccountActivitiesUrl: (params?: GetAccountActivitiesParams) => string;
+/**
+ * Returns a list of activities
+ *
+ * Notes:
+ * * Pagination is handled using the `page_token` and `page_size` parameters.
+ * * `page_token` represents the ID of the last item on your current page of results.
+ *    For example, if the ID of the last activity in your first response is `20220203000000000::045b3b8d-c566-4bef-b741-2bf598dd6ae7`, you would pass that value as `page_token` to retrieve the next page of results.
+ *
+ * * If specified with a `direction` of `desc`, for example, the results will end before the activity with the specified ID.
+ * * If specified with a `direction` of `asc`, results will begin with the activity immediately after the one specified.
+ * * `page_size` is the maximum number of entries to return in the response.
+ * * If `date` is not specified, the default and maximum value is 100.
+ * * If `date` is specified, the default behavior is to return all results, and there is no maximum page size.
+ * @summary Retrieve Account Activities
+ */
+export declare const getAccountActivities: (params?: GetAccountActivitiesParams, options?: RequestInit) => Promise<getAccountActivitiesResponse>;
+export type getAccountActivitiesByTypeResponse200 = {
+    data: Activity[];
+    status: 200;
+};
+export type getAccountActivitiesByTypeResponseSuccess = (getAccountActivitiesByTypeResponse200) & {
+    headers: Headers;
+};
+export type getAccountActivitiesByTypeResponse = (getAccountActivitiesByTypeResponseSuccess);
+export declare const getGetAccountActivitiesByTypeUrl: (activityType: "FILL" | "ACATC" | "ACATS" | "CGD" | "CIL" | "CSD" | "CSW" | "DIV" | "DIVCGL" | "DIVCGS" | "DIVNRA" | "DIVROC" | "DIVTXEX" | "FEE" | "INT" | "MEM" | "JNLC" | "JNLS" | "MA" | "OPASN" | "OPCA" | "OPCSH" | "OPEXC" | "OPEXP" | "OPTRD" | "PTC" | "REORG" | "SPIN" | "SPLIT" | "FOPT", params?: GetAccountActivitiesByTypeParams) => string;
+/**
+ * Retrieves an array of Activity by type.
+ *
+ * If {activity_type} is provided as part of the URL, category cannot be provided as query parameter. They are mutually exclusive.
+ *
+ * Notes:
+ * * Pagination is handled using the `page_token` and `page_size` parameters.
+ * * `page_token` represents the ID of the end of your current page of results.
+ *   for example if in your first response the id of the last Activiy item returned in the array was `20220203000000000::045b3b8d-c566-4bef-b741-2bf598dd6ae7`, you'd pass that value as `page_token` to get the next page of results
+ *
+ * * If specified with a `direction` of `desc`, for example, the results will end before the activity with the specified ID.
+ * * If specified with a `direction` of `asc`, results will begin with the activity immediately after the one specified.
+ * * `page_size` is the maximum number of entries to return in the response.
+ * * If `date` is not specified, the default and maximum value is 100.
+ * * If `date` is specified, the default behavior is to return all results, and there is no maximum page size.
+ * @summary Retrieve Account Activities of Specific Type
+ */
+export declare const getAccountActivitiesByType: (activityType: "FILL" | "ACATC" | "ACATS" | "CGD" | "CIL" | "CSD" | "CSW" | "DIV" | "DIVCGL" | "DIVCGS" | "DIVNRA" | "DIVROC" | "DIVTXEX" | "FEE" | "INT" | "MEM" | "JNLC" | "JNLS" | "MA" | "OPASN" | "OPCA" | "OPCSH" | "OPEXC" | "OPEXP" | "OPTRD" | "PTC" | "REORG" | "SPIN" | "SPLIT" | "FOPT", params?: GetAccountActivitiesByTypeParams, options?: RequestInit) => Promise<getAccountActivitiesByTypeResponse>;
+export type listIRAExcessContritbutionsResponse200 = {
+    data: OvercontributedIRAAccount[];
+    status: 200;
+};
+export type listIRAExcessContritbutionsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type listIRAExcessContritbutionsResponseSuccess = (listIRAExcessContritbutionsResponse200) & {
+    headers: Headers;
+};
+export type listIRAExcessContritbutionsResponseError = (listIRAExcessContritbutionsResponseDefault) & {
+    headers: Headers;
+};
+export type listIRAExcessContritbutionsResponse = (listIRAExcessContritbutionsResponseSuccess | listIRAExcessContritbutionsResponseError);
+export declare const getListIRAExcessContritbutionsUrl: () => string;
+/**
+ * Returns all overcontributed IRA accounts
+ * @summary Retrieve Excess Contributions
+ */
+export declare const listIRAExcessContritbutions: (options?: RequestInit) => Promise<listIRAExcessContritbutionsResponse>;
+export type requestListOptionsApprovalsResponse200 = {
+    data: OptionsApprovalsList;
+    status: 200;
+};
+export type requestListOptionsApprovalsResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type requestListOptionsApprovalsResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type requestListOptionsApprovalsResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type requestListOptionsApprovalsResponseSuccess = (requestListOptionsApprovalsResponse200) & {
+    headers: Headers;
+};
+export type requestListOptionsApprovalsResponseError = (requestListOptionsApprovalsResponse400 | requestListOptionsApprovalsResponse401 | requestListOptionsApprovalsResponse403) & {
+    headers: Headers;
+};
+export type requestListOptionsApprovalsResponse = (requestListOptionsApprovalsResponseSuccess | requestListOptionsApprovalsResponseError);
+export declare const getRequestListOptionsApprovalsUrl: (params?: RequestListOptionsApprovalsParams) => string;
+/**
+ * This endpoint retrieves options trading level approval requests. Query parameters can be specified to filter the results. If multiple query parameters are specified, the results will be filtered to include only those that match all of the specified parameters. Each query parameter can only be specified once.
+ * @summary Retrieve options level approval requests (BETA)
+ */
+export declare const requestListOptionsApprovals: (params?: RequestListOptionsApprovalsParams, options?: RequestInit) => Promise<requestListOptionsApprovalsResponse>;
+export type getV1AccountsPositionsResponse200 = {
+    data: GetV1AccountsPositions200;
+    status: 200;
+};
+export type getV1AccountsPositionsResponseSuccess = (getV1AccountsPositionsResponse200) & {
+    headers: Headers;
+};
+export type getV1AccountsPositionsResponse = (getV1AccountsPositionsResponseSuccess);
+export declare const getGetV1AccountsPositionsUrl: (params?: GetV1AccountsPositionsParams) => string;
+/**
+ * Retrieves a list of the account's open positions.
+ * This endpoint is deprecated and will be removed in the future. Please use the [GET /v1/reporting/eod/positions endpoint](https://docs.alpaca.markets/reference/get-v1-reporting-eod-positions) instead.
+ * @deprecated
+ * @summary Bulk Fetch All Accounts Positions
+ */
+export declare const getV1AccountsPositions: (params?: GetV1AccountsPositionsParams, options?: RequestInit) => Promise<getV1AccountsPositionsResponse>;
+export type getAssetsResponse200 = {
+    data: Asset[];
+    status: 200;
+};
+export type getAssetsResponseSuccess = (getAssetsResponse200) & {
+    headers: Headers;
+};
+export type getAssetsResponse = (getAssetsResponseSuccess);
+export declare const getGetAssetsUrl: (params?: GetAssetsParams) => string;
+/**
+ * Returns all assets
+ * @summary Retrieve All Assets
+ */
+export declare const getAssets: (params?: GetAssetsParams, options?: RequestInit) => Promise<getAssetsResponse>;
+export type getAssetBySymbolOrIdResponse200 = {
+    data: Asset;
+    status: 200;
+};
+export type getAssetBySymbolOrIdResponse404 = {
+    data: void;
+    status: 404;
+};
+export type getAssetBySymbolOrIdResponseSuccess = (getAssetBySymbolOrIdResponse200) & {
+    headers: Headers;
+};
+export type getAssetBySymbolOrIdResponseError = (getAssetBySymbolOrIdResponse404) & {
+    headers: Headers;
+};
+export type getAssetBySymbolOrIdResponse = (getAssetBySymbolOrIdResponseSuccess | getAssetBySymbolOrIdResponseError);
+export declare const getGetAssetBySymbolOrIdUrl: (symbolOrAssetId: string) => string;
+/**
+ * Returns the requested asset, if found
+ * @summary Retrieve an Asset by ID
+ */
+export declare const getAssetBySymbolOrId: (symbolOrAssetId: string, options?: RequestInit) => Promise<getAssetBySymbolOrIdResponse>;
+export type getAssetEntryRequirementsResponse200 = {
+    data: AssetEntryRequirements[];
+    status: 200;
+};
+export type getAssetEntryRequirementsResponseSuccess = (getAssetEntryRequirementsResponse200) & {
+    headers: Headers;
+};
+export type getAssetEntryRequirementsResponse = (getAssetEntryRequirementsResponseSuccess);
+export declare const getGetAssetEntryRequirementsUrl: (params: GetAssetEntryRequirementsParams) => string;
+/**
+ * Returns all entry-requirements
+ * @summary Retrieve Entry Requirements for requested assets
+ */
+export declare const getAssetEntryRequirements: (params: GetAssetEntryRequirementsParams, options?: RequestInit) => Promise<getAssetEntryRequirementsResponse>;
+export type usCorporatesResponse200 = {
+    data: UsCorporatesResp;
+    status: 200;
+};
+export type usCorporatesResponse400 = {
+    data: N400Response;
+    status: 400;
+};
+export type usCorporatesResponse401 = {
+    data: N401Response;
+    status: 401;
+};
+export type usCorporatesResponse403 = {
+    data: N403Response;
+    status: 403;
+};
+export type usCorporatesResponse429 = {
+    data: N429Response;
+    status: 429;
+};
+export type usCorporatesResponse500 = {
+    data: N500Response;
+    status: 500;
+};
+export type usCorporatesResponseSuccess = (usCorporatesResponse200) & {
+    headers: Headers;
+};
+export type usCorporatesResponseError = (usCorporatesResponse400 | usCorporatesResponse401 | usCorporatesResponse403 | usCorporatesResponse429 | usCorporatesResponse500) & {
+    headers: Headers;
+};
+export type usCorporatesResponse = (usCorporatesResponseSuccess | usCorporatesResponseError);
+export declare const getUsCorporatesUrl: (params?: UsCorporatesParams) => string;
+/**
+ * Serves the list of US corporates available at Alpaca. The response is sorted by ISIN.
+ * @summary Get US corporates
+ */
+export declare const usCorporates: (params?: UsCorporatesParams, options?: RequestInit) => Promise<usCorporatesResponse>;
+export type usTreasuriesResponse200 = {
+    data: UsTreasuriesResp;
+    status: 200;
+};
+export type usTreasuriesResponse400 = {
+    data: N400Response;
+    status: 400;
+};
+export type usTreasuriesResponse403 = {
+    data: N403Response;
+    status: 403;
+};
+export type usTreasuriesResponse429 = {
+    data: N429Response;
+    status: 429;
+};
+export type usTreasuriesResponse500 = {
+    data: N500Response;
+    status: 500;
+};
+export type usTreasuriesResponseSuccess = (usTreasuriesResponse200) & {
+    headers: Headers;
+};
+export type usTreasuriesResponseError = (usTreasuriesResponse400 | usTreasuriesResponse403 | usTreasuriesResponse429 | usTreasuriesResponse500) & {
+    headers: Headers;
+};
+export type usTreasuriesResponse = (usTreasuriesResponseSuccess | usTreasuriesResponseError);
+export declare const getUsTreasuriesUrl: (params?: UsTreasuriesParams) => string;
+/**
+ * Serves the list of US treasuries available at Alpaca. The response is sorted by ISIN.
+ * @summary Get US treasuries
+ */
+export declare const usTreasuries: (params?: UsTreasuriesParams, options?: RequestInit) => Promise<usTreasuriesResponse>;
+export type legacyCalendarResponse200 = {
+    data: LegacyPublicCalendarResp;
+    status: 200;
+};
+export type legacyCalendarResponse400 = {
+    data: N400Response;
+    status: 400;
+};
+export type legacyCalendarResponse429 = {
+    data: N429Response;
+    status: 429;
+};
+export type legacyCalendarResponse500 = {
+    data: N500Response;
+    status: 500;
+};
+export type legacyCalendarResponseSuccess = (legacyCalendarResponse200) & {
+    headers: Headers;
+};
+export type legacyCalendarResponseError = (legacyCalendarResponse400 | legacyCalendarResponse429 | legacyCalendarResponse500) & {
+    headers: Headers;
+};
+export type legacyCalendarResponse = (legacyCalendarResponseSuccess | legacyCalendarResponseError);
+export declare const getLegacyCalendarUrl: (params?: LegacyCalendarParams) => string;
+/**
+ * The calendar API serves the full list of market days from 1970 to 2029. It can also be queried by specifying a start and/or end time to narrow down the results. In addition to the dates, the response also contains the specific open and close times for the market days, taking into account early closures.
+ * @summary Get US Market Calendar
+ */
+export declare const legacyCalendar: (params?: LegacyCalendarParams, options?: RequestInit) => Promise<legacyCalendarResponse>;
+export type getV1ListAprTiersResponse200 = {
+    data: ListAPRTiersResponse;
+    status: 200;
+};
+export type getV1ListAprTiersResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type getV1ListAprTiersResponse429 = {
+    data: Error;
+    status: 429;
+};
+export type getV1ListAprTiersResponse500 = {
+    data: Error;
+    status: 500;
+};
+export type getV1ListAprTiersResponseSuccess = (getV1ListAprTiersResponse200) & {
+    headers: Headers;
+};
+export type getV1ListAprTiersResponseError = (getV1ListAprTiersResponse401 | getV1ListAprTiersResponse429 | getV1ListAprTiersResponse500) & {
+    headers: Headers;
+};
+export type getV1ListAprTiersResponse = (getV1ListAprTiersResponseSuccess | getV1ListAprTiersResponseError);
+export declare const getGetV1ListAprTiersUrl: () => string;
+/**
+ * List all available APR tiers. These tiers may be assigned to an account, and will be used to determine the interest rate paid on uninvested cash balances.
+ * @summary List APR Tiers
+ */
+export declare const getV1ListAprTiers: (options?: RequestInit) => Promise<getV1ListAprTiersResponse>;
+export type legacyClockResponse200 = {
+    data: LegacyClock;
+    status: 200;
+};
+export type legacyClockResponse429 = {
+    data: N429Response;
+    status: 429;
+};
+export type legacyClockResponse500 = {
+    data: N500Response;
+    status: 500;
+};
+export type legacyClockResponseSuccess = (legacyClockResponse200) & {
+    headers: Headers;
+};
+export type legacyClockResponseError = (legacyClockResponse429 | legacyClockResponse500) & {
+    headers: Headers;
+};
+export type legacyClockResponse = (legacyClockResponseSuccess | legacyClockResponseError);
+export declare const getLegacyClockUrl: () => string;
+/**
+ * The clock API serves the current market timestamp, whether or not the market is currently open, as well as the times of the next market open and close.
+ * @summary Get US Market Clock
+ */
+export declare const legacyClock: (options?: RequestInit) => Promise<legacyClockResponse>;
+export type getCorporateAnnouncementsResponse200 = {
+    data: Announcement[];
+    status: 200;
+};
+export type getCorporateAnnouncementsResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type getCorporateAnnouncementsResponseSuccess = (getCorporateAnnouncementsResponse200) & {
+    headers: Headers;
+};
+export type getCorporateAnnouncementsResponseError = (getCorporateAnnouncementsResponse400) & {
+    headers: Headers;
+};
+export type getCorporateAnnouncementsResponse = (getCorporateAnnouncementsResponseSuccess | getCorporateAnnouncementsResponseError);
+export declare const getGetCorporateAnnouncementsUrl: (params: GetCorporateAnnouncementsParams) => string;
+/**
+ * This endpoint is deprecated, please use [the new corporate actions endpoint](https://docs.alpaca.markets/reference/corporateactions-1) instead.
+ * @deprecated
+ * @summary Retrieve Announcements
+ */
+export declare const getCorporateAnnouncements: (params: GetCorporateAnnouncementsParams, options?: RequestInit) => Promise<getCorporateAnnouncementsResponse>;
+export type getGETV1CorporateActionsAnnouncementsIdResponse200 = {
+    data: void;
+    status: 200;
+};
+export type getGETV1CorporateActionsAnnouncementsIdResponse400 = {
+    data: void;
+    status: 400;
+};
+export type getGETV1CorporateActionsAnnouncementsIdResponse422 = {
+    data: void;
+    status: 422;
+};
+export type getGETV1CorporateActionsAnnouncementsIdResponse500 = {
+    data: void;
+    status: 500;
+};
+export type getGETV1CorporateActionsAnnouncementsIdResponseSuccess = (getGETV1CorporateActionsAnnouncementsIdResponse200) & {
+    headers: Headers;
+};
+export type getGETV1CorporateActionsAnnouncementsIdResponseError = (getGETV1CorporateActionsAnnouncementsIdResponse400 | getGETV1CorporateActionsAnnouncementsIdResponse422 | getGETV1CorporateActionsAnnouncementsIdResponse500) & {
+    headers: Headers;
+};
+export type getGETV1CorporateActionsAnnouncementsIdResponse = (getGETV1CorporateActionsAnnouncementsIdResponseSuccess | getGETV1CorporateActionsAnnouncementsIdResponseError);
+export declare const getGetGETV1CorporateActionsAnnouncementsIdUrl: (id: string) => string;
+/**
+ * This endpoint is deprecated, please use [the new corporate actions endpoint](https://docs.alpaca.markets/reference/corporateactions-1) instead.
+ * @deprecated
+ * @summary Retrieve a Specific Announcement
+ */
+export declare const getGETV1CorporateActionsAnnouncementsId: (id: string, options?: RequestInit) => Promise<getGETV1CorporateActionsAnnouncementsIdResponse>;
+export type queryCountryInfosResponse200 = {
+    data: CountryInfos;
+    status: 200;
+};
+export type queryCountryInfosResponseSuccess = (queryCountryInfosResponse200) & {
+    headers: Headers;
+};
+export type queryCountryInfosResponse = (queryCountryInfosResponseSuccess);
+export declare const getQueryCountryInfosUrl: () => string;
+/**
+ * The Country Info API serves country information for every supported countries including risk ratings and supported crypto states where applicable.
+ * @summary Retrieve countries information
+ */
+export declare const queryCountryInfos: (options?: RequestInit) => Promise<queryCountryInfosResponse>;
+export type suscribeToAccountStatusSSEResponse200 = {
+    data: AccountStatusEvent[];
+    status: 200;
+};
+export type suscribeToAccountStatusSSEResponseSuccess = (suscribeToAccountStatusSSEResponse200) & {
+    headers: Headers;
+};
+export type suscribeToAccountStatusSSEResponse = (suscribeToAccountStatusSSEResponseSuccess);
+export declare const getSuscribeToAccountStatusSSEUrl: (params?: SuscribeToAccountStatusSSEParams) => string;
+/**
+ * The accounts events API provides streaming of account changes as they occur, via SSE (server sent events). Past events can also be queried.
+ *
+ * Events are generated for changes to the following account properties:
+ * - account_blocked
+ * - admin_configurations
+ * - cash_interest
+ * - crypto_status
+ * - kyc_results
+ * - options
+ * - pattern_day_trader
+ * - status
+ * - trading_blocked
+ *
+ * Only the changed properties are included in the event payload.
+ *
+ * Query Parameter Rules:
+ * - `since` is required if `until` specified
+ * - `since_id` is required if `until_id` specified
+ * - `since_ulid` is required if `until_ulid` specified
+ * - `since`, `since_id` and `since_ulid` can't be used at the same time
+ *
+ * Behavior:
+ * This API supports querying a range of events, starting now or in the past. If the end of the range is in the future or not specified, the connection is kept open and future events are pushed.
+ *
+ * To be specific:
+ * - if `since`, `since_id` or `since_ulid` is not specified, this will not return any historic data
+ * - if `until`, `until_id` or `until_ulid` is reached, the stream will end with a status of 200
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @summary Subscribe to Account Status Events (SSE)
+ */
+export declare const suscribeToAccountStatusSSE: (params?: SuscribeToAccountStatusSSEParams, options?: RequestInit) => Promise<suscribeToAccountStatusSSEResponse>;
+export type subscribeToJournalStatusSSEResponse200 = {
+    data: JournalStatusEvent[];
+    status: 200;
+};
+export type subscribeToJournalStatusSSEResponseSuccess = (subscribeToJournalStatusSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToJournalStatusSSEResponse = (subscribeToJournalStatusSSEResponseSuccess);
+export declare const getSubscribeToJournalStatusSSEUrl: (params?: SubscribeToJournalStatusSSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to journal status updates as they get processed by our backoffice.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since_ulid` required if `until_ulid` specified
+ * - `since`, `since_id` or `since_ulid`  can't be used at the same time
+ * Behavior:
+ * - if `since`, `since_id` or `since_ulid` not specified this will not return any historic data
+ * - if `until`, `until_id` or `until_ulid` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * There is no compatibility between /v1/events/journals/status and /v2/events/journals/status, the ids (ulid) are always different, and the number of events might also different
+ *
+ * Please note that the new `/v2` endpoint, is the same as, and was originally available under `/v2beta1`.
+ * We encourage all customers to adjust their codebase from that interim beta endpoint to the `/v2` stable endpoint.
+ * In the near future we will setup permanent redirect from `/v2beta1` to `/v2` before we completely remove the beta endpoint.
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @summary Subscribe to Journal Events (SSE) (Legacy)
+ */
+export declare const subscribeToJournalStatusSSE: (params?: SubscribeToJournalStatusSSEParams, options?: RequestInit) => Promise<subscribeToJournalStatusSSEResponse>;
+export type getV1EventsNtaResponse200 = {
+    data: NonTradeActivityEvent;
+    status: 200;
+};
+export type getV1EventsNtaResponseSuccess = (getV1EventsNtaResponse200) & {
+    headers: Headers;
+};
+export type getV1EventsNtaResponse = (getV1EventsNtaResponseSuccess);
+export declare const getGetV1EventsNtaUrl: (params?: GetV1EventsNtaParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to non-trading activities updates as they get processed by our backoffice, for both end-user and firm accounts.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * You can listen to when NTAs are pushed such as CSDs, JNLC (journals) or FEEs.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since_ulid` required if `until_ulid` specified
+ * - `since`, `since_id` or `since_ulid`  can't be used at the same time
+ * Behavior:
+ * - if `since`, `since_id` or `since_ulid` not specified this will not return any historic data
+ * - if `until`, `until_id` or `until_ulid` reached stream will end (status 200)'
+ * @summary Subscribe to Non-Trading Activities Events (SSE)
+ */
+export declare const getV1EventsNta: (params?: GetV1EventsNtaParams, options?: RequestInit) => Promise<getV1EventsNtaResponse>;
+export type subscribeToTradeSSEResponse200 = {
+    data: TradeUpdateEvent[];
+    status: 200;
+};
+export type subscribeToTradeSSEResponse410 = {
+    data: void;
+    status: 410;
+};
+export type subscribeToTradeSSEResponseSuccess = (subscribeToTradeSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToTradeSSEResponseError = (subscribeToTradeSSEResponse410) & {
+    headers: Headers;
+};
+export type subscribeToTradeSSEResponse = (subscribeToTradeSSEResponseSuccess | subscribeToTradeSSEResponseError);
+export declare const getSubscribeToTradeSSEUrl: (params?: SubscribeToTradeSSEParams) => string;
+/**
+ * **Deprecation notice**
+ *
+ * As part of the deprecation process, the legacy trade events API is now only available for existing broker-partners at: `GET /v1/events/trades` only for compatibility reasons.
+ *
+ * All new broker partners will not have the option for the legacy trade event endpoint.
+ *
+ * All new broker partners will have to integrate with the new `/v2/events/trades` endpoint.
+ *
+ * Also, all existing broker partners are now recommended to upgrade to the `/v2/events/trades` endpoint, which provides faster event delivery times.
+ *
+ * For trade events of MLeg (multi-leg) order, please use the `/v2/events/trades` endpoint.
+ *
+ * Please note that the new `/v2` endpoint, is the same as, and was originally available under `/v2beta1`.
+ * We encourage all customers to adjust their codebase from that interim beta endpoint to the `/v2` stable endpoint.
+ * In the near future we will setup permanent redirect from `/v2beta1` to `/v2` before we completely remove the beta endpoint.
+ *
+ * ---
+ *
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to events related to trade updates. Most market trades sent during market hours are filled instantly; you can listen to limit order updates through this endpoint.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since_ulid` required if `until_ulid` specified
+ * - `since`, `since_id` or `since_ulid`  can't be used at the same time
+ * Behavior:
+ * - if `since`, `since_id` or `since_ulid` not specified this will not return any historic data
+ * - if `until`, `until_id` or `until_ulid` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ *
+ * ---
+ *
+ * **Deprecation note**
+ *
+ * Legacy event id (integer based) is unavailable for new broker partners, and it will be deprecated for existing brokers as well.
+ * This deprecation is includes the `since_id` and `until_id` query parameter and the `event_id` field in the response.
+ *
+ * ---
+ *
+ * **Common events**
+ *
+ * These are the events that are the expected results of actions you may have taken by sending API requests.
+ *
+ * The meaning of the timestamp field changes for each type; the meanings have been specified here for which types the timestamp field will be present.
+ *
+ * - `accepted` Sent when an order is received and accepted by Alpaca
+ * - `pending_new` Sent when the order has been received by Alpaca and routed to the exchanges, but has not yet been accepted for execution.
+ * - `new` Sent when an order has been routed to exchanges for execution.
+ * - `fill` Sent when your order has been completely filled.
+ *   - timestamp: The time at which the order was filled.
+ * - `partial_fill` Sent when a number of shares less than the total remaining quantity on your order has been filled.
+ *   - timestamp: The time at which the shares were filled.
+ * - `canceled` Sent when your requested cancellation of an order is processed.
+ *   - timestamp: The time at which the order was canceled.
+ * - `expired` Sent when an order has reached the end of its lifespan, as determined by the order's time in force value.
+ *   - timestamp: The time at which the order expired.
+ * - `done_for_day` Sent when the order is done executing for the day, and will not receive further updates until the next trading day.
+ * - `replaced` Sent when your requested replacement of an order is processed.
+ *   - timestamp: The time at which the order was replaced.
+ *
+ * **Rarer events**
+ *
+ * These are events that may rarely be sent due to unexpected circumstances on the exchanges. It is unlikely you will need to design your code around them, but you may still wish to account for the possibility that they will occur.
+ *
+ * - `rejected` Sent when your order has been rejected.
+ * - `held` For multi-leg orders, the secondary orders (stop loss, take profit) will enter this state while waiting to be triggered.
+ * - `stopped` Sent when your order has been stopped, and a trade is guaranteed for the order, usually at a stated price or better, but has not yet occurred.
+ * - `pending_cancel` Sent when the order is awaiting cancellation. Most cancellations will occur without the order entering this state.
+ * - `pending_replace` Sent when the order is awaiting replacement.
+ * - `calculated` Sent when the order has been completed for the day - it is either filled or done_for_day - but remaining settlement calculations are still pending.
+ * - `suspended` Sent when the order has been suspended and is not eligible for trading.
+ * - `order_replace_rejected` Sent when the order replace has been rejected.
+ * - `order_cancel_rejected` Sent when the order cancel has been rejected.
+ * - `trade_bust`: Sent when a previously reported execution has been canceled ("busted") by the upstream exchange.
+ * - `trade_correct`: Sent when a previously reported trade has been corrected. For example, the exchange may have updated the price, quantity, or another execution parameter after the trade was initially reported.
+ * @deprecated
+ * @summary Subscribe to Trade Events (SSE) (Legacy)
+ */
+export declare const subscribeToTradeSSE: (params?: SubscribeToTradeSSEParams, options?: RequestInit) => Promise<subscribeToTradeSSEResponse>;
+export type subscribeToTransferStatusSSEResponse200 = {
+    data: TransferStatusEvent[];
+    status: 200;
+};
+export type subscribeToTransferStatusSSEResponse410 = {
+    data: void;
+    status: 410;
+};
+export type subscribeToTransferStatusSSEResponseSuccess = (subscribeToTransferStatusSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToTransferStatusSSEResponseError = (subscribeToTransferStatusSSEResponse410) & {
+    headers: Headers;
+};
+export type subscribeToTransferStatusSSEResponse = (subscribeToTransferStatusSSEResponseSuccess | subscribeToTransferStatusSSEResponseError);
+export declare const getSubscribeToTransferStatusSSEUrl: (params?: SubscribeToTransferStatusSSEParams) => string;
+/**
+ * **Deprecation notice**
+ *
+ * As part of the deprecation process, the legacy transfer events API is now only available for existing broker-partners at `GET /v1/events/transfers/status` and for compatibility reasons.
+ *
+ * All new broker partners will not have the option to use the legacy transfer events endpoint.
+ *
+ * They should integrate with the new `/v2/events/funding/status` endpoint instead.
+ *
+ * Also, all existing broker partners are now recommended to upgrade to the `/v2/events/funding/status` endpoint, which provides faster event delivery times.
+ *
+ * ---
+ *
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to transfer status updates as they get processed by our backoffice, for both end-user and firm accounts.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since_ulid` required if `until_ulid` specified
+ * - `since`, `since_id` or `since_ulid`  can't be used at the same time
+ * Behavior:
+ * - if `since`, `since_id` or `since_ulid` not specified this will not return any historic data
+ * - if `until`, `until_id` or `until_ulid` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @deprecated
+ * @summary Subscribe to Transfer Events (SSE) (Legacy)
+ */
+export declare const subscribeToTransferStatusSSE: (params?: SubscribeToTransferStatusSSEParams, options?: RequestInit) => Promise<subscribeToTransferStatusSSEResponse>;
+export type getV1FpslAnalyticsAccountLoansResponse200 = {
+    data: FPSLAnalyticsLoansResponse;
+    status: 200;
+};
+export type getV1FpslAnalyticsAccountLoansResponse400 = {
+    data: FPSLError;
+    status: 400;
+};
+export type getV1FpslAnalyticsAccountLoansResponse401 = {
+    data: FPSLError;
+    status: 401;
+};
+export type getV1FpslAnalyticsAccountLoansResponse403 = {
+    data: FPSLError;
+    status: 403;
+};
+export type getV1FpslAnalyticsAccountLoansResponse500 = {
+    data: FPSLError;
+    status: 500;
+};
+export type getV1FpslAnalyticsAccountLoansResponseSuccess = (getV1FpslAnalyticsAccountLoansResponse200) & {
+    headers: Headers;
+};
+export type getV1FpslAnalyticsAccountLoansResponseError = (getV1FpslAnalyticsAccountLoansResponse400 | getV1FpslAnalyticsAccountLoansResponse401 | getV1FpslAnalyticsAccountLoansResponse403 | getV1FpslAnalyticsAccountLoansResponse500) & {
+    headers: Headers;
+};
+export type getV1FpslAnalyticsAccountLoansResponse = (getV1FpslAnalyticsAccountLoansResponseSuccess | getV1FpslAnalyticsAccountLoansResponseError);
+export declare const getGetV1FpslAnalyticsAccountLoansUrl: (accountId: string, params?: GetV1FpslAnalyticsAccountLoansParams) => string;
+/**
+ * Returns aggregated FPSL interest and loan-activity counts for one account over a date range. Use this for "earned so far this month" customer UIs and for supervisory spot-checks against your internal accrual model.
+ *
+ * The `{account_id}` path parameter accepts a account UUID (aggregation for that account).
+ * @summary Read FPSL Loans Analytics for an Account
+ */
+export declare const getV1FpslAnalyticsAccountLoans: (accountId: string, params?: GetV1FpslAnalyticsAccountLoansParams, options?: RequestInit) => Promise<getV1FpslAnalyticsAccountLoansResponse>;
+export type getV1ListFpslLoansResponse200 = {
+    data: ListFPSLLoansResponse;
+    status: 200;
+};
+export type getV1ListFpslLoansResponse400 = {
+    data: FPSLError;
+    status: 400;
+};
+export type getV1ListFpslLoansResponse401 = {
+    data: FPSLError;
+    status: 401;
+};
+export type getV1ListFpslLoansResponse403 = {
+    data: FPSLError;
+    status: 403;
+};
+export type getV1ListFpslLoansResponse500 = {
+    data: FPSLError;
+    status: 500;
+};
+export type getV1ListFpslLoansResponseSuccess = (getV1ListFpslLoansResponse200) & {
+    headers: Headers;
+};
+export type getV1ListFpslLoansResponseError = (getV1ListFpslLoansResponse400 | getV1ListFpslLoansResponse401 | getV1ListFpslLoansResponse403 | getV1ListFpslLoansResponse500) & {
+    headers: Headers;
+};
+export type getV1ListFpslLoansResponse = (getV1ListFpslLoansResponseSuccess | getV1ListFpslLoansResponseError);
+export declare const getGetV1ListFpslLoansUrl: (params?: GetV1ListFpslLoansParams) => string;
+/**
+ * Returns a list of all FPSL loans that match the specified filter criteria, ordered in ascending order by `date`, `account_number`, and `symbol`. Each entry represents a loan of a `symbol` on a given `date`, made on behalf of the specified `account_number`.
+ * @summary List FPSL Loans
+ */
+export declare const getV1ListFpslLoans: (params?: GetV1ListFpslLoansParams, options?: RequestInit) => Promise<getV1ListFpslLoansResponse>;
+export type getV1ListFpslTiersResponse200 = {
+    data: FPSLTier[];
+    status: 200;
+};
+export type getV1ListFpslTiersResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type getV1ListFpslTiersResponse429 = {
+    data: Error;
+    status: 429;
+};
+export type getV1ListFpslTiersResponse500 = {
+    data: Error;
+    status: 500;
+};
+export type getV1ListFpslTiersResponseSuccess = (getV1ListFpslTiersResponse200) & {
+    headers: Headers;
+};
+export type getV1ListFpslTiersResponseError = (getV1ListFpslTiersResponse401 | getV1ListFpslTiersResponse429 | getV1ListFpslTiersResponse500) & {
+    headers: Headers;
+};
+export type getV1ListFpslTiersResponse = (getV1ListFpslTiersResponseSuccess | getV1ListFpslTiersResponseError);
+export declare const getGetV1ListFpslTiersUrl: () => string;
+/**
+ * List all available FPSL tiers. These tiers may be assigned to an account.
+ * @summary List FPSL Tiers
+ */
+export declare const getV1ListFpslTiers: (options?: RequestInit) => Promise<getV1ListFpslTiersResponse>;
+export type getV1InstantFundingListResponse200 = {
+    data: InstantFunding[];
+    status: 200;
+};
+export type getV1InstantFundingListResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingListResponseSuccess = (getV1InstantFundingListResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingListResponseError = (getV1InstantFundingListResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingListResponse = (getV1InstantFundingListResponseSuccess | getV1InstantFundingListResponseError);
+export declare const getGetV1InstantFundingListUrl: (params?: GetV1InstantFundingListParams) => string;
+/**
+ * Returns a list of instant funding records based on the query parameters. The results are
+ * paginated, sorted, and filtered based on the parameters provided.
+ * @summary Get Instant Funding List
+ */
+export declare const getV1InstantFundingList: (params?: GetV1InstantFundingListParams, options?: RequestInit) => Promise<getV1InstantFundingListResponse>;
+export type postV1InstantFundingResponse200 = {
+    data: InstantFunding;
+    status: 200;
+};
+export type postV1InstantFundingResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type postV1InstantFundingResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200 | 422>;
+};
+export type postV1InstantFundingResponseSuccess = (postV1InstantFundingResponse200) & {
+    headers: Headers;
+};
+export type postV1InstantFundingResponseError = (postV1InstantFundingResponse422 | postV1InstantFundingResponseDefault) & {
+    headers: Headers;
+};
+export type postV1InstantFundingResponse = (postV1InstantFundingResponseSuccess | postV1InstantFundingResponseError);
+export declare const getPostV1InstantFundingUrl: () => string;
+/**
+ * Creates an instant funding request. The request will be processed and the funds will be
+ * made available to the account in the form of a Memopost non trade activity. Upon settlement
+ * the Memoposted will be corrected to a CSD activity.
+ *
+ * **Idempotency**: When the `Idempotency-Key` header is supplied, this endpoint is
+ * idempotent. Multiple requests with the same key and identical request body will
+ * create only one transfer. A subsequent request returns the previously created
+ * transfer with the same response (no duplicate is created). If the same key is used
+ * with a different request body, the API returns `422 Unprocessable Entity`.
+ *
+ * **Recommended for production**: Always supply `Idempotency-Key` when creating
+ * transfers. This allows safe retries on timeouts, network errors, or 5xx responses
+ * without risking duplicate transfers. Use a client-generated unique value (e.g. UUID).
+ * @summary Create an instant funding request
+ */
+export declare const postV1InstantFunding: (createIFTransferRequest: CreateIFTransferRequest, options?: RequestInit) => Promise<postV1InstantFundingResponse>;
+export type deleteV1InstantFundingSingleResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteV1InstantFundingSingleResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 204>;
+};
+export type deleteV1InstantFundingSingleResponseSuccess = (deleteV1InstantFundingSingleResponse204) & {
+    headers: Headers;
+};
+export type deleteV1InstantFundingSingleResponseError = (deleteV1InstantFundingSingleResponseDefault) & {
+    headers: Headers;
+};
+export type deleteV1InstantFundingSingleResponse = (deleteV1InstantFundingSingleResponseSuccess | deleteV1InstantFundingSingleResponseError);
+export declare const getDeleteV1InstantFundingSingleUrl: (instantFundingId: string) => string;
+/**
+ * Cancels a single instant funding request based on the ID supplied if possible.
+ * @summary Cancel an instant funding request
+ */
+export declare const deleteV1InstantFundingSingle: (instantFundingId: string, options?: RequestInit) => Promise<deleteV1InstantFundingSingleResponse>;
+export type getV1InstantFundingSingleResponse200 = {
+    data: InstantFunding;
+    status: 200;
+};
+export type getV1InstantFundingSingleResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingSingleResponseSuccess = (getV1InstantFundingSingleResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingSingleResponseError = (getV1InstantFundingSingleResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingSingleResponse = (getV1InstantFundingSingleResponseSuccess | getV1InstantFundingSingleResponseError);
+export declare const getGetV1InstantFundingSingleUrl: (instantFundingId: string) => string;
+/**
+ * Returns an instant funding transfer based on the ID supplied.
+ * @summary Get an instant funding request
+ */
+export declare const getV1InstantFundingSingle: (instantFundingId: string, options?: RequestInit) => Promise<getV1InstantFundingSingleResponse>;
+export type getV1InstantFundingCorrespondentLimitsResponse200 = {
+    data: CorrespondentLimit;
+    status: 200;
+};
+export type getV1InstantFundingCorrespondentLimitsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingCorrespondentLimitsResponseSuccess = (getV1InstantFundingCorrespondentLimitsResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingCorrespondentLimitsResponseError = (getV1InstantFundingCorrespondentLimitsResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingCorrespondentLimitsResponse = (getV1InstantFundingCorrespondentLimitsResponseSuccess | getV1InstantFundingCorrespondentLimitsResponseError);
+export declare const getGetV1InstantFundingCorrespondentLimitsUrl: () => string;
+/**
+ * Returns globally configured limits for the correspondent. These limits are used to determine
+ * the maximum amount that can be extended to all accounts, and reaching this limit will result
+ * in further requests to create instant funding requests being rejected.
+ * @summary Get instant funding limits
+ */
+export declare const getV1InstantFundingCorrespondentLimits: (options?: RequestInit) => Promise<getV1InstantFundingCorrespondentLimitsResponse>;
+export type getV1InstantFundingAccountLimitsResponse200 = {
+    data: AccountLimit[];
+    status: 200;
+};
+export type getV1InstantFundingAccountLimitsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingAccountLimitsResponseSuccess = (getV1InstantFundingAccountLimitsResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingAccountLimitsResponseError = (getV1InstantFundingAccountLimitsResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingAccountLimitsResponse = (getV1InstantFundingAccountLimitsResponseSuccess | getV1InstantFundingAccountLimitsResponseError);
+export declare const getGetV1InstantFundingAccountLimitsUrl: (params: GetV1InstantFundingAccountLimitsParams) => string;
+/**
+ * Returns the limits for individual partner accounts.
+ * @summary Get instant funding account limits
+ */
+export declare const getV1InstantFundingAccountLimits: (params: GetV1InstantFundingAccountLimitsParams, options?: RequestInit) => Promise<getV1InstantFundingAccountLimitsResponse>;
+export type getV1InstantFundingReportsResponse200 = {
+    data: ReportsResponse[];
+    status: 200;
+};
+export type getV1InstantFundingReportsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingReportsResponseSuccess = (getV1InstantFundingReportsResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingReportsResponseError = (getV1InstantFundingReportsResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingReportsResponse = (getV1InstantFundingReportsResponseSuccess | getV1InstantFundingReportsResponseError);
+export declare const getGetV1InstantFundingReportsUrl: (params?: GetV1InstantFundingReportsParams) => string;
+/**
+ * Returns instant funding reports which are to be used for daily reconciliation reporting.
+ * @summary Get instant funding report
+ */
+export declare const getV1InstantFundingReports: (params?: GetV1InstantFundingReportsParams, options?: RequestInit) => Promise<getV1InstantFundingReportsResponse>;
+export type getV1InstantFundingSettlementsResponse200 = {
+    data: SettlementsResponse;
+    status: 200;
+};
+export type getV1InstantFundingSettlementsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingSettlementsResponseSuccess = (getV1InstantFundingSettlementsResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingSettlementsResponseError = (getV1InstantFundingSettlementsResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingSettlementsResponse = (getV1InstantFundingSettlementsResponseSuccess | getV1InstantFundingSettlementsResponseError);
+export declare const getGetV1InstantFundingSettlementsUrl: (params?: GetV1InstantFundingSettlementsParams) => string;
+/**
+ * Returns all settlements filtered by status if provided.
+ * @summary List settlements
+ */
+export declare const getV1InstantFundingSettlements: (params?: GetV1InstantFundingSettlementsParams, options?: RequestInit) => Promise<getV1InstantFundingSettlementsResponse>;
+export type postV1InstantFundingSettlementsResponse200 = {
+    data: SettlementResponse;
+    status: 200;
+};
+export type postV1InstantFundingSettlementsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type postV1InstantFundingSettlementsResponseSuccess = (postV1InstantFundingSettlementsResponse200) & {
+    headers: Headers;
+};
+export type postV1InstantFundingSettlementsResponseError = (postV1InstantFundingSettlementsResponseDefault) & {
+    headers: Headers;
+};
+export type postV1InstantFundingSettlementsResponse = (postV1InstantFundingSettlementsResponseSuccess | postV1InstantFundingSettlementsResponseError);
+export declare const getPostV1InstantFundingSettlementsUrl: () => string;
+/**
+ * Creates a new settlement, which will trigger the reconciliation process for all included
+ * transfers and their interests. There is a limit of 50,000 transfers per settlement. If more
+ * than 50,000 transfers need to be settled, they should be batched in multiple settlements.
+ * @summary Create a new settlement
+ */
+export declare const postV1InstantFundingSettlements: (createSettlementRequest: CreateSettlementRequest, options?: RequestInit) => Promise<postV1InstantFundingSettlementsResponse>;
+export type getV1InstantFundingSettlementsSingleResponse200 = {
+    data: SettlementResponse;
+    status: 200;
+};
+export type getV1InstantFundingSettlementsSingleResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1InstantFundingSettlementsSingleResponseSuccess = (getV1InstantFundingSettlementsSingleResponse200) & {
+    headers: Headers;
+};
+export type getV1InstantFundingSettlementsSingleResponseError = (getV1InstantFundingSettlementsSingleResponseDefault) & {
+    headers: Headers;
+};
+export type getV1InstantFundingSettlementsSingleResponse = (getV1InstantFundingSettlementsSingleResponseSuccess | getV1InstantFundingSettlementsSingleResponseError);
+export declare const getGetV1InstantFundingSettlementsSingleUrl: (settlementId: string) => string;
+/**
+ * Returns the settlement specified by the path parameter.
+ * @summary Get a single settlement
+ */
+export declare const getV1InstantFundingSettlementsSingle: (settlementId: string, options?: RequestInit) => Promise<getV1InstantFundingSettlementsSingleResponse>;
+export type listIPOOfferingsResponse200 = {
+    data: IPOOfferingListResponse;
+    status: 200;
+};
+export type listIPOOfferingsResponseSuccess = (listIPOOfferingsResponse200) & {
+    headers: Headers;
+};
+export type listIPOOfferingsResponse = (listIPOOfferingsResponseSuccess);
+export declare const getListIPOOfferingsUrl: (params?: ListIPOOfferingsParams) => string;
+/**
+ * Returns a paginated list of IPO offerings currently known to Alpaca.
+ *
+ * Use this endpoint to power IPO discovery surfaces (e.g. an "Upcoming IPOs" list). Real-time lifecycle changes (availability, prospectus, 60-minute mail, allocations, cancellations) are pushed over the [IPO Events Stream](#operation/subscribeToIPOEventsSSE).
+ * @summary List IPO Offerings
+ */
+export declare const listIPOOfferings: (params?: ListIPOOfferingsParams, options?: RequestInit) => Promise<listIPOOfferingsResponse>;
+export type getIPOOfferingResponse200 = {
+    data: IPOOfferingResponse;
+    status: 200;
+};
+export type getIPOOfferingResponse404 = {
+    data: void;
+    status: 404;
+};
+export type getIPOOfferingResponseSuccess = (getIPOOfferingResponse200) & {
+    headers: Headers;
+};
+export type getIPOOfferingResponseError = (getIPOOfferingResponse404) & {
+    headers: Headers;
+};
+export type getIPOOfferingResponse = (getIPOOfferingResponseSuccess | getIPOOfferingResponseError);
+export declare const getGetIPOOfferingUrl: (offeringReference: string) => string;
+/**
+ * Returns a single IPO offering by `offering_reference`.
+ *
+ * The `offering_reference` value matches the one delivered on the [IPO Events Stream](#operation/subscribeToIPOEventsSSE).
+ * @summary Retrieve an IPO Offering
+ */
+export declare const getIPOOffering: (offeringReference: string, options?: RequestInit) => Promise<getIPOOfferingResponse>;
+export type getV1JitSettlementsResponse200 = {
+    data: SettlementsResponse;
+    status: 200;
+};
+export type getV1JitSettlementsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1JitSettlementsResponseSuccess = (getV1JitSettlementsResponse200) & {
+    headers: Headers;
+};
+export type getV1JitSettlementsResponseError = (getV1JitSettlementsResponseDefault) & {
+    headers: Headers;
+};
+export type getV1JitSettlementsResponse = (getV1JitSettlementsResponseSuccess | getV1JitSettlementsResponseError);
+export declare const getGetV1JitSettlementsUrl: (params?: GetV1JitSettlementsParams) => string;
+/**
+ * Returns all JIT settlements filtered by status if provided.
+ * @summary List all JIT Settlements
+ */
+export declare const getV1JitSettlements: (params?: GetV1JitSettlementsParams, options?: RequestInit) => Promise<getV1JitSettlementsResponse>;
+export type postV1JitSettlementsResponse200 = {
+    data: SettlementResponse;
+    status: 200;
+};
+export type postV1JitSettlementsResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type postV1JitSettlementsResponseSuccess = (postV1JitSettlementsResponse200) & {
+    headers: Headers;
+};
+export type postV1JitSettlementsResponseError = (postV1JitSettlementsResponseDefault) & {
+    headers: Headers;
+};
+export type postV1JitSettlementsResponse = (postV1JitSettlementsResponseSuccess | postV1JitSettlementsResponseError);
+export declare const getPostV1JitSettlementsUrl: () => string;
+/**
+ * Creates a new JIT settlement, which will trigger the reconciliation process for all included accounts.
+ * @summary Create a new JIT settlement
+ */
+export declare const postV1JitSettlements: (createJITSettlementRequest: CreateJITSettlementRequest, options?: RequestInit) => Promise<postV1JitSettlementsResponse>;
+export type getV1JitSettlementsSingleResponse200 = {
+    data: SettlementResponse;
+    status: 200;
+};
+export type getV1JitSettlementsSingleResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getV1JitSettlementsSingleResponseSuccess = (getV1JitSettlementsSingleResponse200) & {
+    headers: Headers;
+};
+export type getV1JitSettlementsSingleResponseError = (getV1JitSettlementsSingleResponseDefault) & {
+    headers: Headers;
+};
+export type getV1JitSettlementsSingleResponse = (getV1JitSettlementsSingleResponseSuccess | getV1JitSettlementsSingleResponseError);
+export declare const getGetV1JitSettlementsSingleUrl: (settlementId: string) => string;
+/**
+ * Returns the JIT settlement specified by the path parameter.
+ * @summary Get a single JIT settlement
+ */
+export declare const getV1JitSettlementsSingle: (settlementId: string, options?: RequestInit) => Promise<getV1JitSettlementsSingleResponse>;
+export type getAllJournalsResponse200 = {
+    data: Journal[];
+    status: 200;
+};
+export type getAllJournalsResponse400 = {
+    data: string;
+    status: 400;
+};
+export type getAllJournalsResponse422 = {
+    data: string;
+    status: 422;
+};
+export type getAllJournalsResponseSuccess = (getAllJournalsResponse200) & {
+    headers: Headers;
+};
+export type getAllJournalsResponseError = (getAllJournalsResponse400 | getAllJournalsResponse422) & {
+    headers: Headers;
+};
+export type getAllJournalsResponse = (getAllJournalsResponseSuccess | getAllJournalsResponseError);
+export declare const getGetAllJournalsUrl: (params?: GetAllJournalsParams) => string;
+/**
+ * Returns an array of journal objects.
+ * @summary Retrieve a List Journals
+ */
+export declare const getAllJournals: (params?: GetAllJournalsParams, options?: RequestInit) => Promise<getAllJournalsResponse>;
+export type createJournalResponse200 = {
+    data: Journal;
+    status: 200;
+};
+export type createJournalResponse400 = {
+    data: string;
+    status: 400;
+};
+export type createJournalResponse403 = {
+    data: string;
+    status: 403;
+};
+export type createJournalResponse404 = {
+    data: string;
+    status: 404;
+};
+export type createJournalResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type createJournalResponseSuccess = (createJournalResponse200) & {
+    headers: Headers;
+};
+export type createJournalResponseError = (createJournalResponse400 | createJournalResponse403 | createJournalResponse404 | createJournalResponse422) & {
+    headers: Headers;
+};
+export type createJournalResponse = (createJournalResponseSuccess | createJournalResponseError);
+export declare const getCreateJournalUrl: () => string;
+/**
+ * A journal can be JNLC (move cash) or JNLS (move shares), dictated by `entry_type`. Generally, journal requests are subject to approval and starts from the `pending` status. The status changes are propagated through the Event API. Under certain conditions agreed for the partner, such journal transactions that meet the criteria are executed right away.
+ *
+ * **Idempotency**: When the `Idempotency-Key` header is supplied, this endpoint is
+ * idempotent. Multiple requests with the same key and identical request body will
+ * create only one journal. A subsequent request returns the previously created
+ * journal with the same response (no duplicate is created). If the same key is used
+ * with a different request body, the API returns `422 Unprocessable Entity`.
+ *
+ * **Recommended for production**: Always supply `Idempotency-Key` when creating
+ * journals. This allows safe retries on timeouts, network errors, or 5xx responses
+ * without risking duplicate journals. Use a client-generated unique value (e.g. UUID).
+ * @summary Create a Journal
+ */
+export declare const createJournal: (createJournalRequest: CreateJournalRequest, options?: RequestInit) => Promise<createJournalResponse>;
+export type deleteJournalByIdResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteJournalByIdResponse404 = {
+    data: void;
+    status: 404;
+};
+export type deleteJournalByIdResponse422 = {
+    data: void;
+    status: 422;
+};
+export type deleteJournalByIdResponseSuccess = (deleteJournalByIdResponse204) & {
+    headers: Headers;
+};
+export type deleteJournalByIdResponseError = (deleteJournalByIdResponse404 | deleteJournalByIdResponse422) & {
+    headers: Headers;
+};
+export type deleteJournalByIdResponse = (deleteJournalByIdResponseSuccess | deleteJournalByIdResponseError);
+export declare const getDeleteJournalByIdUrl: (journalId: string) => string;
+/**
+ * You can only delete a journal if the journal is still in a pending state, if a journal is executed you will not be able to delete. The alternative is to create a mirror journal entry to reverse the flow of funds.
+ * @summary Cancel a Pending Journal
+ */
+export declare const deleteJournalById: (journalId: string, options?: RequestInit) => Promise<deleteJournalByIdResponse>;
+export type getV1JournalsJournalIdResponse200 = {
+    data: Journal;
+    status: 200;
+};
+export type getV1JournalsJournalIdResponseSuccess = (getV1JournalsJournalIdResponse200) & {
+    headers: Headers;
+};
+export type getV1JournalsJournalIdResponse = (getV1JournalsJournalIdResponseSuccess);
+export declare const getGetV1JournalsJournalIdUrl: (journalId: string) => string;
+/**
+ * You can query a specific journal entry that you submitted to Alpaca by passing into the query the journal_id.
+ *
+ * Will return a journal entry if a journal entry with journal_id exists, otherwise will throw an error.
+ * @summary Retrieve a Single Journal Entry
+ */
+export declare const getV1JournalsJournalId: (journalId: string, options?: RequestInit) => Promise<getV1JournalsJournalIdResponse>;
+export type createBatchJournalResponse200 = {
+    data: BatchJournalResponse[];
+    status: 200;
+};
+export type createBatchJournalResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type createBatchJournalResponseSuccess = (createBatchJournalResponse200) & {
+    headers: Headers;
+};
+export type createBatchJournalResponseError = (createBatchJournalResponse422) & {
+    headers: Headers;
+};
+export type createBatchJournalResponse = (createBatchJournalResponseSuccess | createBatchJournalResponseError);
+export declare const getCreateBatchJournalUrl: () => string;
+/**
+ * You can create a batch of journal requests by using this endpoint. This is enabled on JNLC type Journals for now only.
+ *
+ * Every single request must be valid for the entire batch operation to succeed.
+ *
+ * In the case of a successful request, the response will contain an array of journal objects with an extra attribute error_message in the case when a specific account fails to receive a journal.
+ *
+ * **Idempotency**: When the `Idempotency-Key` header is supplied, this endpoint is
+ * idempotent. Multiple requests with the same key and identical request body will
+ * create only one batch. A subsequent request returns the previously created
+ * batch with the same response (no duplicate is created). If the same key is used
+ * with a different request body, the API returns `422 Unprocessable Entity`.
+ *
+ * **Recommended for production**: Always supply `Idempotency-Key` when creating
+ * journal batches. This allows safe retries on timeouts, network errors, or 5xx responses
+ * without risking duplicate batches. Use a client-generated unique value (e.g. UUID).
+ * @summary Create a Batch Journal Transaction (One-to-Many)
+ */
+export declare const createBatchJournal: (batchJournalRequest: BatchJournalRequest, options?: RequestInit) => Promise<createBatchJournalResponse>;
+export type postV1JournalsReverseBatchResponse200 = {
+    data: BatchJournalResponse[];
+    status: 200;
+};
+export type postV1JournalsReverseBatchResponse400 = {
+    data: void;
+    status: 400;
+};
+export type postV1JournalsReverseBatchResponse403 = {
+    data: void;
+    status: 403;
+};
+export type postV1JournalsReverseBatchResponse404 = {
+    data: void;
+    status: 404;
+};
+export type postV1JournalsReverseBatchResponseSuccess = (postV1JournalsReverseBatchResponse200) & {
+    headers: Headers;
+};
+export type postV1JournalsReverseBatchResponseError = (postV1JournalsReverseBatchResponse400 | postV1JournalsReverseBatchResponse403 | postV1JournalsReverseBatchResponse404) & {
+    headers: Headers;
+};
+export type postV1JournalsReverseBatchResponse = (postV1JournalsReverseBatchResponseSuccess | postV1JournalsReverseBatchResponseError);
+export declare const getPostV1JournalsReverseBatchUrl: () => string;
+/**
+ * You can also create a batch journal request by using the following endpoint. This is enabled on JNLC for now only.
+ *
+ * Note that if there is an invalid account_id the whole batch operation will be canceled.
+ * Every single request must be valid for the entire batch operation to succeed.
+ *
+ * In the case of a successful request, the response will contain an array of journal objects with an extra attribute error_message in the case when a specific account fails to submit a journal.
+ * @summary Create a Reverse Batch Journal Transaction (Many-to-One)
+ */
+export declare const postV1JournalsReverseBatch: (reverseBatchJournalRequest?: ReverseBatchJournalRequest, options?: RequestInit) => Promise<postV1JournalsReverseBatchResponse>;
+export type authorizeOAuthTokenResponse200 = {
+    data: AuthorizeOAuthTokenResponse;
+    status: 200;
+};
+export type authorizeOAuthTokenResponse401 = {
+    data: string;
+    status: 401;
+};
+export type authorizeOAuthTokenResponse422 = {
+    data: string;
+    status: 422;
+};
+export type authorizeOAuthTokenResponseSuccess = (authorizeOAuthTokenResponse200) & {
+    headers: Headers;
+};
+export type authorizeOAuthTokenResponseError = (authorizeOAuthTokenResponse401 | authorizeOAuthTokenResponse422) & {
+    headers: Headers;
+};
+export type authorizeOAuthTokenResponse = (authorizeOAuthTokenResponseSuccess | authorizeOAuthTokenResponseError);
+export declare const getAuthorizeOAuthTokenUrl: () => string;
+/**
+ * The operation issues an OAuth code which can be used in the OAuth code flow.
+ * @summary Authorize an OAuth Token
+ */
+export declare const authorizeOAuthToken: (oAuthTokenRequest: OAuthTokenRequest, options?: RequestInit) => Promise<authorizeOAuthTokenResponse>;
+export type getOAuthClientResponse200 = {
+    data: OathClientResponse;
+    status: 200;
+};
+export type getOAuthClientResponse401 = {
+    data: string;
+    status: 401;
+};
+export type getOAuthClientResponseSuccess = (getOAuthClientResponse200) & {
+    headers: Headers;
+};
+export type getOAuthClientResponseError = (getOAuthClientResponse401) & {
+    headers: Headers;
+};
+export type getOAuthClientResponse = (getOAuthClientResponseSuccess | getOAuthClientResponseError);
+export declare const getGetOAuthClientUrl: (clientId: string, params?: GetOAuthClientParams) => string;
+/**
+ * The endpoint returns the details of OAuth client to display in the authorization page.
+ * @summary Get an OAuth client
+ */
+export declare const getOAuthClient: (clientId: string, params?: GetOAuthClientParams, options?: RequestInit) => Promise<getOAuthClientResponse>;
+export type issueOAuthTokenResponse200 = {
+    data: IssueOAuthTokenResponse;
+    status: 200;
+};
+export type issueOAuthTokenResponse401 = {
+    data: string;
+    status: 401;
+};
+export type issueOAuthTokenResponse422 = {
+    data: string;
+    status: 422;
+};
+export type issueOAuthTokenResponseSuccess = (issueOAuthTokenResponse200) & {
+    headers: Headers;
+};
+export type issueOAuthTokenResponseError = (issueOAuthTokenResponse401 | issueOAuthTokenResponse422) & {
+    headers: Headers;
+};
+export type issueOAuthTokenResponse = (issueOAuthTokenResponseSuccess | issueOAuthTokenResponseError);
+export declare const getIssueOAuthTokenUrl: () => string;
+/**
+ * The operation issues an OAuth code which can be used in the OAuth code flow.
+ * @summary Issue an OAuth token
+ */
+export declare const issueOAuthToken: (oAuthTokenRequest: OAuthTokenRequest, options?: RequestInit) => Promise<issueOAuthTokenResponse>;
+export type getOptionsContractsResponse200 = {
+    data: GetOptionsContracts200;
+    status: 200;
+};
+export type getOptionsContractsResponseSuccess = (getOptionsContractsResponse200) & {
+    headers: Headers;
+};
+export type getOptionsContractsResponse = (getOptionsContractsResponseSuccess);
+export declare const getGetOptionsContractsUrl: (params?: GetOptionsContractsParams) => string;
+/**
+ * This endpoint allows you to retrieve a list of option contracts based on various filtering criteria.
+ * By default only active contracts that expire before the upcoming weekend are returned.
+ * @summary Get Option Contracts (BETA)
+ */
+export declare const getOptionsContracts: (params?: GetOptionsContractsParams, options?: RequestInit) => Promise<getOptionsContractsResponse>;
+export type getOptionContractSymbolOrIdResponse200 = {
+    data: OptionContract;
+    status: 200;
+};
+export type getOptionContractSymbolOrIdResponse404 = {
+    data: Error;
+    status: 404;
+};
+export type getOptionContractSymbolOrIdResponseSuccess = (getOptionContractSymbolOrIdResponse200) & {
+    headers: Headers;
+};
+export type getOptionContractSymbolOrIdResponseError = (getOptionContractSymbolOrIdResponse404) & {
+    headers: Headers;
+};
+export type getOptionContractSymbolOrIdResponse = (getOptionContractSymbolOrIdResponseSuccess | getOptionContractSymbolOrIdResponseError);
+export declare const getGetOptionContractSymbolOrIdUrl: (symbolOrId: string) => string;
+/**
+ * Get an option contract by symbol or contract ID. The symbol or id should be passed in as a path parameter.
+ * @summary Get an option contract by ID or Symbol (BETA)
+ */
+export declare const getOptionContractSymbolOrId: (symbolOrId: string, options?: RequestInit) => Promise<getOptionContractSymbolOrIdResponse>;
+export type getV1RebalancingPortfoliosResponse200 = {
+    data: Portfolio[];
+    status: 200;
+};
+export type getV1RebalancingPortfoliosResponseSuccess = (getV1RebalancingPortfoliosResponse200) & {
+    headers: Headers;
+};
+export type getV1RebalancingPortfoliosResponse = (getV1RebalancingPortfoliosResponseSuccess);
+export declare const getGetV1RebalancingPortfoliosUrl: (params?: GetV1RebalancingPortfoliosParams) => string;
+/**
+ * Lists portfolios.
+ *
+ * When more than one query parameter is passed, only portfolios meeting all provided values will be returned (logical AND between parameter values).
+ * @summary List Portfolios
+ */
+export declare const getV1RebalancingPortfolios: (params?: GetV1RebalancingPortfoliosParams, options?: RequestInit) => Promise<getV1RebalancingPortfoliosResponse>;
+export type postV1RebalancingPortfoliosResponse200 = {
+    data: Portfolio;
+    status: 200;
+};
+export type postV1RebalancingPortfoliosResponseSuccess = (postV1RebalancingPortfoliosResponse200) & {
+    headers: Headers;
+};
+export type postV1RebalancingPortfoliosResponse = (postV1RebalancingPortfoliosResponseSuccess);
+export declare const getPostV1RebalancingPortfoliosUrl: () => string;
+/**
+ * Creates a portfolio allocation containing securities and/or cash. Having no rebalancing conditions is allowed but the rebalance event would need to be triggered manually. Portfolios created with API may have multiple rebalance_conditions, but only one of type calendar.
+ * @summary Create Portfolio
+ */
+export declare const postV1RebalancingPortfolios: (postV1RebalancingPortfoliosBody?: PostV1RebalancingPortfoliosBody, options?: RequestInit) => Promise<postV1RebalancingPortfoliosResponse>;
+export type deleteV1RebalancingPortfoliosPortfolioIdResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteV1RebalancingPortfoliosPortfolioIdResponse400 = {
+    data: void;
+    status: 400;
+};
+export type deleteV1RebalancingPortfoliosPortfolioIdResponse422 = {
+    data: void;
+    status: 422;
+};
+export type deleteV1RebalancingPortfoliosPortfolioIdResponseSuccess = (deleteV1RebalancingPortfoliosPortfolioIdResponse204) & {
+    headers: Headers;
+};
+export type deleteV1RebalancingPortfoliosPortfolioIdResponseError = (deleteV1RebalancingPortfoliosPortfolioIdResponse400 | deleteV1RebalancingPortfoliosPortfolioIdResponse422) & {
+    headers: Headers;
+};
+export type deleteV1RebalancingPortfoliosPortfolioIdResponse = (deleteV1RebalancingPortfoliosPortfolioIdResponseSuccess | deleteV1RebalancingPortfoliosPortfolioIdResponseError);
+export declare const getDeleteV1RebalancingPortfoliosPortfolioIdUrl: (portfolioId: string) => string;
+/**
+ * Sets a portfolio to "inactive", so it can be filtered out of the list request. Only permitted if there are no active subscriptions to this portfolio and this portfolio is not a listed in the weights of any active portfolios.
+ *
+ * Inactive portfolios cannot be linked in new subscriptions or added as weights to new portfolios.
+ * @summary Inactivate Portfolio By ID
+ */
+export declare const deleteV1RebalancingPortfoliosPortfolioId: (portfolioId: string, options?: RequestInit) => Promise<deleteV1RebalancingPortfoliosPortfolioIdResponse>;
+export type getV1RebalancingPortfoliosPortfolioIdResponse200 = {
+    data: Portfolio;
+    status: 200;
+};
+export type getV1RebalancingPortfoliosPortfolioIdResponseSuccess = (getV1RebalancingPortfoliosPortfolioIdResponse200) & {
+    headers: Headers;
+};
+export type getV1RebalancingPortfoliosPortfolioIdResponse = (getV1RebalancingPortfoliosPortfolioIdResponseSuccess);
+export declare const getGetV1RebalancingPortfoliosPortfolioIdUrl: (portfolioId: string) => string;
+/**
+ * Get a portfolio by its ID.
+ * @summary Get Portfolio by ID
+ */
+export declare const getV1RebalancingPortfoliosPortfolioId: (portfolioId: string, options?: RequestInit) => Promise<getV1RebalancingPortfoliosPortfolioIdResponse>;
+export type patchV1RebalancingPortfoliosPortfolioIdResponse200 = {
+    data: Portfolio;
+    status: 200;
+};
+export type patchV1RebalancingPortfoliosPortfolioIdResponseSuccess = (patchV1RebalancingPortfoliosPortfolioIdResponse200) & {
+    headers: Headers;
+};
+export type patchV1RebalancingPortfoliosPortfolioIdResponse = (patchV1RebalancingPortfoliosPortfolioIdResponseSuccess);
+export declare const getPatchV1RebalancingPortfoliosPortfolioIdUrl: (portfolioId: string) => string;
+/**
+ * Updates a portfolio. If weights or conditions are changed, all subscribed accounts will be evaluated for rebalancing at the next opportunity (normal market hours). If a cooldown is active on the portfolio, the rebalancing will occur after the cooldown expired.
+ * @summary Update Portfolio by ID
+ */
+export declare const patchV1RebalancingPortfoliosPortfolioId: (portfolioId: string, patchV1RebalancingPortfoliosPortfolioIdBody?: PatchV1RebalancingPortfoliosPortfolioIdBody, options?: RequestInit) => Promise<patchV1RebalancingPortfoliosPortfolioIdResponse>;
+export type getV1RebalancingRunsResponse200 = {
+    data: PortfolioRun[];
+    status: 200;
+};
+export type getV1RebalancingRunsResponseSuccess = (getV1RebalancingRunsResponse200) & {
+    headers: Headers;
+};
+export type getV1RebalancingRunsResponse = (getV1RebalancingRunsResponseSuccess);
+export declare const getGetV1RebalancingRunsUrl: (params?: GetV1RebalancingRunsParams) => string;
+/**
+ * Lists runs.
+ * @summary List All Runs.
+ */
+export declare const getV1RebalancingRuns: (params?: GetV1RebalancingRunsParams, options?: RequestInit) => Promise<getV1RebalancingRunsResponse>;
+export type postV1RebalancingRunsResponse200 = {
+    data: void;
+    status: 200;
+};
+export type postV1RebalancingRunsResponseSuccess = (postV1RebalancingRunsResponse200) & {
+    headers: Headers;
+};
+export type postV1RebalancingRunsResponse = (postV1RebalancingRunsResponseSuccess);
+export declare const getPostV1RebalancingRunsUrl: () => string;
+/**
+ * Manually creates a run.
+ *
+ * The determination of a run's orders and the execution of a run take place during normal market hours
+ *
+ * Runs can be initiated either by the system (when the system evaluates the rebalance conditions specified at the portfolio level) or by API call (manual run creation using POST /v1/rebalancing/runs). Runs can be initiated manually outside of the normal market hours but will remain in the QUEUED status until normal market hours
+ *
+ * Only 1 run in a non-terminal status is allowed at any time.
+ *
+ * Manually executing a run is currently only allowed for accounts who do not have an active subscription.
+ * @summary Create Run (Manual rebalancing event)
+ */
+export declare const postV1RebalancingRuns: (postV1RebalancingRunsBody?: PostV1RebalancingRunsBody, options?: RequestInit) => Promise<postV1RebalancingRunsResponse>;
+export type deleteV1RebalancingRunsRunIdResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteV1RebalancingRunsRunIdResponseSuccess = (deleteV1RebalancingRunsRunIdResponse204) & {
+    headers: Headers;
+};
+export type deleteV1RebalancingRunsRunIdResponse = (deleteV1RebalancingRunsRunIdResponseSuccess);
+export declare const getDeleteV1RebalancingRunsRunIdUrl: (runId: string) => string;
+/**
+ * Cancels a run. Only runs within certain statuses (QUEUED, CANCELED, SELLS_IN_PROGRESS, BUYS_IN_PROGRESS) are cancelable. If this endpoint is called after orders have been submitted, we'll attempt to cancel the orders.
+ * @summary Cancel Run by ID
+ */
+export declare const deleteV1RebalancingRunsRunId: (runId: string, options?: RequestInit) => Promise<deleteV1RebalancingRunsRunIdResponse>;
+export type getV1RebalancingRunsRunIdResponse200 = {
+    data: PortfolioRun;
+    status: 200;
+};
+export type getV1RebalancingRunsRunIdResponseSuccess = (getV1RebalancingRunsRunIdResponse200) & {
+    headers: Headers;
+};
+export type getV1RebalancingRunsRunIdResponse = (getV1RebalancingRunsRunIdResponseSuccess);
+export declare const getGetV1RebalancingRunsRunIdUrl: (runId: string) => string;
+/**
+ * Get a run by its ID.
+ * @summary Get Run by ID
+ */
+export declare const getV1RebalancingRunsRunId: (runId: string, options?: RequestInit) => Promise<getV1RebalancingRunsRunIdResponse>;
+export type getV1RebalancingSubscriptionsResponse200 = {
+    data: GetV1RebalancingSubscriptions200;
+    status: 200;
+};
+export type getV1RebalancingSubscriptionsResponseSuccess = (getV1RebalancingSubscriptionsResponse200) & {
+    headers: Headers;
+};
+export type getV1RebalancingSubscriptionsResponse = (getV1RebalancingSubscriptionsResponseSuccess);
+export declare const getGetV1RebalancingSubscriptionsUrl: (params?: GetV1RebalancingSubscriptionsParams) => string;
+/**
+ * Lists subscriptions
+ * @summary List All Subscriptions
+ */
+export declare const getV1RebalancingSubscriptions: (params?: GetV1RebalancingSubscriptionsParams, options?: RequestInit) => Promise<getV1RebalancingSubscriptionsResponse>;
+export type postV1RebalancingSubscriptionsResponse200 = {
+    data: PortfolioSubscription;
+    status: 200;
+};
+export type postV1RebalancingSubscriptionsResponseSuccess = (postV1RebalancingSubscriptionsResponse200) & {
+    headers: Headers;
+};
+export type postV1RebalancingSubscriptionsResponse = (postV1RebalancingSubscriptionsResponseSuccess);
+export declare const getPostV1RebalancingSubscriptionsUrl: () => string;
+/**
+ * Creates a subscription between an account and a portfolio.
+ * @summary Create Subscription
+ */
+export declare const postV1RebalancingSubscriptions: (postV1RebalancingSubscriptionsBody?: PostV1RebalancingSubscriptionsBody, options?: RequestInit) => Promise<postV1RebalancingSubscriptionsResponse>;
+export type deleteV1RebalancingSubscriptionsSubscriptionIdResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteV1RebalancingSubscriptionsSubscriptionIdResponseSuccess = (deleteV1RebalancingSubscriptionsSubscriptionIdResponse204) & {
+    headers: Headers;
+};
+export type deleteV1RebalancingSubscriptionsSubscriptionIdResponse = (deleteV1RebalancingSubscriptionsSubscriptionIdResponseSuccess);
+export declare const getDeleteV1RebalancingSubscriptionsSubscriptionIdUrl: (subscriptionId: string) => string;
+/**
+ * Deletes the subscription which stops the rebalancing of an account.
+ * @summary Unsubscribe Account (Delete Subscription)
+ */
+export declare const deleteV1RebalancingSubscriptionsSubscriptionId: (subscriptionId: string, options?: RequestInit) => Promise<deleteV1RebalancingSubscriptionsSubscriptionIdResponse>;
+export type getV1RebalancingSubscriptionsSubscriptionIdResponse200 = {
+    data: PortfolioSubscription;
+    status: 200;
+};
+export type getV1RebalancingSubscriptionsSubscriptionIdResponseSuccess = (getV1RebalancingSubscriptionsSubscriptionIdResponse200) & {
+    headers: Headers;
+};
+export type getV1RebalancingSubscriptionsSubscriptionIdResponse = (getV1RebalancingSubscriptionsSubscriptionIdResponseSuccess);
+export declare const getGetV1RebalancingSubscriptionsSubscriptionIdUrl: (subscriptionId: string) => string;
+/**
+ * Get a subscription by its ID.
+ * @summary Get Subscription by ID
+ */
+export declare const getV1RebalancingSubscriptionsSubscriptionId: (subscriptionId: string, options?: RequestInit) => Promise<getV1RebalancingSubscriptionsSubscriptionIdResponse>;
+export type getV1ReportingEodAggregatePositionsResponse200 = {
+    data: AggregatePositionResponse[];
+    status: 200;
+};
+export type getV1ReportingEodAggregatePositionsResponseSuccess = (getV1ReportingEodAggregatePositionsResponse200) & {
+    headers: Headers;
+};
+export type getV1ReportingEodAggregatePositionsResponse = (getV1ReportingEodAggregatePositionsResponseSuccess);
+export declare const getGetV1ReportingEodAggregatePositionsUrl: (params: GetV1ReportingEodAggregatePositionsParams) => string;
+/**
+ * This API endpoint provides reporting data to partners for aggregate common stock and crypto positions across their account base. Partners can view historical snapshots of their holding across their entire account base. Please note that this API utilizes an 8:00 pm (EST) cutoff which aligns with the end of the Securities extended hours trading session as well as Alpaca's 24 hour Crypto trading window. Additionally, the endpoint supports indexing to help the partner efficiently filter by key information including date and symbol while being able to include or remove firm accounts.
+ * @summary Retrieve Aggregate Positions
+ */
+export declare const getV1ReportingEodAggregatePositions: (params: GetV1ReportingEodAggregatePositionsParams, options?: RequestInit) => Promise<getV1ReportingEodAggregatePositionsResponse>;
+export type getV1GetEodCashInterestReportResponse200 = {
+    data: EoDCashInterestReportResponse;
+    status: 200;
+};
+export type getV1GetEodCashInterestReportResponse400 = {
+    data: Error;
+    status: 400;
+};
+export type getV1GetEodCashInterestReportResponse401 = {
+    data: Error;
+    status: 401;
+};
+export type getV1GetEodCashInterestReportResponse429 = {
+    data: Error;
+    status: 429;
+};
+export type getV1GetEodCashInterestReportResponse500 = {
+    data: Error;
+    status: 500;
+};
+export type getV1GetEodCashInterestReportResponseSuccess = (getV1GetEodCashInterestReportResponse200) & {
+    headers: Headers;
+};
+export type getV1GetEodCashInterestReportResponseError = (getV1GetEodCashInterestReportResponse400 | getV1GetEodCashInterestReportResponse401 | getV1GetEodCashInterestReportResponse429 | getV1GetEodCashInterestReportResponse500) & {
+    headers: Headers;
+};
+export type getV1GetEodCashInterestReportResponse = (getV1GetEodCashInterestReportResponseSuccess | getV1GetEodCashInterestReportResponseError);
+export declare const getGetV1GetEodCashInterestReportUrl: (params?: GetV1GetEodCashInterestReportParams) => string;
+/**
+ * This API retrieves a list of cash interest details for the given date(s) for a single account or all accounts. End-of-day (EOD) details are typically accessible after 8:00pm Eastern Time (ET) and reflect that day's ending state across cash balances, accrued interest, accrued fees, as well as additional ancillary details.
+ * @summary Retrieve EOD Cash Interest Details
+ */
+export declare const getV1GetEodCashInterestReport: (params?: GetV1GetEodCashInterestReportParams, options?: RequestInit) => Promise<getV1GetEodCashInterestReportResponse>;
+export type getV1ReportingEodPositionsResponse200 = {
+    data: GetV1ReportingEodPositions200;
+    status: 200;
+};
+export type getV1ReportingEodPositionsResponse422 = {
+    data: void;
+    status: 422;
+};
+export type getV1ReportingEodPositionsResponseSuccess = (getV1ReportingEodPositionsResponse200) & {
+    headers: Headers;
+};
+export type getV1ReportingEodPositionsResponseError = (getV1ReportingEodPositionsResponse422) & {
+    headers: Headers;
+};
+export type getV1ReportingEodPositionsResponse = (getV1ReportingEodPositionsResponseSuccess | getV1ReportingEodPositionsResponseError);
+export declare const getGetV1ReportingEodPositionsUrl: (params?: GetV1ReportingEodPositionsParams) => string;
+/**
+ * This API retrieves a comprehensive list of end-of-day positions for all accounts. End-of-day (EOD) positions are typically accessible after 4:00 am Eastern Time (ET) on the following day, providing a comprehensive view of the day's closing positions across all accounts.
+ * This API currently only supports retrieving EOD positions for the last trading date.
+ * @summary Retrieve EOD Positions
+ */
+export declare const getV1ReportingEodPositions: (params?: GetV1ReportingEodPositionsParams, options?: RequestInit) => Promise<getV1ReportingEodPositionsResponse>;
+export type getTradingAccountResponse200 = {
+    data: TradeAccount;
+    status: 200;
+};
+export type getTradingAccountResponseSuccess = (getTradingAccountResponse200) & {
+    headers: Headers;
+};
+export type getTradingAccountResponse = (getTradingAccountResponseSuccess);
+export declare const getGetTradingAccountUrl: (accountId: string) => string;
+/**
+ * As a broker you can view more trading details about your users.
+ *
+ * The response is a Trading Account model.
+ * @summary Retrieve Trading Details for an Account
+ */
+export declare const getTradingAccount: (accountId: string, options?: RequestInit) => Promise<getTradingAccountResponse>;
+export type patchPATCHV1TradingAccountsAccountIdAccountConfigurationsResponse200 = {
+    data: AccountConfigurations;
+    status: 200;
+};
+export type patchPATCHV1TradingAccountsAccountIdAccountConfigurationsResponseSuccess = (patchPATCHV1TradingAccountsAccountIdAccountConfigurationsResponse200) & {
+    headers: Headers;
+};
+export type patchPATCHV1TradingAccountsAccountIdAccountConfigurationsResponse = (patchPATCHV1TradingAccountsAccountIdAccountConfigurationsResponseSuccess);
+export declare const getPatchPATCHV1TradingAccountsAccountIdAccountConfigurationsUrl: (accountId: string) => string;
+/**
+ * You can also set the margin settings for your users' account by passing a PATCH request. By default any account with funds under $2,000 is set a margin multiplier of 1.0, and accounts with over $2,000 are set to 2.0.
+ * @summary Update Trading Configurations for an Account
+ */
+export declare const patchPATCHV1TradingAccountsAccountIdAccountConfigurations: (accountId: string, accountConfigurations?: AccountConfigurations, options?: RequestInit) => Promise<patchPATCHV1TradingAccountsAccountIdAccountConfigurationsResponse>;
+export type pdtOneTimeRemovalResponse200 = {
+    data: PDTRemoval;
+    status: 200;
+};
+export type pdtOneTimeRemovalResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type pdtOneTimeRemovalResponseSuccess = (pdtOneTimeRemovalResponse200) & {
+    headers: Headers;
+};
+export type pdtOneTimeRemovalResponseError = (pdtOneTimeRemovalResponse403) & {
+    headers: Headers;
+};
+export type pdtOneTimeRemovalResponse = (pdtOneTimeRemovalResponseSuccess | pdtOneTimeRemovalResponseError);
+export declare const getPdtOneTimeRemovalUrl: (accountId: string) => string;
+/**
+ * **Deprecation notice**
+ *
+ * FINRA's revised Rule 4210 replaces the legacy Pattern Day Trading (PDT) framework with an intraday margin regime, so this endpoint no longer reflects current regulatory behavior. See https://docs.alpaca.markets/us/docs/understanding-finras-new-intraday-margin-rule-and-the-end-of-pdt
+ *
+ * This endpoint will be sunset July 6, 2026. Please remove calls to PDT-specific endpoints before this date.
+ *
+ * ---
+ *
+ * Requests the exercise of pattern day trader one time removal for given account
+ * @deprecated
+ * @summary Exercise PDT one time removal
+ */
+export declare const pdtOneTimeRemoval: (accountId: string, options?: RequestInit) => Promise<pdtOneTimeRemovalResponse>;
+export type pdtGetStatusResponse200 = {
+    data: PDTStatus;
+    status: 200;
+};
+export type pdtGetStatusResponseSuccess = (pdtGetStatusResponse200) & {
+    headers: Headers;
+};
+export type pdtGetStatusResponse = (pdtGetStatusResponseSuccess);
+export declare const getPdtGetStatusUrl: (accountId: string) => string;
+/**
+ * **Deprecation notice**
+ *
+ * FINRA's revised Rule 4210 replaces the legacy Pattern Day Trading (PDT) framework with an intraday margin regime, so this endpoint no longer reflects current regulatory behavior. See https://docs.alpaca.markets/us/docs/understanding-finras-new-intraday-margin-rule-and-the-end-of-pdt
+ *
+ * This endpoint will be sunset July 6, 2026. Please remove calls to PDT-specific endpoints before this date.
+ *
+ * ---
+ *
+ * Retrieves the account's pattern day trader status
+ * @deprecated
+ * @summary Get Pattern Day Trader Status for account
+ */
+export declare const pdtGetStatus: (accountId: string, options?: RequestInit) => Promise<pdtGetStatusResponse>;
+export type getV1TradingAccountsAccountIdAccountPortfolioHistoryResponse200 = {
+    data: PortfolioHistory;
+    status: 200;
+};
+export type getV1TradingAccountsAccountIdAccountPortfolioHistoryResponseSuccess = (getV1TradingAccountsAccountIdAccountPortfolioHistoryResponse200) & {
+    headers: Headers;
+};
+export type getV1TradingAccountsAccountIdAccountPortfolioHistoryResponse = (getV1TradingAccountsAccountIdAccountPortfolioHistoryResponseSuccess);
+export declare const getGetV1TradingAccountsAccountIdAccountPortfolioHistoryUrl: (accountId: string, params?: GetV1TradingAccountsAccountIdAccountPortfolioHistoryParams) => string;
+/**
+ * Returns timeseries data about equity and profit/loss (P/L) of the account in requested timespan.
+ * @summary Get Account Portfolio History
+ */
+export declare const getV1TradingAccountsAccountIdAccountPortfolioHistory: (accountId: string, params?: GetV1TradingAccountsAccountIdAccountPortfolioHistoryParams, options?: RequestInit) => Promise<getV1TradingAccountsAccountIdAccountPortfolioHistoryResponse>;
+export type getV1AccountTradingLimitsResponse200 = {
+    data: AccountTradingLimit;
+    status: 200;
+};
+export type getV1AccountTradingLimitsResponse404 = {
+    data: void;
+    status: 404;
+};
+export type getV1AccountTradingLimitsResponseSuccess = (getV1AccountTradingLimitsResponse200) & {
+    headers: Headers;
+};
+export type getV1AccountTradingLimitsResponseError = (getV1AccountTradingLimitsResponse404) & {
+    headers: Headers;
+};
+export type getV1AccountTradingLimitsResponse = (getV1AccountTradingLimitsResponseSuccess | getV1AccountTradingLimitsResponseError);
+export declare const getGetV1AccountTradingLimitsUrl: (accountId: string) => string;
+/**
+ * This endpoint is only available to accounts with the trading limits feature enabled, and not on JIT.
+ * The daily trading limit is set at the correspondent level (or the account level) and is used as the limit for the total amount due to Alpaca on the date of settlement.
+ * The limit in use returns the real time usage of this limit, based on the setup it uses the usage is calculated differently.
+ * If the limit in use reaches the `daily_net_limit` or `available` is zero, further purchasing activity will be halted, however, the limit can be adjusted by reaching out to Alpaca with the proposed new limit and the reason for the change.
+ * @summary Retrieve real-time Trading Limits for an Account
+ */
+export declare const getV1AccountTradingLimits: (accountId: string, options?: RequestInit) => Promise<getV1AccountTradingLimitsResponse>;
+export type deleteAllOrdersForAccountResponse207 = {
+    data: OrderClosedResponse[];
+    status: 207;
+};
+export type deleteAllOrdersForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type deleteAllOrdersForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type deleteAllOrdersForAccountResponseSuccess = (deleteAllOrdersForAccountResponse207) & {
+    headers: Headers;
+};
+export type deleteAllOrdersForAccountResponseError = (deleteAllOrdersForAccountResponse400 | deleteAllOrdersForAccountResponse404) & {
+    headers: Headers;
+};
+export type deleteAllOrdersForAccountResponse = (deleteAllOrdersForAccountResponseSuccess | deleteAllOrdersForAccountResponseError);
+export declare const getDeleteAllOrdersForAccountUrl: (accountId: string) => string;
+/**
+ * Attempts to cancel all open orders. A response will be provided for each order that is attempted to be cancelled.
+ * @summary Cancel all Open Orders For an Account
+ */
+export declare const deleteAllOrdersForAccount: (accountId: string, options?: RequestInit) => Promise<deleteAllOrdersForAccountResponse>;
+export type getAllOrdersForAccountResponse200 = {
+    data: Order[];
+    status: 200;
+};
+export type getAllOrdersForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type getAllOrdersForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type getAllOrdersForAccountResponseSuccess = (getAllOrdersForAccountResponse200) & {
+    headers: Headers;
+};
+export type getAllOrdersForAccountResponseError = (getAllOrdersForAccountResponse400 | getAllOrdersForAccountResponse404) & {
+    headers: Headers;
+};
+export type getAllOrdersForAccountResponse = (getAllOrdersForAccountResponseSuccess | getAllOrdersForAccountResponseError);
+export declare const getGetAllOrdersForAccountUrl: (accountId: string, params?: GetAllOrdersForAccountParams) => string;
+/**
+ * Retrieves a list of orders for the account, filtered by the supplied query parameters.
+ *
+ * Endpoint defaults to open orders if no parameters are provided.
+ * @summary Retrieve a List of Orders
+ */
+export declare const getAllOrdersForAccount: (accountId: string, params?: GetAllOrdersForAccountParams, options?: RequestInit) => Promise<getAllOrdersForAccountResponse>;
+export type createOrderForAccountResponse200 = {
+    data: Order;
+    status: 200;
+};
+export type createOrderForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type createOrderForAccountResponse403 = {
+    data: ForbiddenResponse;
+    status: 403;
+};
+export type createOrderForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type createOrderForAccountResponse422 = {
+    data: void;
+    status: 422;
+};
+export type createOrderForAccountResponseSuccess = (createOrderForAccountResponse200) & {
+    headers: Headers;
+};
+export type createOrderForAccountResponseError = (createOrderForAccountResponse400 | createOrderForAccountResponse403 | createOrderForAccountResponse404 | createOrderForAccountResponse422) & {
+    headers: Headers;
+};
+export type createOrderForAccountResponse = (createOrderForAccountResponseSuccess | createOrderForAccountResponseError);
+export declare const getCreateOrderForAccountUrl: (accountId: string) => string;
+/**
+ * Creating an order for your end customer. Each trading request must pass in the account_id in the URL.
+ *
+ * - Note that when submitting crypto orders, `market`, `limit` and `stop_limit` orders are supported while the supported `time_in_force` values are `gtc`, and `ioc`.
+ * - For equities and crypto we accept fractional orders as well with either `notional` or `qty` provided.
+ * - Note that submitting an options order is only available for partners who have been enabled for Options BETA.
+ * - In case of Fixed Income, only `market` and `limit` order types with `day` `time_in_force` are supported, and order replacement is not supported.
+ * Note that submitting Fixed Income orders is only available for partners who have been enabled for Fixed Income.
+ * - For IPO indications of interest (`asset_class: "ipo"`), the `symbol` is the offering reference returned by [`GET /v1/ipos`](#operation/listIPOOfferings) (e.g. `FI111225`). IPO orders are notional-only (`notional` required, `qty` must be omitted), buy-side, `market` type, and `gtc` time_in_force. Indications of interest can be replaced or canceled while the offering is open via [`PATCH /v1/trading/accounts/{account_id}/orders/{order_id}`](#operation/replaceOrderForAccount) and [`DELETE /v1/trading/accounts/{account_id}/orders/{order_id}`](#operation/deleteOrderForAccount).
+ * @summary Create an Order for an Account
+ */
+export declare const createOrderForAccount: (accountId: string, createOrderRequest: CreateOrderRequest, options?: RequestInit) => Promise<createOrderForAccountResponse>;
+export type deleteOrderForAccountResponse204 = {
+    data: void;
+    status: 204;
+};
+export type deleteOrderForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type deleteOrderForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type deleteOrderForAccountResponseSuccess = (deleteOrderForAccountResponse204) & {
+    headers: Headers;
+};
+export type deleteOrderForAccountResponseError = (deleteOrderForAccountResponse400 | deleteOrderForAccountResponse404) & {
+    headers: Headers;
+};
+export type deleteOrderForAccountResponse = (deleteOrderForAccountResponseSuccess | deleteOrderForAccountResponseError);
+export declare const getDeleteOrderForAccountUrl: (accountId: string, orderId: string) => string;
+/**
+ * Attempts to cancel an open order. If the order is no longer cancelable (for example if the status is "filled"), the server will respond with status 422, and reject the request.
+ *
+ * Upon acceptance of the cancel request, it returns status 204.
+ * @summary Cancel an Open Order
+ */
+export declare const deleteOrderForAccount: (accountId: string, orderId: string, options?: RequestInit) => Promise<deleteOrderForAccountResponse>;
+export type getOrderForAccountResponse200 = {
+    data: Order;
+    status: 200;
+};
+export type getOrderForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type getOrderForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type getOrderForAccountResponseSuccess = (getOrderForAccountResponse200) & {
+    headers: Headers;
+};
+export type getOrderForAccountResponseError = (getOrderForAccountResponse400 | getOrderForAccountResponse404) & {
+    headers: Headers;
+};
+export type getOrderForAccountResponse = (getOrderForAccountResponseSuccess | getOrderForAccountResponseError);
+export declare const getGetOrderForAccountUrl: (accountId: string, orderId: string) => string;
+/**
+ * Retrieves a single order for the given order_id.
+ * @summary Retrieve an Order by its ID
+ */
+export declare const getOrderForAccount: (accountId: string, orderId: string, options?: RequestInit) => Promise<getOrderForAccountResponse>;
+export type replaceOrderForAccountResponse200 = {
+    data: Order;
+    status: 200;
+};
+export type replaceOrderForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type replaceOrderForAccountResponse403 = {
+    data: void;
+    status: 403;
+};
+export type replaceOrderForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type replaceOrderForAccountResponseSuccess = (replaceOrderForAccountResponse200) & {
+    headers: Headers;
+};
+export type replaceOrderForAccountResponseError = (replaceOrderForAccountResponse400 | replaceOrderForAccountResponse403 | replaceOrderForAccountResponse404) & {
+    headers: Headers;
+};
+export type replaceOrderForAccountResponse = (replaceOrderForAccountResponseSuccess | replaceOrderForAccountResponseError);
+export declare const getReplaceOrderForAccountUrl: (accountId: string, orderId: string) => string;
+/**
+ * Replaces a single order with updated parameters. Each parameter overrides the corresponding attribute of the existing order. The other attributes remain the same as the existing order.
+ *
+ * A success return code from a replaced order does NOT guarantee the existing open order has been replaced. If the existing open order is filled before the replacing (new) order reaches the execution venue, the replacing (new) order is rejected, and these events are sent in the trade_updates stream channel found [here](https://docs.alpaca.markets/reference/subscribetotradev2sse).
+ *
+ * While an order is being replaced, the account's buying power is reduced by the larger of the two orders that have been placed (the old order being replaced, and the newly placed order to replace it). If you are replacing a buy entry order with a higher limit price than the original order, the buying power is calculated based on the newly placed order. If you are replacing it with a lower limit price, the buying power is calculated based on the old order.
+ *
+ * Note: Order cannot be replaced when the status is `accepted`, `pending_new`, `pending_cancel` or `pending_replace`.
+ *
+ * Note: Notional orders for non-IPO asset classes cannot be replaced. Any attempt to modify a non-IPO notional order via this endpoint will be rejected; cancel it and submit a new one instead.
+ *
+ * Note: IPO indications of interest (`asset_class: "ipo"`) **are** notional and **can** be replaced via this endpoint by providing a new `notional` value. `qty` and `notional` are mutually exclusive on a single replace request.
+ * @summary Replace an Order
+ */
+export declare const replaceOrderForAccount: (accountId: string, orderId: string, updateOrderRequest: UpdateOrderRequest, options?: RequestInit) => Promise<replaceOrderForAccountResponse>;
+export type getV1TradingAccountsAccountIdOrdersEstimationResponse200 = {
+    data: Order;
+    status: 200;
+};
+export type getV1TradingAccountsAccountIdOrdersEstimationResponseSuccess = (getV1TradingAccountsAccountIdOrdersEstimationResponse200) & {
+    headers: Headers;
+};
+export type getV1TradingAccountsAccountIdOrdersEstimationResponse = (getV1TradingAccountsAccountIdOrdersEstimationResponseSuccess);
+export declare const getGetV1TradingAccountsAccountIdOrdersEstimationUrl: (accountId: string) => string;
+/**
+ * Order estimation endpoint will display, based on user's account balance, the estimated quantity and price they will receive for their notional order.
+ *
+ * For LCT - customer's order will include the Alpaca swap_fee, while correspondent side swap_fee is configurable in the API call. Utilising this API does not result in a real order and after the calculation - the user's buying power reverts to the previous state.
+ *
+ * Responses and Errors are the same as with the Orders API
+ *
+ * Please note that the estimation is based on the market condition at the time of submission and a live order will differ. The output should be considered indicative.
+ *
+ * **Note:** This does not support Crypto or non-market orders at this time.
+ * @summary Estimate an Order
+ */
+export declare const getV1TradingAccountsAccountIdOrdersEstimation: (accountId: string, getV1TradingAccountsAccountIdOrdersEstimationBody?: GetV1TradingAccountsAccountIdOrdersEstimationBody, options?: RequestInit) => Promise<getV1TradingAccountsAccountIdOrdersEstimationResponse>;
+export type getOrderByClientOrderIdForAccountResponse200 = {
+    data: Order;
+    status: 200;
+};
+export type getOrderByClientOrderIdForAccountResponse400 = {
+    data: BadRequestResponse;
+    status: 400;
+};
+export type getOrderByClientOrderIdForAccountResponse404 = {
+    data: NotFoundResponse;
+    status: 404;
+};
+export type getOrderByClientOrderIdForAccountResponseSuccess = (getOrderByClientOrderIdForAccountResponse200) & {
+    headers: Headers;
+};
+export type getOrderByClientOrderIdForAccountResponseError = (getOrderByClientOrderIdForAccountResponse400 | getOrderByClientOrderIdForAccountResponse404) & {
+    headers: Headers;
+};
+export type getOrderByClientOrderIdForAccountResponse = (getOrderByClientOrderIdForAccountResponseSuccess | getOrderByClientOrderIdForAccountResponseError);
+export declare const getGetOrderByClientOrderIdForAccountUrl: (accountId: string, params: GetOrderByClientOrderIdForAccountParams) => string;
+/**
+ * Retrieves a single order specified by the client order ID.
+ * @summary Retrieves a single order specified by the client order ID.
+ */
+export declare const getOrderByClientOrderIdForAccount: (accountId: string, params: GetOrderByClientOrderIdForAccountParams, options?: RequestInit) => Promise<getOrderByClientOrderIdForAccountResponse>;
+export type closeAllPositionsForAccountResponse207 = {
+    data: PositionClosedResponse[];
+    status: 207;
+};
+export type closeAllPositionsForAccountResponse500 = {
+    data: void;
+    status: 500;
+};
+export type closeAllPositionsForAccountResponseSuccess = (closeAllPositionsForAccountResponse207) & {
+    headers: Headers;
+};
+export type closeAllPositionsForAccountResponseError = (closeAllPositionsForAccountResponse500) & {
+    headers: Headers;
+};
+export type closeAllPositionsForAccountResponse = (closeAllPositionsForAccountResponseSuccess | closeAllPositionsForAccountResponseError);
+export declare const getCloseAllPositionsForAccountUrl: (accountId: string, params?: CloseAllPositionsForAccountParams) => string;
+/**
+ * Closes (liquidates) all of the account's open long and short positions. A response will be provided for each order that is attempted to be cancelled. If an order is no longer cancelable, the server will respond with status 500 and reject the request.
+ * @summary Close All Positions for an Account
+ */
+export declare const closeAllPositionsForAccount: (accountId: string, params?: CloseAllPositionsForAccountParams, options?: RequestInit) => Promise<closeAllPositionsForAccountResponse>;
+export type getPositionsForAccountResponse200 = {
+    data: Position[];
+    status: 200;
+};
+export type getPositionsForAccountResponseSuccess = (getPositionsForAccountResponse200) & {
+    headers: Headers;
+};
+export type getPositionsForAccountResponse = (getPositionsForAccountResponseSuccess);
+export declare const getGetPositionsForAccountUrl: (accountId: string) => string;
+/**
+ * List open positions for an account
+ * @summary List Open Positions for an Account
+ */
+export declare const getPositionsForAccount: (accountId: string, options?: RequestInit) => Promise<getPositionsForAccountResponse>;
+export type closePositionForAccountBySymbolResponse200 = {
+    data: Order;
+    status: 200;
+};
+export type closePositionForAccountBySymbolResponseSuccess = (closePositionForAccountBySymbolResponse200) & {
+    headers: Headers;
+};
+export type closePositionForAccountBySymbolResponse = (closePositionForAccountBySymbolResponseSuccess);
+export declare const getClosePositionForAccountBySymbolUrl: (accountId: string, symbolOrAssetId: string, params?: ClosePositionForAccountBySymbolParams) => string;
+/**
+ * Closes (liquidates) the account's open position for the given symbol. Works for both long and short positions.
+ * @summary Close a Position for an Account
+ */
+export declare const closePositionForAccountBySymbol: (accountId: string, symbolOrAssetId: string, params?: ClosePositionForAccountBySymbolParams, options?: RequestInit) => Promise<closePositionForAccountBySymbolResponse>;
+export type getPositionsForAccountBySymbolResponse200 = {
+    data: Position;
+    status: 200;
+};
+export type getPositionsForAccountBySymbolResponse404 = {
+    data: void;
+    status: 404;
+};
+export type getPositionsForAccountBySymbolResponseSuccess = (getPositionsForAccountBySymbolResponse200) & {
+    headers: Headers;
+};
+export type getPositionsForAccountBySymbolResponseError = (getPositionsForAccountBySymbolResponse404) & {
+    headers: Headers;
+};
+export type getPositionsForAccountBySymbolResponse = (getPositionsForAccountBySymbolResponseSuccess | getPositionsForAccountBySymbolResponseError);
+export declare const getGetPositionsForAccountBySymbolUrl: (accountId: string, symbolOrAssetId: string) => string;
+/**
+ * Retrieves the account's open position for the given symbol or asset_id.
+ * @summary Get an Open Position for account by Symbol or AssetId
+ */
+export declare const getPositionsForAccountBySymbol: (accountId: string, symbolOrAssetId: string, options?: RequestInit) => Promise<getPositionsForAccountBySymbolResponse>;
+export type optionDoNotExerciseResponse200 = {
+    data: DoNotExerciseResponse;
+    status: 200;
+};
+export type optionDoNotExerciseResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type optionDoNotExerciseResponse422 = {
+    data: Error;
+    status: 422;
+};
+export type optionDoNotExerciseResponseSuccess = (optionDoNotExerciseResponse200) & {
+    headers: Headers;
+};
+export type optionDoNotExerciseResponseError = (optionDoNotExerciseResponse403 | optionDoNotExerciseResponse422) & {
+    headers: Headers;
+};
+export type optionDoNotExerciseResponse = (optionDoNotExerciseResponseSuccess | optionDoNotExerciseResponseError);
+export declare const getOptionDoNotExerciseUrl: (accountId: string, symbolOrContractId: string) => string;
+/**
+ * This endpoint enables users to submit a do-not-exercise (DNE) instruction for a held option contract, preventing automatic exercise at expiry.
+ * By default, Alpaca will automatically exercise in-the-money (ITM) contracts at expiry. This endpoint allows users to override that behavior.
+ * DNE requests will be processed immediately once received. DNE requests submitted between market close and midnight will be rejected to avoid any confusion about when the instruction will take effect.
+ * To cancel a DNE request or to submit an exercise instruction, please contact our support team.
+ * @summary Do Not Exercise an Options Position (BETA)
+ */
+export declare const optionDoNotExercise: (accountId: string, symbolOrContractId: string, doNotExerciseRequest?: DoNotExerciseRequest, options?: RequestInit) => Promise<optionDoNotExerciseResponse>;
+export type optionExerciseResponse200 = {
+    data: ExerciseResponse;
+    status: 200;
+};
+export type optionExerciseResponse403 = {
+    data: Error;
+    status: 403;
+};
+export type optionExerciseResponseSuccess = (optionExerciseResponse200) & {
+    headers: Headers;
+};
+export type optionExerciseResponseError = (optionExerciseResponse403) & {
+    headers: Headers;
+};
+export type optionExerciseResponse = (optionExerciseResponseSuccess | optionExerciseResponseError);
+export declare const getOptionExerciseUrl: (accountId: string, symbolOrContractId: string) => string;
+/**
+ * This endpoint enables users to exercise a held option contract, converting it into the underlying asset based on the specified terms.
+ * All available held shares of this option contract will be exercised.
+ * By default, Alpaca will automatically exercise in-the-money (ITM) contracts at expiry.
+ * Exercise requests will be processed immediately once received. Exercise requests submitted between market close and midnight will be rejected to avoid any confusion about when the exercise will settle.
+ * To cancel an exercise request or to submit a Do-not-exercise (DNE) instruction, you can use the do-not-exercise endpoint or contact our support team.
+ * @summary Exercise an Options Position (BETA)
+ */
+export declare const optionExercise: (accountId: string, symbolOrContractId: string, exerciseRequest?: ExerciseRequest, options?: RequestInit) => Promise<optionExerciseResponse>;
+export type getAllWatchlistsForAccountResponse200 = {
+    data: WatchlistWithoutAsset[];
+    status: 200;
+};
+export type getAllWatchlistsForAccountResponseSuccess = (getAllWatchlistsForAccountResponse200) & {
+    headers: Headers;
+};
+export type getAllWatchlistsForAccountResponse = (getAllWatchlistsForAccountResponseSuccess);
+export declare const getGetAllWatchlistsForAccountUrl: (accountId: string) => string;
+/**
+ * Fetch a list of all watchlists currently in an account.
+ * @summary Retrieve all Watchlists for an Account
+ */
+export declare const getAllWatchlistsForAccount: (accountId: string, options?: RequestInit) => Promise<getAllWatchlistsForAccountResponse>;
+export type createWatchlistForAccountResponse200 = {
+    data: Watchlist;
+    status: 200;
+};
+export type createWatchlistForAccountResponseSuccess = (createWatchlistForAccountResponse200) & {
+    headers: Headers;
+};
+export type createWatchlistForAccountResponse = (createWatchlistForAccountResponseSuccess);
+export declare const getCreateWatchlistForAccountUrl: (accountId: string) => string;
+/**
+ * Returns the watchlist object
+ * @summary Create a New Watchlist for an Account
+ */
+export declare const createWatchlistForAccount: (accountId: string, createWatchlistRequest?: CreateWatchlistRequest, options?: RequestInit) => Promise<createWatchlistForAccountResponse>;
+export type deleteWatchlistFromAccountByIdResponse200 = {
+    data: void;
+    status: 200;
+};
+export type deleteWatchlistFromAccountByIdResponseSuccess = (deleteWatchlistFromAccountByIdResponse200) & {
+    headers: Headers;
+};
+export type deleteWatchlistFromAccountByIdResponse = (deleteWatchlistFromAccountByIdResponseSuccess);
+export declare const getDeleteWatchlistFromAccountByIdUrl: (accountId: string, watchlistId: string) => string;
+/**
+ * Irrevocably delete a watchlist.
+ * @summary Remove a Watchlist
+ */
+export declare const deleteWatchlistFromAccountById: (accountId: string, watchlistId: string, options?: RequestInit) => Promise<deleteWatchlistFromAccountByIdResponse>;
+export type getWatchlistForAccountByIdResponse200 = {
+    data: Watchlist;
+    status: 200;
+};
+export type getWatchlistForAccountByIdResponseSuccess = (getWatchlistForAccountByIdResponse200) & {
+    headers: Headers;
+};
+export type getWatchlistForAccountByIdResponse = (getWatchlistForAccountByIdResponseSuccess);
+export declare const getGetWatchlistForAccountByIdUrl: (accountId: string, watchlistId: string) => string;
+/**
+ * Retrieve Watchlist by ID
+ * @summary Manage watchlists
+ */
+export declare const getWatchlistForAccountById: (accountId: string, watchlistId: string, options?: RequestInit) => Promise<getWatchlistForAccountByIdResponse>;
+export type postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse200 = {
+    data: Watchlist;
+    status: 200;
+};
+export type postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse404 = {
+    data: void;
+    status: 404;
+};
+export type postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse422 = {
+    data: void;
+    status: 422;
+};
+export type postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponseSuccess = (postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse200) & {
+    headers: Headers;
+};
+export type postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponseError = (postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse404 | postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse422) & {
+    headers: Headers;
+};
+export type postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse = (postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponseSuccess | postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponseError);
+export declare const getPostV1TradingAccountsAccountIdWatchlistsWatchlistIdUrl: (accountId: string, watchlistId: string) => string;
+/**
+ * Adds an asset to an existing watchlist.
+ * @summary Add an Asset to a Watchlist
+ */
+export declare const postV1TradingAccountsAccountIdWatchlistsWatchlistId: (accountId: string, watchlistId: string, postV1TradingAccountsAccountIdWatchlistsWatchlistIdBody?: PostV1TradingAccountsAccountIdWatchlistsWatchlistIdBody, options?: RequestInit) => Promise<postV1TradingAccountsAccountIdWatchlistsWatchlistIdResponse>;
+export type replaceWatchlistForAccountByIdResponse200 = {
+    data: Watchlist;
+    status: 200;
+};
+export type replaceWatchlistForAccountByIdResponseSuccess = (replaceWatchlistForAccountByIdResponse200) & {
+    headers: Headers;
+};
+export type replaceWatchlistForAccountByIdResponse = (replaceWatchlistForAccountByIdResponseSuccess);
+export declare const getReplaceWatchlistForAccountByIdUrl: (accountId: string, watchlistId: string) => string;
+/**
+ * Replace entirely the set of securities contained in the watchlist while optionally renaming it. Destructive operation.
+ * @summary Update a Watchlist
+ */
+export declare const replaceWatchlistForAccountById: (accountId: string, watchlistId: string, createWatchlistRequest?: CreateWatchlistRequest, options?: RequestInit) => Promise<replaceWatchlistForAccountByIdResponse>;
+export type deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponse200 = {
+    data: void;
+    status: 200;
+};
+export type deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponse404 = {
+    data: void;
+    status: 404;
+};
+export type deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponseSuccess = (deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponse200) & {
+    headers: Headers;
+};
+export type deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponseError = (deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponse404) & {
+    headers: Headers;
+};
+export type deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponse = (deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponseSuccess | deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponseError);
+export declare const getDeleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolUrl: (accountId: string, watchlistId: string, symbol: string) => string;
+/**
+ * Delete one entry for an asset by symbol name
+ * @summary Remove a Symbol from a Watchlist
+ */
+export declare const deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbol: (accountId: string, watchlistId: string, symbol: string, options?: RequestInit) => Promise<deleteDELETEV1TradingAccountsAccountIdWatchlistsWatchlistIdSymbolResponse>;
+export type getV1TransfersJitLedgerIdBalancesResponse200 = {
+    data: GetV1TransfersJitLedgerIdBalances200;
+    status: 200;
+};
+export type getV1TransfersJitLedgerIdBalancesResponseSuccess = (getV1TransfersJitLedgerIdBalancesResponse200) & {
+    headers: Headers;
+};
+export type getV1TransfersJitLedgerIdBalancesResponse = (getV1TransfersJitLedgerIdBalancesResponseSuccess);
+export declare const getGetV1TransfersJitLedgerIdBalancesUrl: (ledgerId: string, params?: GetV1TransfersJitLedgerIdBalancesParams) => string;
+/**
+ * Returns an array of objects that correspond to each ledger account.
+ * @summary Retrieve JIT Ledger Balances
+ */
+export declare const getV1TransfersJitLedgerIdBalances: (ledgerId: string, params?: GetV1TransfersJitLedgerIdBalancesParams, options?: RequestInit) => Promise<getV1TransfersJitLedgerIdBalancesResponse>;
+export type getV1TransfersJitLedgersResponse200 = {
+    data: JITLedgerAccount[];
+    status: 200;
+};
+export type getV1TransfersJitLedgersResponseSuccess = (getV1TransfersJitLedgersResponse200) & {
+    headers: Headers;
+};
+export type getV1TransfersJitLedgersResponse = (getV1TransfersJitLedgersResponseSuccess);
+export declare const getGetV1TransfersJitLedgersUrl: () => string;
+/**
+ * Returns an array of objects that correspond to each ledger account, each of whichcontain the following attributes.
+ * @summary Retrieve JIT Ledgers
+ */
+export declare const getV1TransfersJitLedgers: (options?: RequestInit) => Promise<getV1TransfersJitLedgersResponse>;
+export type getV1TransfersJitLimitsResponse200 = {
+    data: DailyTradingLimit;
+    status: 200;
+};
+export type getV1TransfersJitLimitsResponseSuccess = (getV1TransfersJitLimitsResponse200) & {
+    headers: Headers;
+};
+export type getV1TransfersJitLimitsResponse = (getV1TransfersJitLimitsResponseSuccess);
+export declare const getGetV1TransfersJitLimitsUrl: () => string;
+/**
+ * The JIT Securities daily trading limit is set at the correspondent level and is used as the limit for the total amount due to Alpaca on the date of settlement. The limit in use returns the real time usage of this limit and is calculated by taking the net of trade and non-trade activity inflows and outflows. If the limit in use reaches the daily net limit, further purchasing activity will be halted, however, the limit can be adjusted by reaching out to Alpaca with the proposed new limit and the reason for the change.
+ * @summary Retrieve Daily Trading Limits
+ */
+export declare const getV1TransfersJitLimits: (options?: RequestInit) => Promise<getV1TransfersJitLimitsResponse>;
+export type getV1TransfersJitReportsResponse200 = {
+    data: JITReport | JITReportDownloadURL;
+    status: 200;
+};
+export type getV1TransfersJitReportsResponseSuccess = (getV1TransfersJitReportsResponse200) & {
+    headers: Headers;
+};
+export type getV1TransfersJitReportsResponse = (getV1TransfersJitReportsResponseSuccess);
+export declare const getGetV1TransfersJitReportsUrl: (params: GetV1TransfersJitReportsParams) => string;
+/**
+ * Retrieves a JIT report for the requested report type and system date. By default, the report is returned inline. For large reports, use response_type=download_url to receive a temporary signed download URL.
+ * @summary Retrieve JIT Reports
+ */
+export declare const getV1TransfersJitReports: (params: GetV1TransfersJitReportsParams, options?: RequestInit) => Promise<getV1TransfersJitReportsResponse>;
+export type getCryptoTransferEstimateResponse200 = {
+    data: GetCryptoTransferEstimate200;
+    status: 200;
+};
+export type getCryptoTransferEstimateResponseDefault = {
+    data: Error;
+    status: Exclude<HTTPStatusCodes, 200>;
+};
+export type getCryptoTransferEstimateResponseSuccess = (getCryptoTransferEstimateResponse200) & {
+    headers: Headers;
+};
+export type getCryptoTransferEstimateResponseError = (getCryptoTransferEstimateResponseDefault) & {
+    headers: Headers;
+};
+export type getCryptoTransferEstimateResponse = (getCryptoTransferEstimateResponseSuccess | getCryptoTransferEstimateResponseError);
+export declare const getGetCryptoTransferEstimateUrl: (params?: GetCryptoTransferEstimateParams) => string;
+/**
+ * Returns the estimated on-chain network (gas) fee for a proposed crypto withdrawal at current chain conditions. Pass the `asset`, `from_address`, `to_address`, and `amount` you intend to send; the response reports the network fee that would be charged for the corresponding transaction.
+ * @summary Returns the estimated gas fee for a proposed transaction.
+ */
+export declare const getCryptoTransferEstimate: (params?: GetCryptoTransferEstimateParams, options?: RequestInit) => Promise<getCryptoTransferEstimateResponse>;
+export type getAccountActivityEventResponse200 = {
+    data: ActivityEventV2;
+    status: 200;
+};
+export type getAccountActivityEventResponseSuccess = (getAccountActivityEventResponse200) & {
+    headers: Headers;
+};
+export type getAccountActivityEventResponse = (getAccountActivityEventResponseSuccess);
+export declare const getGetAccountActivityEventUrl: (accountId: string, eventId: string) => string;
+/**
+ * Returns a single account activity (V2) event for the specified account by ULID `event_id`, delivered as a server-sent event message.
+ *
+ * This is the single-event counterpart to the `subscribeToActivitiesSSE` streaming endpoint, intended for re-fetching an individual activity that was previously observed on the activities stream.
+ * @summary Get a single activity (V2) event by event_id ULID.
+ */
+export declare const getAccountActivityEvent: (accountId: string, eventId: string, options?: RequestInit) => Promise<getAccountActivityEventResponse>;
+export type subscribeToActivitiesSSEResponse200 = {
+    data: ActivityEventV2[];
+    status: 200;
+};
+export type subscribeToActivitiesSSEResponseSuccess = (subscribeToActivitiesSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToActivitiesSSEResponse = (subscribeToActivitiesSSEResponseSuccess);
+export declare const getSubscribeToActivitiesSSEUrl: (params?: SubscribeToActivitiesSSEParams) => string;
+/**
+ * The Events API sends the real-time events and provides historical queries with SSE (Server Sent Events).
+ *
+ * This endpoint streams events on account activities.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query parameter rules:
+ * - If `until` is specified, `since` is required.
+ * - If `until_id` is specified, `since_id` is required.
+ * - You cannot use `since` and `since_id` together.
+ * Behavior:
+ * - If `since` or `since_id` is not specified, this will not return any historic data.
+ * - If `until` or `until_id` is specified, stream will end at the specified point with status 200.
+ *
+ * ---
+ *
+ * Warning: Currently, OAS-3 does not fully support responses from an SSE API.
+ *
+ * In case the client code is generated from this OAS spec, please do not specify `since` and `until`, as the generated client may hang forever waiting for the response to end.
+ *
+ * If you require the streaming capabilities, we recommend not using the generated clients for this specific endpoint until the OAS-3 standards define how to represent this behavior.
+ *
+ * ---
+ *
+ * ###  Comment messages
+ * According to the SSE specification, any line that starts with a colon is a comment which does not contain data.  It is typically a free text that does not follow any data schema. A few examples mentioned below for comment messages.
+ *
+ * #####  Slow client
+ *
+ * The server sends a comment when the client is not consuming messages fast enough. Example: `: you are reading too slowly, dropped 10000 messages`
+ *
+ * ##### Internal server error
+ *
+ * An error message is sent as a comment when the server closes the connection on an internal server error (only sent by the v2 and v2beta1 endpoints). Example: `: internal server error`
+ *
+ * ---
+ * @summary Subscribe to Activity Events (SSE)
+ */
+export declare const subscribeToActivitiesSSE: (params?: SubscribeToActivitiesSSEParams, options?: RequestInit) => Promise<subscribeToActivitiesSSEResponse>;
+export type calendarResponse200 = {
+    data: PublicCalendarResp;
+    status: 200;
+};
+export type calendarResponse400 = {
+    data: N400Response;
+    status: 400;
+};
+export type calendarResponse429 = {
+    data: N429Response;
+    status: 429;
+};
+export type calendarResponse500 = {
+    data: N500Response;
+    status: 500;
+};
+export type calendarResponseSuccess = (calendarResponse200) & {
+    headers: Headers;
+};
+export type calendarResponseError = (calendarResponse400 | calendarResponse429 | calendarResponse500) & {
+    headers: Headers;
+};
+export type calendarResponse = (calendarResponseSuccess | calendarResponseError);
+export declare const getCalendarUrl: (market: "BMO" | "BNYM" | "BOATS" | "CEUX" | "CHIX" | "HKEX" | "IEX" | "IEXG" | "ISE" | "LSE" | "MTA" | "MTAA" | "NASDAQ" | "NYSE" | "OCEA" | "OPRA" | "OTC" | "OTCM" | "SIFMA" | "TADAWUL" | "XAMS" | "XBRU" | "XDUB" | "XETR" | "XETRA" | "XHKG" | "XLIS" | "XLON" | "XNAS" | "XNYS" | "XPAR" | "XSAU", params?: CalendarParams) => string;
+/**
+ * This endpoint returns the market calendar.
+ * @summary Get Market Calendar
+ */
+export declare const calendar: (market: "BMO" | "BNYM" | "BOATS" | "CEUX" | "CHIX" | "HKEX" | "IEX" | "IEXG" | "ISE" | "LSE" | "MTA" | "MTAA" | "NASDAQ" | "NYSE" | "OCEA" | "OPRA" | "OTC" | "OTCM" | "SIFMA" | "TADAWUL" | "XAMS" | "XBRU" | "XDUB" | "XETR" | "XETRA" | "XHKG" | "XLIS" | "XLON" | "XNAS" | "XNYS" | "XPAR" | "XSAU", params?: CalendarParams, options?: RequestInit) => Promise<calendarResponse>;
+export type clockResponse200 = {
+    data: ClockResp;
+    status: 200;
+};
+export type clockResponse400 = {
+    data: N400Response;
+    status: 400;
+};
+export type clockResponse429 = {
+    data: N429Response;
+    status: 429;
+};
+export type clockResponse500 = {
+    data: N500Response;
+    status: 500;
+};
+export type clockResponseSuccess = (clockResponse200) & {
+    headers: Headers;
+};
+export type clockResponseError = (clockResponse400 | clockResponse429 | clockResponse500) & {
+    headers: Headers;
+};
+export type clockResponse = (clockResponseSuccess | clockResponseError);
+export declare const getClockUrl: (params?: ClockParams) => string;
+/**
+ * This API serves information about multiple markets: the current time, if it's a market day, the current phase of the market, etc.
+ * @summary Get Market Clock
+ */
+export declare const clock: (params?: ClockParams, options?: RequestInit) => Promise<clockResponse>;
+export type subscribeToAdminActionSSEResponse200 = {
+    data: (AdminActionLegacyNote | AdminActionLiquidation | AdminActionTransactionCancel)[];
+    status: 200;
+};
+export type subscribeToAdminActionSSEResponseSuccess = (subscribeToAdminActionSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToAdminActionSSEResponse = (subscribeToAdminActionSSEResponseSuccess);
+export declare const getSubscribeToAdminActionSSEUrl: (params?: SubscribeToAdminActionSSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * This endpoint streams events related to administrative actions performed by our systems.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since` and `since_id` can't be used at the same time
+ * Behavior:
+ * - if `since` or `since_id` not specified this will not return any historic data
+ * - if `until` or `until_id` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Warning: Currently OAS-3 doesn't have full support for representing SSE style responses from an API.
+ *
+ * In case the client code is generated from this OAS spec, don't specify a `since` and `until` there is a good chance the generated clients will hang forever waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific endpoint until the OAS-3 standards come to a consensus on how to represent this behavior in OAS-3.
+ *
+ * ---
+ *
+ * ###  Comment messages
+ * According to the SSE specification, any line that starts with a colon is a comment which does not contain data.  It is typically a free text that does not follow any data schema. A few examples mentioned below for comment messages.
+ *
+ * #####  Slow client
+ *
+ * The server sends a comment when the client is not consuming messages fast enough. Example: `: you are reading too slowly, dropped 10000 messages`
+ *
+ * ##### Internal server error
+ *
+ * An error message is sent as a comment when the server closes the connection on an internal server error (only sent by the v2 and v2beta1 endpoints). Example: `: internal server error`
+ *
+ * ---
+ *
+ * **Event Types**
+ *
+ * - **LegacyNote:** Old free text based admin notes
+ * - **Liquidation:** Event for a position liquidation which initialized by an admin
+ * - **TransactionCancel:** Event for a manually cancelled transaction
+ * @summary Subscribe to Admin Action Events (SSE)
+ */
+export declare const subscribeToAdminActionSSE: (params?: SubscribeToAdminActionSSEParams, options?: RequestInit) => Promise<subscribeToAdminActionSSEResponse>;
+export type subscribeToFundingStatusSSEResponse200 = {
+    data: StatusFundingEvent[];
+    status: 200;
+};
+export type subscribeToFundingStatusSSEResponseSuccess = (subscribeToFundingStatusSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToFundingStatusSSEResponse = (subscribeToFundingStatusSSEResponseSuccess);
+export declare const getSubscribeToFundingStatusSSEUrl: (params?: SubscribeToFundingStatusSSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to funding status updates as they get processed by our backoffice, for both end-user and firm accounts.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since` and `since_id` can't be used at the same time
+ * - `until` and `until_id` can't be used at the same time
+ * Behavior:
+ * - if `since` or `since_id` not specified this will not return any historic data
+ * - if `until` or `until_id` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @summary Subscribe to Funding Status Events (SSE)
+ */
+export declare const subscribeToFundingStatusSSE: (params?: SubscribeToFundingStatusSSEParams, options?: RequestInit) => Promise<subscribeToFundingStatusSSEResponse>;
+export type subscribeToIPOEventsSSEResponse200 = {
+    data: IPOEvent[];
+    status: 200;
+};
+export type subscribeToIPOEventsSSEResponseSuccess = (subscribeToIPOEventsSSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToIPOEventsSSEResponse = (subscribeToIPOEventsSSEResponseSuccess);
+export declare const getSubscribeToIPOEventsSSEUrl: (params?: SubscribeToIPOEventsSSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to IPO offering lifecycle updates as they happen - including new offerings, offering updates, prospectus availability, the 60-minute pricing window, account-scoped allocation results, and offering cancellations.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * ---
+ *
+ * **Event types**
+ *
+ * Each event has a `verb` field that determines the shape of `payload`. See the `IPOEvent` schema for the full payload structure for each verb.
+ *
+ * - `Offering` - initial publication of an offering (system-wide).
+ * - `OfferingUpdate` - update to a previously published offering (system-wide).
+ * - `Prospectus` - prospectus document is now available (system-wide).
+ * - `SixtyMinMail` - 60-minute pricing window has opened, no new orders accepted (system-wide).
+ * - `Allocation` - final allocation result for a specific account. **Account-scoped** - `account_id` and `correspondent` are populated.
+ * - `OfferingCancellation` - offering was cancelled. **No `payload` field is present.**
+ *
+ * Use the `offering_reference` field on each event to fetch the full offering metadata via [`GET /v1/ipos/{offering_reference}`](#operation/getIPOOffering).
+ *
+ * ---
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since` and `since_id` can't be used at the same time
+ * - `until` and `until_id` can't be used at the same time
+ *
+ * Behavior:
+ * - if `since` or `since_id` not specified this will not return any historic data
+ * - if `until` or `until_id` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @summary Subscribe to IPO Events (SSE)
+ */
+export declare const subscribeToIPOEventsSSE: (params?: SubscribeToIPOEventsSSEParams, options?: RequestInit) => Promise<subscribeToIPOEventsSSEResponse>;
+export type subscribeToJournalStatusV2SSEResponse200 = {
+    data: JournalStatusEventV2[];
+    status: 200;
+};
+export type subscribeToJournalStatusV2SSEResponseSuccess = (subscribeToJournalStatusV2SSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToJournalStatusV2SSEResponse = (subscribeToJournalStatusV2SSEResponseSuccess);
+export declare const getSubscribeToJournalStatusV2SSEUrl: (params?: SubscribeToJournalStatusV2SSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to journal status updates as they get processed by our backoffice.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since` and `since_id` can't be used at the same time
+ * - `until` and `until_id` can't be used at the same time
+ * Behavior:
+ * - if `since` or `since_id` not specified this will not return any historic data
+ * - if `until` or `until_id` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * There is no compatibility between /v1/events/journals/status and /v2/events/journals/status, the ids (ulid) are always different, and the number of events might also different
+ *
+ * Please note that the new `/v2` endpoint, is the same as, and was originally available under `/v2beta1`.
+ * We encourage all customers to adjust their codebase from that interim beta endpoint to the `/v2` stable endpoint.
+ * In the near future we will setup permanent redirect from `/v2beta1` to `/v2` before we completely remove the beta endpoint.
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @summary Subscribe to Journal Events (SSE)
+ */
+export declare const subscribeToJournalStatusV2SSE: (params?: SubscribeToJournalStatusV2SSEParams, options?: RequestInit) => Promise<subscribeToJournalStatusV2SSEResponse>;
+export type subscribeToSystemEventV2SSEResponse200 = {
+    data: SystemEventV2[];
+    status: 200;
+};
+export type subscribeToSystemEventV2SSEResponseSuccess = (subscribeToSystemEventV2SSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToSystemEventV2SSEResponse = (subscribeToSystemEventV2SSEResponseSuccess);
+export declare const getSubscribeToSystemEventV2SSEUrl: (params?: SubscribeToSystemEventV2SSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to system event updates as they happen in our backend.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since` and `since_id` can't be used at the same time
+ * - `until` and `until_id` can't be used at the same time
+ * Behavior:
+ * - if `since` or `since_id` not specified this will not return any historic data
+ * - if `until` or `until_id` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ * @summary Subscribe to System Events (SSE)
+ */
+export declare const subscribeToSystemEventV2SSE: (params?: SubscribeToSystemEventV2SSEParams, options?: RequestInit) => Promise<subscribeToSystemEventV2SSEResponse>;
+export type subscribeToTradeV2SSEResponse200 = {
+    data: TradeUpdateEventV2[];
+    status: 200;
+};
+export type subscribeToTradeV2SSEResponseSuccess = (subscribeToTradeV2SSEResponse200) & {
+    headers: Headers;
+};
+export type subscribeToTradeV2SSEResponse = (subscribeToTradeV2SSEResponseSuccess);
+export declare const getSubscribeToTradeV2SSEUrl: (params?: SubscribeToTradeV2SSEParams) => string;
+/**
+ * The Events API provides event push as well as historical queries via SSE (server sent events).
+ *
+ * You can listen to events related to trade updates. Most market trades sent during market hours are filled instantly; you can listen to limit order updates through this endpoint.
+ *
+ * Historical events are streamed immediately if queried, and updates are pushed as events occur.
+ *
+ * Query Params Rules:
+ * - `since` required if `until` specified
+ * - `since_id` required if `until_id` specified
+ * - `since` and `since_id` can't be used at the same time
+ * Behavior:
+ * - if `since` or `since_id` not specified this will not return any historic data
+ * - if `until` or `until_id` reached stream will end (status 200)
+ *
+ * ---
+ *
+ * Note for people using the clients generated from this OAS spec. Currently OAS-3 doesn't have full support for representing SSE style responses from an API, so if you are using a generated client and don't specify a `since` and `until` there is a good chance the generated clients will hang waiting for the response to end.
+ *
+ * If you require the streaming capabilities we recommend not using the generated clients for this specific usecase until the OAS-3 standards come to a consensus on how to represent this correctly in OAS-3.
+ *
+ * ---
+ *
+ * **Legacy trade events API**
+ *
+ * **Deprecation notice**
+ *
+ * As part of the deprecation process,
+ * the legacy trade events API is now only available for existing broker-partners at: `GET /v1/events/trades` only for compatibility reasons.
+ *
+ * All new broker partners will not have the option for the legacy trade event endpoint.
+ *
+ * All new broker partners will have to integrate with the new `/v2/events/trades` endpoint.
+ *
+ * Also, all existing broker partners are now recommended to upgrade to the `/v2/events/trades` endpoint, which provides faster event delivery times.
+ *
+ * The legacy trade events api works the same way as the new one with the exception of the event_id which is an integer except of an ULID. This results in the request's since_id and until_id are also being integers. This integer is monotonically increasing over time for events.
+ *
+ * Please note that the new `/v2` endpoint, is the same as, and was originally available under `/v2beta1`.
+ * We encourage all customers to adjust their codebase from that interim beta endpoint to the `/v2` stable endpoint.
+ * In the near future we will setup permanent redirect from `/v2beta1` to `/v2` before we completely remove the beta endpoint.
+ *
+ * ---
+ *
+ * ###  Comment messages
+ * According to the SSE specification, any line that starts with a colon is a comment which does not contain data.  It is typically a free text that does not follow any data schema. A few examples mentioned below for comment messages.
+ *
+ * #####  Slow client
+ *
+ * The server sends a comment when the client is not consuming messages fast enough. Example: `: you are reading too slowly, dropped 10000 messages`
+ *
+ * ##### Internal server error
+ *
+ * An error message is sent as a comment when the server closes the connection on an internal server error (only sent by the v2 and v2beta1 endpoints). Example: `: internal server error`
+ *
+ * ---
+ *
+ * **Common events**
+ *
+ * These are the events that are the expected results of actions you may have taken by sending API requests.
+ *
+ * The meaning of the timestamp field changes for each type; the meanings have been specified here for which types the timestamp field will be present.
+ *
+ * - `accepted` Sent when an order is received and accepted by Alpaca
+ * - `pending_new` Sent when the order has been received by Alpaca and routed to the exchanges, but has not yet been accepted for execution.
+ * - `new` Sent when an order has been routed to exchanges for execution.
+ * - `fill` Sent when your order has been completely filled.
+ *   - timestamp: The time at which the order was filled.
+ * - `partial_fill` Sent when a number of shares less than the total remaining quantity on your order has been filled.
+ *   - timestamp: The time at which the shares were filled.
+ * - `canceled` Sent when your requested cancellation of an order is processed.
+ *   - timestamp: The time at which the order was canceled.
+ * - `expired` Sent when an order has reached the end of its lifespan, as determined by the order's time in force value.
+ *   - timestamp: The time at which the order expired.
+ * - `done_for_day` Sent when the order is done executing for the day, and will not receive further updates until the next trading day.
+ * - `replaced` Sent when your requested replacement of an order is processed.
+ *   - timestamp: The time at which the order was replaced.
+ *
+ * **Rarer events**
+ *
+ * These are events that may rarely be sent due to unexpected circumstances on the exchanges. It is unlikely you will need to design your code around them, but you may still wish to account for the possibility that they will occur.
+ *
+ * - `rejected` Sent when your order has been rejected.
+ *   - timestamp: The time at which the rejection occurred.
+ * - `held` For multi-leg orders, the secondary orders (stop loss, take profit) will enter this state while waiting to be triggered.
+ * - `stopped` Sent when your order has been stopped, and a trade is guaranteed for the order, usually at a stated price or better, but has not yet occurred.
+ * - `pending_cancel` Sent when the order is awaiting cancellation. Most cancellations will occur without the order entering this state.
+ * - `pending_replace` Sent when the order is awaiting replacement.
+ * - `calculated` Sent when the order has been completed for the day - it is either filled or done_for_day - but remaining settlement calculations are still pending.
+ * - `suspended` Sent when the order has been suspended and is not eligible for trading.
+ * - `order_replace_rejected` Sent when the order replace has been rejected.
+ * - `order_cancel_rejected` Sent when the order cancel has been rejected.
+ * - `trade_bust`: Sent when a previously reported execution has been canceled ("busted") by the upstream exchange.
+ * - `trade_correct`: Sent when a previously reported trade has been corrected. For example, the exchange may have updated the price, quantity, or another execution parameter after the trade was initially reported.
+ * - `restated`: Sent when the order is manually modified.
+ * @summary Subscribe to Trade Events (SSE)
+ */
+export declare const subscribeToTradeV2SSE: (params?: SubscribeToTradeV2SSEParams, options?: RequestInit) => Promise<subscribeToTradeV2SSEResponse>;