ABOSS Integrations

  • Home
  • ABOSS Integrations
image
image
image
imageFor ABOSS agencies, artists & partners

Make ABOSS work with everything else you use

ABOSS 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.

What we offer

Six focused services. Each can be bought on its own, and they combine well.

Accounting & Finance Sync

Push invoices, payments, and artist statements from ABOSS into the bookkeeping tool your accountant already uses, so nobody retypes numbers at month-end.

  • Invoice and payment export to Xero, QuickBooks, Exact, Moneybird and similar
  • Contact and VAT-detail mapping, with duplicate handling
  • Reconciliation report: what is in ABOSS vs. what is in the ledger

Typically 2–4 weeks

Ask about this

Tour-Date Websites & Widgets

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.

  • Next.js, WordPress, or plain-embed widgets
  • Public-safe field selection (you choose what is shown)
  • Cached and rate-limit friendly, so traffic never hits the API directly

Typically 1–2 weeks

Ask about this

Reporting & Data Pipelines

Get your booking, deal, and financial data into the place where you actually analyze it, on a schedule, without manual exports.

  • Nightly sync to Postgres, BigQuery, Google Sheets, or Airtable
  • Dashboards: revenue by territory, artist, agent, or season
  • Custom artist-statement and settlement exports

Typically 2–3 weeks

Ask about this

Workflow Automation

When something changes in ABOSS, other things should happen on their own. We wire the triggers to the tools your team lives in.

  • Confirmed deal → Slack message, Drive folder, calendar hold
  • New advancing details → ticketing, travel, or production tools
  • n8n, Make, Zapier, or a small hosted service, whichever fits

Typically 1–3 weeks

Ask about this

Custom Apps on the ABOSS API

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.

  • Internal dashboards and approval tools for agencies
  • Client or promoter portals with scoped access

Scoped per project

Ask about this

Integration Care Plan

Integrations break quietly: tokens expire, APIs change, a field gets renamed. A monthly plan keeps what we built, or what you already have, healthy.

  • Uptime and failure alerts, with a human who reads them
  • OAuth token and credential rotation
  • Updates when the ABOSS API changes (it is in beta, so it will)

Monthly retainer

Ask about this

How we work with the platform

We are independent and want ABOSS to do well. These are the rules we build by.

Official API only

We build on the documented ABOSS API with OAuth 2.0. No scraping, no screen automation, no workarounds around their platform.

Your data, your credentials

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.

Kind to the platform

Caching, backoff, and sensible polling. Integrations should never be the reason an API has a bad day.

Built to be handed over

Clean code in your repo or ours, documented and tested. You can keep us on, or take it in-house.

How an engagement runs

01Discovery call

Free, 30 minutes. You describe the manual work or the missing tool; we tell you honestly whether the API can support it.

02Fixed-scope proposal

A written scope, timeline, and price. No open-ended hourly surprises for defined work.

03Build & test

Short iterations against your real data, with a working demo early rather than a reveal at the end.

04Launch & support

Monitoring from day one, a handover document, and an optional Care Plan.

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 call

Ruby 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.