← All workBalaji SankarCase study 12 / 12
Fintech / tax compliance / developer tools2020-21NDA · name withheld

Tax APIPortal

The public developer portal for a global tax-compliance platform: API references generated from Swagger, integration guides, SDK docs and demos that make live API calls right from the page.

Client

A global tax-compliance software company

Role

Co-lead frontend developer

Timeline

2020-21

Stack
Next.jsReactstyled-componentsTailwind CSSreact-markdownOpenAPI / SwaggerGitLab CIAWS S3 + CloudFrontTerraform
Outcomes
~18 mo

Embedded with the client’s engineering team

✦

One templated portal covering API references, integration guides and SDKs

Thechallenge

The company had dozens of APIs - tax calculation, exemption certificates, VAT, item classification, document management and more - and needed one developer portal that partners and customer engineers could actually use.

Content was spread across products and formats, references came from Swagger files, and integration guides for ecommerce, ERP, marketplace and hospitality partners all had different shapes. It had to be fast, searchable and deployable through the client’s own pipeline.

How Iapproached it

01

Config-driven pages

Products, guides and references described in JSON and Markdown and rendered through shared Next.js dynamic routes and layouts, so a new guide is mostly content, not code.

02

References you can explore

API reference pages generated from OpenAPI files, with a request and response console and an API explorer with side navigation.

03

Docs you can try

Live demos against the real API: a sample tax calculation with address input, a test-credentials checker, an integration-check flow and an exemption-certificate capture demo.

04

Static, fast and searchable

A fully pre-rendered export served from S3 behind CloudFront, with a search index generated at build time from the same configs that drive the pages.

Highlightsworth showing

  • (01)

    Dozens of products and guides rendered through one set of templates.

  • (02)

    Live API calls from the docs instead of static samples.

  • (03)

    Search with no search server - the index is built at deploy time.

  • (04)

    Separate CI, QA and production environments with cache invalidation on every release.

  • (05)

    Worked directly inside the client’s engineering team, ticketing and review process for around 18 months.

Have a project like this?

Tell me what you’re building or what’s broken. I’ll tell you straight whether I’m the right person for it.

Next caseProcurement / B2B SaaS2026Django to React with a Claude skill set→