Environments and Base URLs

OOLIN exposes HTTPS JSON APIs. BPMG provides the Base URL for each onboarding environment; do not append a trailing slash.

https://{environment-api-host}

Keep development, test, and production settings separate. Account IDs, asset IDs, network IDs, addresses, balances, and API credentials are environment-specific and must never be copied as if they were shared identifiers.

API environments and blockchain networks

Development, test, and production API environments are separate from a blockchain's mainnet/testnet classification. Select the network and asset agreed during onboarding rather than inferring the chain from a Base URL.

Supported Networks provides the mainnet/testnet catalog and customer-requested expansion guidance. The tutorials in these docs use the Ethereum Sepolia testnet.

Common rules

• Character encoding: UTF-8
• Date and time: UTC ISO 8601
• Amounts: decimal strings; *_raw fields are integer strings in the asset's smallest unit
• Response format: { success, data, error }

Use GET /health to confirm process reachability and GET /time to compare server time. The health response does not guarantee every database or blockchain dependency is available, so readiness checks should include a protected business API.

Configuration example

export WALLET_BASE_URL='https://{environment-api-host}'

Store the URL in environment configuration rather than application code. Apply TLS verification and explicit connection/read timeouts in every environment.

Environment readiness checklist

For each environment, record the Base URL, credential identifier, supported network, enabled asset, and operational contact. Do not store the secret value in the checklist.

Validate the following before running mutations:

• DNS and TLS verification succeed from the actual application network.
• /time differs from the caller clock by less than the authentication tolerance.
• A signed reference-data request succeeds with the intended credential.
• The required network, asset type, and asset combination are active.
• Your database can store 64-bit numeric IDs without truncation.
• UTC timestamps and decimal/raw amount strings survive serialization unchanged.

Treat HTTP 503 availability errors as scoped signals. A network or asset can be unavailable while the process health endpoint remains reachable.