Questions about customer support, market data accuracy, transparency, and proprietary trading information from an existing paying customer considering a $100,000 IRA transfer.
I first heard about Alpaca Markets several years ago while researching programmatic trading platforms and looking for a brokerage with a decent API. At the time, I was primarily trading futures, so Alpaca wasn’t particularly well suited to my needs.
Fast-forward to a few months ago.
I began researching trading platforms, API providers, and brokerages again because I had become increasingly active trading equities in one of my retirement accounts at Fidelity.
Fidelity is an excellent brokerage for traditional investing and buy-and-hold strategies. However, automated trade execution through an API isn’t an option for my needs.
That’s when Alpaca Markets appeared in my searches again.
My plan was straightforward:
- Open an Alpaca paper trading account.
- Develop and thoroughly test an automated trading platform using its API.
- Subscribe to its paid market data service to obtain the real-time data necessary for development and testing.
- Once satisfied with the platform and brokerage, transfer approximately $100,000 from an existing Fidelity retirement account into an IRA established at Alpaca.
And to be clear, I’m already paying Alpaca for its premium market data feed.
I’m not someone who simply opened a free account, browsed the documentation, and decided to complain.
I’m an existing paying customer who has invested considerable time developing software around Alpaca’s API, with the intention of establishing a substantially larger financial relationship.
Sounds reasonable, right?
Well, that’s where things started getting interesting.
The Research and First Red Flags
During the development process, I spent considerable time reviewing Alpaca’s API documentation, browsing this community forum, and researching customer experiences on independent review platforms.
What I discovered was concerning.
According to the Trustpilot figures I reviewed, Alpaca Markets had the following customer ratings:
Alpaca Markets — Trustpilot Customer Reviews
Overall Rating: 2.1 out of 5 stars
Total Reviews: 44
5-Star Reviews: 25%
1-Star Reviews: 64%
Reviews in the Past 12 Months: 22
Nearly two-thirds of those reviewers gave Alpaca the lowest possible rating of just one star.
Several reviews described problems involving unanswered support inquiries, difficulty reaching customer service representatives, delayed withdrawals, and account-access issues.
Some of these complaints sounded remarkably similar to the difficulties I’ve experienced firsthand.
To be fair, Alpaca also receives positive reviews, particularly from developers who appreciate its API and automated trading capabilities. Its TradingView ratings are considerably more favorable.
I recognize that online reviews are subjective and don’t necessarily represent the experiences of the company’s entire customer base.
Nevertheless, when multiple customers independently describe similar problems, I believe prospective customers have good reason to investigate those concerns before transferring substantial amounts of money.
I decided to give Alpaca the benefit of the doubt and evaluate the company based on my own experience.
August 21, 2026 — My First Support Inquiry
On August 21, I emailed Alpaca’s support address with a relatively straightforward question about available funding methods.
Why?
Because several of the company’s webpages appeared to contain outdated information, and I wanted confirmation before initiating a substantial retirement account transfer.
I didn’t receive a response until September 11.
That’s 21 days to receive what amounted to a generic response to a basic funding question.
Not exactly confidence-inspiring.
Additional Support Tickets — Mostly Silence
Since then, I’ve submitted approximately four additional support tickets.
Of those four, I’ve received a response to exactly one.
And that response concerned a widespread market data feed outage, meaning Alpaca could presumably send essentially the same explanation to every affected customer.
The remaining tickets?
Crickets.
No meaningful responses. No indication that anyone is actively investigating the issues. Nothing that inspires confidence in the organization’s customer support capabilities.
And here’s what makes this particularly frustrating:
I’m paying Alpaca for its premium market data feed.
I’m not expecting unlimited technical consulting or someone to debug my trading application. I’m simply expecting reasonable customer support for services I’m already paying to use.
When a customer is paying for market data and encounters technical or service-related issues, is it unreasonable to expect someone to respond to a support ticket?
Apparently, that expectation may be too ambitious.
Concerns About Market Data Accuracy
I’ve also encountered some troubling discrepancies with Alpaca’s paid SIP market data feed.
For example, on August 17, 2026, Alpaca reported SOXL trades around $148.53–$148.56, while other market data indicated prices closer to $150.60–$150.95.
These transactions significantly affected the reported one-minute price range, potentially influencing automated trading strategies that rely on accurate highs, lows, and execution prices.
I understand that off-exchange transactions and extended-hours trading can produce unusual prints. However, developers paying for premium market data should be able to obtain timely technical explanations when discrepancies of this magnitude occur.
If we can’t confidently interpret the market data we’re paying for—and can’t get support when something looks wrong—how are we supposed to trust it for automated trading?
October 26, 2026 — Does Anyone Answer the Phone?
Today, after growing increasingly frustrated with the lack of communication, I decided to search for an actual telephone number.
A Google search returned the following:
Crypto Support / Complaints Phone Number:
(855) 825-7222 (855-8-ALPACA)
I decided to give it a call.
Here’s what happened:
The phone rang once.
A recorded message announced that calls may be recorded.
Then…
BEEP.
That was it.
No professional greeting identifying the company. No automated menu. No explanation of whether I’d reached customer support, a complaints department, or someone’s voicemail.
Just a beep.
I’ve encountered small, family-owned businesses operating out of garages with more professional telephone systems.
And we’re talking about a financial services company that wants customers to entrust it with their investment capital.
To be clear, I cannot independently confirm that the number returned by Google is an official Alpaca customer support line. But the experience only reinforces my concern about how difficult it is to find a reliable way to contact someone.
Is Alpaca Actually Serious About Attracting and Retaining Customers?
I understand that Alpaca is a technology-focused brokerage, and I appreciate the capabilities its API provides.
In fact, that’s precisely why I became interested in the company.
But having a good API is only one component of operating a successful brokerage.
Customer service, operational transparency, responsiveness, and accessibility matter just as much — particularly when you’re asking customers to transfer substantial amounts of their retirement savings.
So I’d genuinely like to understand:
Does Alpaca want individual retail customers?
Is the company primarily focused on institutional clients and API integrations?
Are individual investors simply not a priority?
And perhaps most importantly:
Does Alpaca seriously expect prospective customers to feel comfortable transferring $100,000 or more when existing paying customers can’t even get basic support questions answered?
The Irony of Being an API-First, Technology-Focused Brokerage
Here’s what I find particularly frustrating.
Alpaca positions itself as a modern, technology-driven brokerage operating in an era of sophisticated automation and artificial intelligence.
Yet some of the most basic customer-facing functions appear to be missing or poorly implemented.
Surely a company with Alpaca’s technical capabilities could implement systems that:
- Respond to support inquiries within a reasonable timeframe, even if only to acknowledge receipt and provide an estimated response time.
- Answer telephone calls professionally, rather than leaving callers wondering whether they’ve reached the correct organization.
- Maintain accurate, current website documentation, particularly regarding account funding and retirement accounts.
- Provide a reliable escalation process for unresolved customer issues.
- Offer meaningful support to customers paying for premium services, especially when those services are experiencing problems.
- Demonstrate that customer communication is a priority, rather than an afterthought.
We’re not talking about revolutionary technological advancements here.
These are basic operational expectations.
What Is Alpaca’s Actual Business Objective?
There’s another question I’ve increasingly found myself asking throughout this experience:
What exactly is Alpaca’s long-term business objective, and where do independent algorithmic traders fit into that business model?
Alpaca actively appeals to developers building automated trading systems. Its API is arguably one of its most attractive features.
But that raises some interesting questions.
When developers build proprietary trading strategies around Alpaca’s infrastructure, the brokerage potentially has visibility into considerable amounts of information about their trading activity.
Depending on the systems involved, that could include order timing, execution patterns, position management, trading frequency, and other information that might reveal aspects of a strategy.
As someone who has invested substantial time developing proprietary automated trading software, I think it’s entirely reasonable to ask:
- What information does Alpaca collect about the trading strategies its customers develop and execute through its API?
- Does Alpaca analyze customer trading activity beyond what is necessary for order execution, compliance, risk management, and normal brokerage operations?
- Can Alpaca or its affiliates use aggregated or individual customer trading data to develop proprietary trading models, algorithms, or other commercial products?
- Are customer trading patterns, execution data, or strategy-related information shared with third parties?
- What contractual protections prevent proprietary trading information from being used for purposes unrelated to providing brokerage services?
- Are there meaningful differences in how Alpaca handles trading data generated through paper accounts versus funded brokerage accounts?
To be absolutely clear, I’m not claiming to have evidence that Alpaca is misappropriating anyone’s trading strategies.
But I do believe developers have every right to understand how their intellectual property and trading information are protected.
After all, we’re not simply using a brokerage’s website to buy a few shares of stock.
Some of us are developing sophisticated, proprietary trading systems that represent hundreds or thousands of hours of research, development, and testing.
And when a company actively markets its API capabilities to developers while seemingly struggling to provide even basic customer support, I think it’s fair to ask:
Is Alpaca primarily interested in attracting long-term brokerage customers, generating revenue from API-driven trading activity, or obtaining access to the valuable trading data generated by developers using its platform?
Those objectives aren’t necessarily mutually exclusive. Nor would collecting trading data automatically imply improper conduct.
But transparency matters.
If Alpaca wants developers to trust it with both their capital and their proprietary trading activity, it should be willing to explain exactly how that information is collected, protected, and used.
Until those questions are answered, I remain cautious about committing either substantial retirement funds or additional proprietary trading development to the platform.
Final Thoughts
I genuinely wanted Alpaca to work out.
I’ve invested considerable time developing and testing an automated trading platform around its API. I’ve subscribed to its paid market data service, and I was prepared to establish a meaningful, long-term brokerage relationship.
But at this point, I have serious reservations.
If this is the level of responsiveness I can expect as an existing PAYING customer, BEFORE transferring $100,000, what should I expect AFTER Alpaca has custody of those funds?
And what happens when the issue isn’t a routine support question, but something urgent involving an account, an execution problem, a paid market data service, or access to retirement funds?
I would genuinely appreciate a response from someone at Alpaca who can address these concerns — particularly someone in a position to speak to the company’s customer service standards, business objectives, and policies governing customer trading data.
I’d also be interested in hearing from existing customers who have substantial funds deposited with Alpaca.
Has your experience been different? Are you able to obtain timely assistance when something goes wrong?
Because right now, based on my personal experience, Alpaca has done very little to earn my confidence as a brokerage.
And that’s unfortunate, because the API itself is exactly what attracted me to the company in the first place.
A capable API may attract developers, but reliable customer service, transparency, and trust are what ultimately convince them to commit their capital.
/gw