dimesumdevelopers API reference Console Open the app

Security and privacy

A key can do what you can do, so the rules around keys are strict, and some things are never reachable with one.

How keys are kept#

  • Shown once, stored as a hash. When you make or regenerate a key, the app shows the secret once. Dimesum stores only its SHA-256 hash, so nobody at Dimesum, and nobody who reads the database, can recover your key.
  • Managed only from a signed-in session. Making, regenerating, switching off and deleting keys happens in the app. A key can never make, widen or read a key.
  • Stops at once. Regenerating or deleting a key makes the old secret fail from the next request; switching it off does the same until you switch it on.
  • Recognisable. Keys start with dms_live_, so secret scanners can flag one committed to a repository.

Every request is logged for you#

Each request a key makes is recorded for the key's owner: the time, the method, the path, the status and how long it took. Capability tokens that appear in a path are masked before the path is stored. You can read the log in the app, from GET /v1/developer/key, or in the console, and spot anything you did not do.

What the API never exposes#

  • Sign-in tokens and sessions. No route returns one, and a key cannot sign in as you.
  • Account deletion, your profile, your sign-in methods and your payment details. These are app-only (why).
  • Other people's payment details beyond what the app shows members. A group's member list includes the ways its members have chosen to be paid, exactly as the app shows them to fellow members. Nothing more, and never for people outside your groups.
  • Groups you are not in. They answer 404 not_found, the same as a group that does not exist.
  • Keys: not yours, not anyone's. GET /v1/developer/key returns the calling key's metadata, never a secret.

The console and this site#

The console runs in your browser and sends requests straight to the API. Your key stays in the page's memory, or in the tab's sessionStorage if you ask it to, and is never written to localStorage, cookies or any server of ours. The API accepts browser requests only from https://developers.dimesum.com (and http://localhost:4600 in development), and never with cookies.

Data handling#

The API reads and writes the same data the app does, under the same privacy policy. Text you send to POST /v1/captures is read by Dimesum's parser; phone numbers, email addresses and UPI ids are masked before it reaches the language model. Dimesum never holds or moves money: recording a payment is a statement, which the other person confirms or disputes.

Reporting a vulnerability#

Email security@dimesum.com with what you found, how to reproduce it and what it lets someone do. Please:

  • Test only against your own account and groups you own, and never read, change or delete other people's data.
  • Give us a reasonable time to fix it before you tell anyone else.
  • Stop and tell us if you reach data that is not yours.

We will confirm we have your report, keep you told how the fix is going, and credit you if you want to be credited.