Splital API integration & OpenData services

Authorization & account binding

We mirror Splital's in-app sign-in to obtain a user-permissioned session token. The wrapper exposes a stable /auth/login and /auth/refresh pair so back-office systems can rotate sessions without changing app behaviour. Useful for finance teams centralising access to multiple users' shared groups.

Group & member sync

Every group on Splital has members, default split ratios, and an active currency. The /groups endpoint returns this metadata, so external tools can mirror the household, trip, or couple group structure used by the original app.

Expense ledger query

Pull individual expense entries — title, amount, category, payer, participants, date, attached photos, and the underlying split shares. Ideal for accounting reconciliation, per-diem reporting, or pulling shared roommate utility bills into a personal-finance dashboard.

Settlement & balance API

Returns the simplified "who owes whom" graph that Splital's debt-simplification engine produces, alongside the raw balance per member. Two outputs let you choose between the optimised settlement path and a complete audit trail of every share.

Multi-currency & FX context

For trips abroad, Splital records both the local currency and the home-currency conversion. Our endpoint surfaces both sides so finance tools can re-price expenses with their own treasury FX rates rather than the in-app one.

Export bridge (CSV / PDF / JSON)

Splital users can already export CSV and PDF from inside the app. We extend this with a hosted JSON envelope plus webhook delivery, so a nightly job can drop a clean expense file into S3, Google Drive, or a SFTP folder for the customer's accountant.

1. Couple finance dashboard

Business context: A neobank or personal-finance product wants to surface a couple's shared spending alongside individual spending. Data involved: the partner group's expense ledger, simplified balance, and category breakdown. OpenFinance mapping: the shared group becomes a virtual joint sub-ledger that can be merged with PSD2 account aggregation, giving each partner a unified "what we spent together vs. alone" view inside their banking app.

2. Group trip reimbursement bot

Business context: A travel platform wants to automate trip settlement when the trip ends. Data involved: the trip group, expense list with FX context, and the settle-up payment graph. OpenFinance mapping: the simplified settlement graph is converted to outbound payment intents in a partner payment rail (SEPA, UPI, ACH), so each traveller sees a single pre-filled transfer instead of mental maths.

3. Roommate utility ingestion into a household budget tool

Business context: A household budgeting SaaS wants to pull recurring rent, utilities, and grocery expenses without manual entry. Data involved: the roommate group, recurring expense detection, attached receipt photos. OpenFinance mapping: each Splital expense becomes a categorised household-ledger row, alongside open-banking transaction data, enabling true "who paid what for the apartment" reporting.

4. Accountant export pipeline for freelancers

Business context: Freelancers and small-business owners often co-fund client trips or coworking memberships. Data involved: filtered expense ledger over a fiscal period, with photos and category tags. OpenData mapping: our nightly job produces a structured JSON file (and matching PDF receipts bundle) dropped into the accountant's SFTP folder, ready for VAT or per-diem reporting.

5. Cross-app unified ledger (Splital + Splitwise + Tricount)

Business context: Many users keep historical data in Splitwise and new groups in Splital. Data involved: Splital's existing Splitwise CSV import endpoints plus our wrapper around the Splital ledger. OpenData mapping: a merged event stream that normalises expense schemas across providers, so dashboards stay accurate when users migrate or run apps in parallel.

1. Authenticated session bootstrap

POST /api/v1/splital/auth/login
Content-Type: application/json

{
  "email": "user@example.com",
  "password": "<encrypted>",
  "device_id": "ext-svc-7af2"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rT8...",
  "expires_in": 3600,
  "user_id": "u_91823"
}

2. Expense ledger query with paging

GET /api/v1/splital/groups/{group_id}/expenses
  ?from=2026-01-01&to=2026-04-29
  &page=1&page_size=50
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "page": 1,
  "total": 217,
  "items": [{
    "expense_id": "e_4421",
    "title": "Dinner — Lisbon trip",
    "amount": 84.50,
    "currency": "EUR",
    "home_amount": 92.10,
    "home_currency": "USD",
    "fx_rate": 1.0900,
    "category": "Food",
    "subcategory": "Restaurants",
    "payer_id": "u_91823",
    "shares": [
      {"member_id":"u_91823","share":42.25},
      {"member_id":"u_77410","share":42.25}
    ],
    "attachments": ["att_7791.jpg"],
    "created_at": "2026-04-12T20:14:11Z"
  }]
}

3. Settlement webhook

POST {customer_webhook_url}
X-Splital-Bridge-Signature: sha256=...
Content-Type: application/json

{
  "event": "group.settlement.updated",
  "group_id": "g_8821",
  "currency": "USD",
  "balances": [
    {"member_id":"u_91823","net": -47.30},
    {"member_id":"u_77410","net":  47.30}
  ],
  "simplified_payments": [
    {"from":"u_91823","to":"u_77410","amount":47.30}
  ],
  "occurred_at": "2026-04-29T08:02:55Z"
}

// Error envelope
{ "error": {"code":"AUTH_EXPIRED","retryable":true} }

Compliance & privacy

All Splital integrations we deliver run under explicit user authorisation; no scraping of third-party data without consent. Because Splital stores personal financial information of EEA users, our reference implementation is built to support GDPR requirements on data export and deletion (the 30-day data subject access window) and aligns with the spirit of PSD2 when settlement data is forwarded to a payment institution. Where pay-out flows are wired to a regulated rail, we add Strong Customer Authentication hooks and consent receipts.

For non-EEA jurisdictions we follow the equivalent local data-protection rule (UK GDPR, Brazil's LGPD, India's DPDP Act). Logging is minimised to integration metadata; raw expense content is never written to our servers when the customer chooses on-prem deployment.

Data flow / architecture

A typical deployment is a four-stage pipeline:

1. Splital app / mobile session — user grants authorisation to our session bridge.
2. Ingestion / wrapper API — normalises expenses, FX, categories into OpenData JSON.
3. Storage layer — customer-side warehouse (BigQuery, Snowflake, Postgres) or message bus (Kafka, SQS).
4. Consumer — accounting tool, dashboard, payment rail, or compliance archive.

Webhooks deliver incremental settlement updates; nightly batch jobs produce the canonical CSV/JSON snapshot.

Deliverables checklist

• OpenAPI / Swagger specification for the Splital wrapper
• Protocol & auth flow report (login, refresh, session lifetime, error map)
• Runnable source for ledger and settlement endpoints (Python or Node.js)
• Webhook signing helper and replay protection sample
• CSV / PDF / JSON export job and SFTP / S3 drop-off recipe
• Automated test suite + Postman collection
• Compliance notes for GDPR data subject requests

Engagement workflow

1. Scope confirmation: target groups (couple / trip / roommate) and required endpoints.
2. Protocol analysis & auth design (2–5 business days).
3. Build & internal validation against test accounts (3–8 business days).
4. Documentation, sample SDK, and test cases (1–2 business days).
5. First delivery typically within 5–15 business days.

FAQ

What do you need from me?

How do you handle privacy?

Can you bridge to other splitting apps too?

About our studio

We are an independent technical studio focused on App interface integration and authorised API integration. The team has hands-on experience in mobile applications and fintech, including expense management, OpenBanking, and cross-border settlement. We deliver protocol analysis, interface refactoring, OpenData integration, third-party interface integration, automated data scripting, and full interface documentation.

• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront fee.
• Coverage of finance, e-commerce, travel, and social app categories across regions.
• Compliant, lawful interface implementations aligned with local privacy law.

Contact

To request a quote or submit your Splital integration scope, open our contact page:

Contact page