Your purchases, remembered.
ReturnDocket stores confirmed return dates and refund status. You can use the account page directly or connect the API to a compatible Muse account.
1. Create your invitation account
Open Your account with your beta invite code. Save the recovery key in a password manager. The service does not collect your email; losing the key means we cannot restore your access.
2. Connect to Muse
In Muse’s custom connector or secure credentials setup, use the API address below and the connector key as a Bearer credential. Keep your recovery key private; never give it to a connector. The exact setup labels can vary with Muse access. Directory approval is pending.
API: https://returndocket.bergapp.net/api OpenAPI: https://returndocket.bergapp.net/openapi.json Authorization: Bearer YOUR_CONNECTOR_KEY
The connector key expires after 90 days. Replace or revoke it in your account whenever you need. Replacement disconnects the old key immediately.
3. Save one real purchase
“Track my $68 overshirt from Example Store, bought September 20, 2026. My receipt says return by October 20, 2026.” Muse should ask for any missing date or source instead of guessing from a store name.
4. Review and close the loop
“What needs attention as of September 25?” returns upcoming, overdue and pending-refund records. Say “I returned it” when that happens and confirm the actual refund amount later. Reported refund totals are not a claim of savings caused by this service.
Calendar export
Your account can export an ICS file with all open deadlines. Import it into your own calendar and choose your calendar’s reminder settings. The export is a snapshot, not a subscription; later changes require a new export. Avoid importing repeated snapshots if your calendar duplicates entries.
API behavior
Dates are exact YYYY-MM-DD calendar dates from 2000–2099, USD amounts are integer cents, and merchant eligibility is never inferred. Every create/update needs a unique Idempotency-Key reused for retries. Updates also need the current version. Retry conflicting edits after reading the latest record. Retried writes are retained for 30 days; deleting a record tombstones its replay response. Account management endpoints require the recovery key and are intentionally excluded from the connector schema.