What Is an FSA/HSA API?
An FSA/HSA API lets a company's software show a customer's balance, flag eligible items, help with a letter and get a claim filed. The two kinds, explained.
5 minute read

Short answer
An FSA/HSA API lets a company's own software do FSA and HSA jobs for its customers. Burst's API is for retailers, enterprises and platforms, and it does four jobs: it checks the customer's balance and shows it in your app or site, it flags item by item what can be reimbursed, it helps the customer request a Letter of Medical Necessity, and Burst files the claim.
Two kinds of FSA/HSA API exist. A payment API runs the FSA or HSA card at a checkout. A reimbursement API works after any payment. Burst's API is the second kind: your customer pays the way they already pay, Burst files the claim, and the plan administrator pays them back to their bank account. Burst is free for merchants.
To see it working, book a call with the Burst team.
Book a call with the Burst team →
Why these accounts need an API
An FSA or an HSA holds money set aside before tax for medical expenses. IRS Publication 502 describes which expenses count. Each account sits with a plan administrator, and each administrator has its own site, its own claim form and its own rules for paperwork.
That leaves the account holder doing the work by hand. They open a separate site to see a balance. They guess whether a purchase counts. They find out after buying that it needed a letter from a clinician. A company that wants to help its customers with any of this would have to read balances, judge items, arrange clinician review and prepare claims. An FSA/HSA API does that work so the company doesn't have to.
The four jobs
Job | What your customer sees | What they get |
|---|---|---|
Their FSA/HSA balance in your app or site, after they connect their account | They know how much they have while they shop | |
A flag on each item: eligible outright, reimbursable with a letter, or not reimbursable | A plain label before they buy | |
A letter request started for what they're buying | A Letter of Medical Necessity that a licensed clinician reviews and signs | |
No claim form to fill in | A claim filed for them and money back to their bank account. If it's denied, Burst writes the appeal. |
A company doesn't have to offer all four at once. Some begin with the flag on items, because every shopper sees it on a product page. Others begin with the balance, because that's the number their customers ask for.
Payment APIs and reimbursement APIs
The two kinds do their work at different moments, and that decides what each one asks of your team.
Question | Payment API | Reimbursement API |
|---|---|---|
When does it act? | During checkout | After the purchase |
How does the customer pay? | With their FSA or HSA card, through a payment option added to your checkout | With any card or payment method you already accept |
What changes for you? | Your checkout and payment flow | Nothing at checkout or billing |
Where does the account money go? | From the account to you, as the payment | From the account to the customer's bank account, as a reimbursement |
Which jobs does it cover? | Taking the payment | Balance, item-level eligibility, letters and claims |
When a payment API fits
A payment API fits when your goal is to accept the FSA or HSA card as a way to pay, and your team is ready to add a payment option to checkout and maintain it. The customer needs the card in hand and needs to choose that option when they pay.
When a reimbursement API fits
A reimbursement API fits when you want to leave checkout alone. That covers a retailer with a checkout it won't reopen, an app billed through an app store, a gym or studio with recurring billing, and any business whose customers pay with credit cards, debit cards or buy now pay later. It also fits when you want the jobs around the purchase: showing a balance, flagging items and helping with the letter. Accepting HSA and FSA without an integration covers the same idea for a small business that sets Burst up itself.
How Burst's API does it
Burst's API covers the four jobs for the customers of retailers, enterprises and platforms. A customer connects their FSA/HSA account and sees their balance in your app. Each item they look at carries a flag. Where an item needs a letter, the customer requests one for what they're buying, and a licensed clinician reviews and signs it. Burst files the claim with the plan administrator, and the money comes back to the customer's bank account. Your checkout stays as it is.
Burst is the only AI-native FSA/HSA company: a person can point their AI agent to Burst to request a Letter of Medical Necessity, and retailers, enterprises and platforms use Burst's API to show customers their balance, flag which items can be reimbursed, help them request letters and file their claims.
Access is by request, through an intro call with the Burst team.
Frequently asked questions
Is an FSA/HSA API the same as accepting HSA cards?
No. Accepting the card is one kind, the payment API. A reimbursement API never touches the card. It gets the customer paid back from the account after they've paid you another way.
Who uses an FSA/HSA API?
Retailers, enterprises and platforms whose customers ask "can I use my HSA for this" while they shop or manage their benefits.
Does a reimbursement API change our checkout?
No. The customer pays the way they already do. With Burst, nothing changes at your checkout or billing.
Can the API tell us whether a product can be reimbursed?
It can. Burst flags each item with one of three answers: eligible outright, reimbursable with a letter, or not reimbursable.
What does Burst cost a merchant?
Burst is free for merchants. The customer pays a one-time letter fee when their purchase needs a letter.
Can our own shopping or benefits assistant use it?
It can. An assistant inside your product can show the customer their balance, tell them whether an item can be reimbursed and help them request a letter, using the same four jobs your app uses.
More on AI and FSA/HSA: the FSA/HSA API for retailers, enterprises and platforms, what AI-native means for an FSA/HSA company, and all the AI guides.
