DuitMyself Public API
The DuitMyself Public API gives Pro users a predictable REST surface for accounts, transactions, categories, payees, and subject metadata.
Stable REST API for bookkeeping, sync, and agents
Production host: https://api.duitmyself.app. Start with Quickstart for a first successful
request, then move into concepts and resource reference as your integration grows.
QuickstartMake a first read request, bootstrap context, and send a safe write.AuthenticationLearn key lifecycle, bearer auth, scopes, and response headers.Safe writesUse idempotency keys and upserts correctly so retries never duplicate data.API referenceJump straight into resource-specific endpoints, examples, and schemas.
First request
Section titled “First request” curl "https://api.duitmyself.app/v1/me" \
-H "Authorization: Bearer key_..."
Choose your integration surface
Section titled “Choose your integration surface”Raw HTTPBest when you want direct control over requests, retries, and response handling.OpenAPIUse the published schema for generated clients, collections, or internal tooling.MCP serverConnect MCP-capable agents over stdio with first-party tools and resources.
What v1 includes
Section titled “What v1 includes”- Profile and bootstrap endpoints for the authenticated subject.
- Resource endpoints for accounts, transactions, categories, and payees.
- Idempotent write flows for
POSTandPATCH. externalId-based upsert endpoints for sync-safe integrations and agents.- A published OpenAPI document at
/openapi.json. - A first-party MCP bridge for agent tooling.
Delegated and team-style access is not public in v1, but the authorization model is built with enough separation between the key owner and the data subject to support that later without replacing the route contract.