Have an ABOSS workflow that should run itself?
Tell us what you are doing by hand today. We will say whether the API can handle it and what it would take.
Book a discovery callABOSS runs bookings, contracts, advancing, and finances for the live-music industry, and it offers an open REST API so the platform can connect to the rest of your stack. We are a Ruby on Rails team that has built on the ABOSS platform as a contractor, and we now help agencies and artist teams get more out of that API: the integrations, sites, reports, and tools around it.
Six focused services. Each can be bought on its own, and they combine well.
Push invoices, payments, and artist statements from ABOSS into the bookkeeping tool your accountant already uses, so nobody retypes numbers at month-end.
Typically 2–4 weeks
Ask about this
Show live, always-correct show dates on an artist or agency website, straight from ABOSS. Update it once in the platform and the site follows.
Typically 1–2 weeks
Ask about this
Get your booking, deal, and financial data into the place where you actually analyze it, on a schedule, without manual exports.
Typically 2–3 weeks
Ask about this
When something changes in ABOSS, other things should happen on their own. We wire the triggers to the tools your team lives in.
Typically 1–3 weeks
Ask about this
Build the thing ABOSS does not do, on top of the data it already holds. Internal tools, client portals, or products for the wider ecosystem.
Scoped per project
Ask about this
Integrations break quietly: tokens expire, APIs change, a field gets renamed. A monthly plan keeps what we built, or what you already have, healthy.
Monthly retainer
Ask about this
We are independent and want ABOSS to do well. These are the rules we build by.
We build on the documented ABOSS API with OAuth 2.0. No scraping, no screen automation, no workarounds around their platform.
Integrations run on your own ABOSS account with the narrowest scopes that work. We never need to hold your password, and you can revoke access at any time.
Caching, backoff, and sensible polling. Integrations should never be the reason an API has a bad day.
Clean code in your repo or ours, documented and tested. You can keep us on, or take it in-house.
Free, 30 minutes. You describe the manual work or the missing tool; we tell you honestly whether the API can support it.
A written scope, timeline, and price. No open-ended hourly surprises for defined work.
Short iterations against your real data, with a working demo early rather than a reveal at the end.
Monitoring from day one, a handover document, and an optional Care Plan.
Tell us what you are doing by hand today. We will say whether the API can handle it and what it would take.
Book a discovery callRuby Dev is an independent software company and is not owned by, endorsed by, or an official partner of ABOSS. ABOSS is a trademark of its respective owner. Integrations use the ABOSS API under its published terms.