Delivery Check

Fixed-scope API assurance for integration delivery teams.

Delivery Check gives integration and automation delivery partners an additional assurance layer before client delivery. You provide the API, working test environment and relevant delivery information. We challenge the implementation beyond the happy path and return a structured evidence report.

Fixed-scope engagement

One Delivery Check includes

One API product · Up to 10 endpoints · One test environment · One agreed test-data set · One retest round · Up to 40 hours of assurance work · Evidence report within 15 working days of confirmed working access.

What we examine

The exact tests depend on the API, but the engagement may challenge contract and behavioural correctness, input and boundary handling, error behaviour, dependency failure, data transformation, state consistency, retry behaviour, partial failure, recovery behaviour and gaps in the existing test evidence.

The purpose is not simply to execute more tests. It is to establish what the available evidence supports — and what it does not.

What you receive

Your Delivery Evidence Report records the engagement boundary, existing evidence, assurance evidence, material findings, coverage gaps, retest evidence, and untested or unresolved areas.

AIKUS provides evidence for the delivery team and client. The release decision remains with them.

What we need before testing starts

API specification or equivalent documentation, a working test environment, required credentials, usable test data, access to dependencies or suitable stubs, relevant existing tests where available, and the identity and sector of the end client.

The 15-working-day delivery window starts only after working access is confirmed. If the environment becomes materially unavailable, the delivery clock pauses. If usable access cannot be restored within five working days, the engagement may need to be re-scoped.

Fixed scope means fixed scope

The standard Delivery Check covers one API product and up to 10 endpoints. Additional APIs, endpoints, environments, test-data sets, further retest rounds or materially changed implementations require separate scope.

We do not perform unsolicited testing against production systems or systems for which testing has not been explicitly authorised.