API Integration and Development Services
Payment, carrier, health and building-system integrations that keep working when the other side doesn't. Our Sydney team has built and run API integrations for Australian products since 2006, including Shippit and Airtasker.
build with Sentia
API integration services built for when things go wrong upstream.
The happy path is the easy part.
Connecting two APIs from the docs takes days. Keeping it working when the other side times out, renames a field or sends the same event twice is the real job.
Where incidents start.
Most production incidents begin in the integration layer, not your own code. A slow carrier or a payment webhook that never arrives becomes your customer's problem.
Invisible when it's done well.
Good integration work is the part nobody notices. Data arrives, payments reconcile and orders ship, because the layer underneath was built and maintained properly.
Integrations we've built and run in production.
Our API integration developers have connected Australian products to payment providers, carrier networks, national health infrastructure and building hardware. A few examples.

Payment flows that reconcile.
Most payment work goes well beyond a basic Stripe checkout: split transactions, escrow, payouts and real-time authorisation, reconciled against the books.
Explore financial servicesTransaction processing, payouts and reconciliation across the payment providers your product uses.
Real-time payment authorisation, approved by the customer directly from their bank account.
Accounting and financial reporting kept in step with your product, so the books match what happened.
Split transactions, escrow or delayed release, refunds and disputes, built into the payment flow.

One reliable view across every carrier.
Carrier APIs are inconsistent, data formats vary and SLAs differ. We build the layer above them, so operators get one view whoever is carrying the freight.
Explore transport and logisticsRates, bookings and tracking across providers, whatever their API, data format or service type.
Real-time tracking across carriers and delivery legs, so merchants and customers see every step.
Catch-e, novated leasing and the financial workflows that sit around fleet management.
Live data streaming, operational alerts and driver notifications that go out as things change.

National infrastructure, built to its standards.
Some integrations need more than an API key. We've built against health and government systems and know the access rules and data standards they involve.
See our workIntegrations with eRx, Medicare and PBS, built to the compliance standards these systems require.
NSW ePlanning Portal and Spatial Viewer, built around their data standards and access rules.
GNAF, Australia's authoritative address dataset, so addresses match the national record.
Building certification, sign-off and strata levy obligations, built into the software itself.

Software that talks to hardware.
Access control, sensors and location beacons need fast, two-way communication. We connect platforms to the physical systems inside a building.
Explore property and constructionBrivo, Origo Access and Smartalock, connected so your software can manage who gets in and when.
Shelly devices connected to your platform, so building systems can be read and controlled.
Minew RTLS beacons for real-time location, so you know where people and assets are on site.
Data that moves when events happen, not on a schedule, so what your team sees is current.
API development services for your own product.
Sometimes the API you need doesn't exist yet. Usually it's part of a bigger build, which is where our custom software development team comes in.
APIs other teams can build on.
We design and build APIs for your partners, your customers and your own web and mobile apps, so other teams can connect to your product without a workaround.
Client libraries we publish.
When an API is hard to work with, we wrap it in a library your team can use. Some are public: we publish and maintain Ruby gems for the Zai and Airwallex APIs.
Open source you can read.
Our gems are public, so your team can read the code we write before working with us. See our Zai and Airwallex gems on GitHub.
How we approach integration development.
Understand upstream first.
Before writing any code, we learn how the other system really behaves: its rate limits, its failure modes and what its documentation quietly leaves out.
Build for failure.
Timeouts, retries, duplicate events and bad data are designed in from day one, so one slow or broken provider doesn't take your whole product down with it.
Real-time where it matters.
Event-driven integrations move data the moment something happens, not on a nightly schedule, so your team and your customers always see what's true now.
Monitored after launch.
We add monitoring that flags a slowing or degrading upstream service early, so a failing provider is caught and dealt with before it becomes a bigger problem.
Products we've connected
Shippit
Industry
Transport & Logistics, Retail & eCommerce
Airtasker
Industry
On-demand Service, Marketplace
Paylab
Industry
Financial Services & Fintech, Retail & eCommerce



