Smokeball documents a REST API with OAuth, plus webhooks for events such as a new matter, a matter stage change, a new or updated contact, a finalized invoice and fee entries. Access comes through Smokeball's partner program: you apply, and its partnerships or product team follows up.
Reads are broad. Matters, contacts, invoices, fees and bank account transactions, including balances by matter, can all be read.
Writes are narrower. The API can create matters and contacts, and record a deposit against a bank account and matter. Invoices are read-only, and the transaction endpoint lists deposits as its only type, so a refund or withdrawal is still entered in Smokeball by a person. A sound integration flags those for staff instead of skipping them.
That's the shape of what n-frames builds: intake from a CRM or web form that opens the contact and matter without duplicates, payments from outside processors recorded as deposits on the right matter, a finalized invoice that tells your other systems, and a short list of the changes only a person can make.