“Has the API at Japan's Tachibana e-Shiten brokerage returned?”
Not as of November 10, 2026. The company's official notice says the service suspension started at 3:30 p.m. on October 23, 2026. Both its production trading API and its demo API are listed. For development related to migrating equipment, it is aiming for around March 2027.
You wanted an estimated return time. You got a whole new calendar year.
That's a Very Large Definition of “Temporary”
The official wording attributes the suspension to a “PHP issue.” That's what the notice says; it does not establish the precise technical root cause, a specific vulnerability, or who might be responsible.
The list of suspended services is extensive: the live API, demo API, BRiSK Next, a stock-price board, the smartphone-specific site, an AI earnings calendar, and account opening. This is more than one sluggish endpoint.
Developer: “No production access? I'll test on the demo server.”
Announcement: “The demo is suspended too.”
Developer: “Even the emergency exit has a construction sign.”
That's a metaphor for the published outage list, not evidence that every form of manual trading has stopped.
March 2027 Is Not a Promised API Reopening Day
The crucial distinction is the object of the target. The company is targeting around March 2027 for the equipment-migration development and says services will resume progressively as their development and checks are completed.
That does not guarantee an API reopening on March 1. It also doesn't mean every service must stay offline until March. Each actual restart requires a later official update.
Still, what a twist. An interruption begins in late October; you check again in November; the answer points at March of the following year. You clicked on maintenance news and ended up reading a quarterly project roadmap.
What Automated Trading Users Should Do
An automated system may rely on the API for orders, fills, positions, and market data. Without it, the priority is a safe stop rather than an infinite retry loop.
Pause jobs that assume the connection works. Check open orders and exposure using officially supported channels that remain available. If considering another provider, compare its actual API functionality, terms, authentication, fees, request limits, and data coverage. Once service returns, test with small requests and carefully controlled orders before going live at full scale.
Sending another request every second is not a disaster-recovery plan. It's a prayer written in HTTP.
Why the Notice Is So Absurdly Funny
“Temporary outage” suggests hours or maybe days. The official page gives you a month in the following year. It's like opening a game's launcher to find out when maintenance ends and being shown the roadmap for its next expansion. Even the practice server is on the affected list.
The joke is the mismatch between expectations and timescales, not speculation about someone's competence.
Bottom Line
As of November 10, the API had not been confirmed as restored. March 2027 was a development target, not a guaranteed API restart date. Keep following official notices, and design automated workflows that can halt safely if a critical outside service disappears.
“Is it back?”
“No. The answer now comes in fiscal quarters.”
Five-second question. Quarter-sized answer.
References (2)
Checked November 10, 2026. Subsequent official updates take precedence.
