docs.neptlium.com

Build against governed financial state.

Neptlium Developers documents only contracts that exist or are explicitly labeled Beta or Planned. No speculative endpoint is represented as live.

Overview

Product-family boundaries, environments and shared API authority.

Available

Authentication

Customer and organization authentication boundaries.

Available

API

Shared api.neptlium.com contract and namespace conventions.

Available

Errors

Error shape, safe failure and retry expectations.

Available

Idempotency

Request identity and replay-safe command guidance.

Available

Webhooks

Signed provider ingress and replay-safe event handling.

Available

Payments

Business payment lifecycle. Execution is not production-supported yet.

Planned

Treasury

Capital and treasury projections that are already exposed safely.

Beta

Approvals

Organization approval contracts are not yet production-authoritative.

Planned

Reconciliation

Evidence, posting and reconciliation concepts.

Available

Audit

Append-only audit and activity semantics.

Beta

SDKs / Examples

Examples will publish only when stable contracts exist.

Planned

Shared API boundary

All customer and business products converge on api.neptlium.com. Phase A does not create separate VaultRail or Pay APIs.

GET /v1/account
GET /v1/capital
GET /v1/portfolio

# Business namespaces are documented only when implemented
/v1/organizations
/v1/treasury
/v1/payments
/v1/approvals

Production truth

Unknown is not zero. Provider observation is not canonical balance. Authorization is not execution. Submitted is not settled. Settled is not necessarily reconciled.