Contract snapshot 0.101.0 · Deployment and client release availability follow the integration note for your environment.
Pin a supplied release
The core client is generated from the same route schemas as OpenAPI. Pin the version in your integration note and verify its release hashes.
Keep tokens fresh
The client accepts a token callback so each request can use a fresh session. REWALTO_CORE_API_URL selects the environment. Credentials stay in server code.
Version boundaries
The API path is /v1. This guide renders from the pinned client contract. Check the connected service version and integration note independently; contract, client release and deployed API are separate versions.
Keep the integration boundary on the server
Let the application server obtain credentials and call the generated client, then return only the data the browser needs. Keep the API base URL configurable for the connected environment. A public environment variable is bundled for browser use and must not contain a long-lived secret.
Review upgrades as contract changes
Compare the supplied contract and client release before updating a pinned version. Check response shapes, optional fields and error handling used by the application. Run a bounded read against the intended environment and inspect its source and receipt fields before enabling broader requests.
Keep generated types separate from runtime evidence
A typed response helps application code understand the contract but does not establish live coverage, source freshness or deployment status. Preserve missing values and validate inputs at your application boundary. Use the actual service response when showing current account state.