The Mouve API is in active development and not yet live. Follow the changelog for the launch announcement.

Mouve Developers

Developer terms

The legal frame for building on the Mouve API — obligations summary and where the binding documents live.

Summary, not the contract

This page summarizes the developer legal package so you know what you are agreeing to before you build. The binding documents are the versioned texts at the URLs below, which publish together with the API launch. Where this summary and the binding text differ, the binding text wins.

The documents

DocumentWhereWho accepts it
Developer Termsmouve.it/legal/developer-termsYou, when creating an app or token
Connected Apps & API Termsmouve.it/legal/connected-apps-termsUsers, when connecting an app
Connected Apps Privacy Noticemouve.it/legal/connected-apps-privacyShown to users at consent
Mouve Terms of Servicemouve.it/legal/termsEvery Mouve user

Acceptance of the Developer Terms is recorded at app creation (clickwrap). The controller is Mouve Technology OÜ (Tallinn, Estonia); governing law is Estonian, venue Harju County.

What you commit to (the short version)

Data handling

  • Use user data only for the purpose the user connected your app for.
  • Delete a user's data within 30 days of grant revocation, an erasure notice, or Mouve's request. You act as an independent controller for data you receive — with contractual purpose and deletion limits.
  • Notify Mouve of a personal-data breach affecting Mouve-sourced data within 72 hours.
  • Never sell user data, use it for advertising, eligibility decisions, or surveillance, and never train AI models on it without the user's separate, explicit consent.

Health data (scopes marked in the catalog) carries a stricter floor: explicit consent recorded per grant, a published privacy policy on your app, and no processing beyond the consented purpose — ever.

Conduct

  • Automation touches Mouve only through this API with issued credentials, within granted scopes and published limits. Scraping is prohibited — including of publicly viewable content.
  • Label automated content honestly; API-created posts carry your app's provenance (app_id) and are treated as the user's content under the Terms of Service.
  • Respect Mouve's branding rules; do not present an unverified app as official.

Lifecycle

  • Mouve can suspend or take down an app that breaks these rules, with a cure process for good-faith issues; user grants for a restored app require re-consent.
  • Material changes to the developer documents are announced at least 30 days ahead (see the changelog); limits themselves live in the docs and may be tuned with changelog notice.

Rate limits and numbers

The legal documents deliberately contain no enforcement numbers. Limits, quotas, and windows are published only in rate limits and reported live in response headers — one source of truth that cannot drift from enforcement.