Smokeball
Legal practice management software with a REST API for managing matters, contacts, documents, time entries, billing, trust accounting, and law firm workflows. The API follows REST principles, accepts JSON, returns JSON, and supports OAuth 2.0 authentication. Available in US, AU, and UK regions.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Smokeball the way a machine reads it — 76 machine-readable artifacts across 34 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Smokeball scores 54.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Smokeball
Each block below is one kind of artifact we hold for Smokeball. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 34
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Smokeball Activity Codes API
The Activity Codes API from Smokeball — 2 operation(s) for activity codes.
Smokeball Authorization API
The Authorization API from Smokeball — 4 operation(s) for authorization.
Smokeball Bank Accounts API
The Bank Accounts API from Smokeball — 9 operation(s) for bank accounts.
Smokeball Contacts API
The Contacts API from Smokeball — 6 operation(s) for contacts.
Smokeball Events API
The Events API from Smokeball — 4 operation(s) for events.
Smokeball Expenses API
The Expenses API from Smokeball — 2 operation(s) for expenses.
Smokeball Fees API
The Fees API from Smokeball — 2 operation(s) for fees.
Smokeball Files API
The Files API from Smokeball — 8 operation(s) for files.
Smokeball Firm API
The Firm API from Smokeball — 3 operation(s) for firm.
Smokeball Folders API
The Folders API from Smokeball — 4 operation(s) for folders.
Smokeball Intake API
The Intake API from Smokeball — 3 operation(s) for intake.
Smokeball Integrated Search API
The Integrated Search API from Smokeball — 1 operation(s) for integrated search.
Smokeball Invoices API
The Invoices API from Smokeball — 3 operation(s) for invoices.
Smokeball Layout Designs API
The Layout Designs API from Smokeball — 2 operation(s) for layout designs.
Smokeball Layout Matter Items API
The Layout Matter Items API from Smokeball — 3 operation(s) for layout matter items.
Smokeball Matter Items API
The Matter Items API from Smokeball — 2 operation(s) for matter items.
Smokeball Matter Types API
The Matter Types API from Smokeball — 3 operation(s) for matter types.
Smokeball Matters API
The Matters API from Smokeball — 6 operation(s) for matters.
Smokeball Memos API
The Memos API from Smokeball — 2 operation(s) for memos.
Smokeball Notifications API
The Notifications API from Smokeball — 2 operation(s) for notifications.
Smokeball Plugins API
The Plugins API from Smokeball — 5 operation(s) for plugins.
Smokeball Portal API
The Portal API from Smokeball — 3 operation(s) for portal.
Smokeball Referral Types API
The Referral Types API from Smokeball — 2 operation(s) for referral types.
Smokeball Relationships API
The Relationships API from Smokeball — 2 operation(s) for relationships.
Smokeball Roles API
The Roles API from Smokeball — 2 operation(s) for roles.
Smokeball Search API
The Search API from Smokeball — 1 operation(s) for search.
Smokeball Staff API
The Staff API from Smokeball — 2 operation(s) for staff.
Smokeball Stages API
The Stages API from Smokeball — 5 operation(s) for stages.
Smokeball Subscription Payments API
The Subscription Payments API from Smokeball — 4 operation(s) for subscription payments.
Smokeball Subscription Promotions API
The Subscription Promotions API from Smokeball — 3 operation(s) for subscription promotions.
Smokeball Subscriptions API
The Subscriptions API from Smokeball — 26 operation(s) for subscriptions.
Smokeball Tasks API
The Tasks API from Smokeball — 6 operation(s) for tasks.
Smokeball Users API
The Users API from Smokeball — 3 operation(s) for users.
Smokeball Webhooks API
The Webhooks API from Smokeball — 4 operation(s) for webhooks.
Scroll within the panel for all 34 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Smokeball Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Smokeball Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Smokeball API Rules
SPECTRALJSON Schema 28
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Smokeball BankAccount
JSON SCHEMASmokeball Contact
JSON SCHEMASmokeball ContactDto
JSON SCHEMASmokeball Event
JSON SCHEMASmokeball EventDto
JSON SCHEMASmokeball Expense
JSON SCHEMASmokeball ExpenseDto
JSON SCHEMASmokeball Fee
JSON SCHEMASmokeball FeeDto
JSON SCHEMASmokeball File
JSON SCHEMASmokeball FirmUser
JSON SCHEMASmokeball Folder
JSON SCHEMASmokeball Invoice
JSON SCHEMASmokeball Matter
JSON SCHEMASmokeball MatterDto
JSON SCHEMASmokeball MatterType
JSON SCHEMASmokeball Memo
JSON SCHEMASmokeball MemoDto
JSON SCHEMASmokeball Role
JSON SCHEMASmokeball RoleDto
JSON SCHEMASmokeball API Schemas
JSON SCHEMASmokeball Staff
JSON SCHEMASmokeball StaffDto
JSON SCHEMASmokeball Tag
JSON SCHEMASmokeball Task
JSON SCHEMASmokeball TaskDto
JSON SCHEMASmokeball WebhookSubscription
JSON SCHEMASmokeball WebhookSubscriptionDto
JSON SCHEMAScroll within the panel for all 28 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Smokeball Contact Example
EXAMPLESmokeball Fee Example
EXAMPLESmokeball Invoice Example
EXAMPLESmokeball Matter Example
EXAMPLESmokeball Task Example
EXAMPLESmokeball Webhook Example
EXAMPLEScroll within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Smokeball — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/smokeball · machine-readable index on apis.io