API & Integrations.

— FAQ

Common questions.

• Can you integrate with a system that does not have a public API?+

  Sometimes. We assess what is available — screen scraping, file-based exchange, native database access or a vendor-specific SDK — and recommend the most reliable approach. If no integration path exists, we tell you clearly.

• What happens when a third-party API changes or goes down?+

  We build with versioning, retry logic and alerting from the start. If a provider changes their API, the scope of the update is usually small and well-understood. We can be on a monthly plan to handle these quickly.

• Do you work with legacy or on-premise systems?+

  Yes. SOAP services, legacy XML APIs, FTP-based data exchange, database-level access — we have worked with them. We assess the integration complexity in discovery before committing to a timeline.

• How do you handle sensitive data moving between systems?+

  With encryption in transit (TLS), scoped credentials, secrets management and data minimisation. We document the data flow and flag any compliance implications — GDPR, PCI-DSS — before the build begins.

• Is everything listed above included in the fixed-price packages?+

  No — the deliverables above describe a custom project, where we scope the work around your goals and the design, build and revision rounds follow what the project actually needs. A package is a deliberately narrower slice of the same craft: defined scope, a set number of revision rounds and a fixed timeline, which is what lets us fix the price. Every package page lists exactly what it includes. Most of our work is custom — that’s where you get the deeper process and decisions made specifically for you.