Let’s start with “why”
Many people in our industry capitalise FIX in our name, assuming the company is named after the protocol that dominates our niche.
That was certainly part of the thinking, but the primary reason our founder named us FixSpec was to reference fix as a verb. Chris founded the company after repeatedly seeing slow, inefficient onboarding caused by poor, outdated or inaccurate documentation, and brittle manual processes around it. The goal was to move the industry from legacy PDFs to machine-readable API specifications, bringing the same efficiency and automation that OpenAPI brought to REST APIs elsewhere.
Adoption of machine-readable API documentation for non-REST protocols has remained stubbornly slow. But as awareness of non-FIX APIs grows (thanks in large part to new entrants), and AI accelerates the shift from documentation for humans to documentation for machines, we believe the moment for that migration has now arrived.
As we navigate this new world, however, we must avoid duplicating documentation. Firms should not maintain one set of documentation for AI and another for humans. Likewise, QA and conformance should use exactly the same documentation asset that a connecting developer - human or AI - uses. That’s the direction we’re building towards, across the multi-protocol reality of modern trading — FIX and REST today, with binary protocols and WebSocket on our roadmap. The format that has quietly powered FixSpec for over a decade is FinSpec: our extensible JSON schema, now open-sourced under the Apache 2.0 License.
The Path Ahead
We won’t sugarcoat it: migrating from legacy PDFs to modern, machine-readable workflows is a significant undertaking. FixSpec can provide consulting and software, but your team needs to actively engage in the process rather than delegating it to AI, which tends to produce poor outcomes here.
This portal is a key part of that migration. As PDFs are retired, firms need to move to developer portals to improve the developer experience. Trading firms have exceptional engineering talent, but you can’t ask a low-latency C++ developer to deploy and style a developer portal. Likewise, trading product managers understand market structure deeply, but often don’t have the technical writing tooling to organise and maintain content alongside a corporate website that was never designed for this purpose.
FixSpec’s white-labelled portal is our response: easy to maintain, fast to deploy and purpose-built for this use case, delivered alongside the consulting expertise needed to complete the migration.
ℹ️ Info
This website is itself a copy of our white-labelled portal software, so feel free to open your browser’s developer tools and explore the rendered HTML and CSS.
Is It Worth It?
AI-driven development is here to stay, and it changes what “good documentation” needs to mean. As AI increasingly handles API integration work, your existing onboarding workflow is put under strain in ways it wasn’t designed for:
- Humans can smooth over documentation flaws, fill in gaps from experience and know when to ask someone for help. AI needs complete, accurate information up front, or it will confidently get things wrong.
- You can talk a human through conformance testing when something doesn’t quite work. That’s much harder to do when AI is on the other side of the connection.
So this isn’t really a “time saved” calculation. It’s about keeping your onboarding process working at all as more of your counterparties connect via AI rather than a person reading a PDF.
Why can’t I just use an open-source (free) framework?
It’s entirely reasonable for firms to look at free “portal” software before considering a commercial tool. If that’s where you are, here’s what’s out there:
- Swagger UI: perhaps the most mature and widespread OpenAPI rendering library.
- Redocly Redoc: modern OpenAPI rendering which links into a larger ecosystem.
- Docusaurus OpenAPI Plugin, which adds OpenAPI rendering to a Docusaurus site.
- OpenApi2Slate, which converts OpenAPI to Markdown for display in a Slate site.
- Scalar: offers polished OpenAPI rendering, including “Try it Now” functionality.
If you’re a trading firm, though, these all run into the same wall: none of them support the FIX protocol, because it’s too niche a use case for their maintainers to prioritise. Choose one of these and your OpenAPI (REST) documentation will stay neatly synchronised to a re-used machine-readable schema, while your FIX documentation ends up as a basic table that someone has to maintain by hand, or via a script you write and own yourself.
Our focus on trading protocols means the portal supports OpenAPI (REST) and FIX natively, alongside a few other things you won’t get from a general-purpose framework:
- Embedding API definition fragments directly into other documentation, for a familiar, PDF-like reading experience,
- Authentication, so you can restrict documentation to authorised customers only,
- Integration with FixSpec’s self-service conformance tooling,
- Embedded analytics, so you can see who has looked at which documentation.
FAQs
Is FinSpec open source? Yes — FinSpec, the JSON schema format behind FixSpec’s non-REST documentation, is open-sourced under the Apache 2.0 License. See FinSpec for details.
Does the portal only support FIX and REST? Today, yes — FIX and REST are what the portal handles natively. Binary protocols and WebSocket are on our roadmap, as we work towards covering the full multi-protocol reality of modern trading described above.
Do I need to migrate manually, or does FixSpec help with that? FixSpec provides both consulting and software to support the migration from legacy PDFs — see The Path Ahead above. Your team should stay actively involved in the process rather than delegating it entirely.