Documentation

Keely for developers

Get access.

A Keely account, a registered app, your own account to build against, and Keely’s approval before anyone else can connect.

Updated

On this page
  1. Four steps
  2. Test data
  3. The portal

Four steps

  1. Create a Keely account in the Keely app, with the email you’ll use as a developer. There’s no separate developer account.
  2. Register your app at meetkeely.com/developers/apps: its name, what it does, its website, its redirect URIs, whether it keeps a secret, and the permissions it asks for, each with one line on why, which the person reads on the consent page. Registering accepts the rules for apps.
  3. Connect your own account. A new app is awaiting approval. Until it’s approved, only you, its developer, can connect, so you can build and test against your own data.
  4. Wait for approval. Keely approves apps one by one, by hand, and writes to the email on your account. Once approved, anyone with a Keely account can connect your app.

Test data

A developer without a Polar Loop has no data of their own to read. A sandbox account with sample data is coming; until then, your own band is the test data.

The portal

meetkeely.com/developers/apps is where your apps live. You sign in with the email on your Keely account, and for each app you can:

  • Register it: its name, what it does, its website, its redirect URIs (up to 10; a native app may use its own scheme or http://127.0.0.1 with a port), whether it’s a confidential or a public client, and the permissions it asks for, with a line on why for each.
  • Copy its client ID, and its client secret, which is shown once: Keely never stores it. If you lose it, remove the app and register it again.
  • See its status: awaiting approval, approved, or suspended.
  • Add its webhook subscriptions, send each a test, pause or delete them, and read their recent deliveries. Webhooks has the details.
  • Remove it, which ends every connection people made to it.