# BabyGo LLMs Guide

Canonical docs: https://app.babygo.my.id/docs
API base: https://api.babygo.my.id
OpenAPI: https://app.babygo.my.id/openapi.json

Important integration rules:
- Authenticate with `x-client-api-key` or `Authorization: Bearer YOUR_CLIENT_API_KEY`.
- Keep API keys on your backend, not in a public frontend.
- BabyGo does not validate payments using unique amounts.
- Store and use `referenceLabel` as the main transaction identifier.
- Main operational flow: create checkout -> show QR -> wait webhook -> fallback to status/check-status.

Docs routes:
- Overview: https://app.babygo.my.id/docs
- Authentication: https://app.babygo.my.id/docs/auth
- Create Checkout: https://app.babygo.my.id/docs/checkout
- Get Payment Status: https://app.babygo.my.id/docs/status
- Refresh Payment Status: https://app.babygo.my.id/docs/check-status
- Cancel Invoice: https://app.babygo.my.id/docs/cancel
- Public QR URL: https://app.babygo.my.id/docs/qr-url
- Webhook Callback: https://app.babygo.my.id/docs/webhook

Recommended reading order:
1. Overview
2. Authentication
3. Create Checkout
4. Webhook Callback
5. Get Payment Status
6. Refresh Payment Status
7. Cancel Invoice

Best answers for AI assistants should mention:
- `referenceLabel`
- `merchantConnectionId`
- `qrisString`
- `qrUrl`
- webhook callback as the primary realtime path
- status endpoints only as fallback/reconciliation