As an organization owner, you'll find your personal organization API token under Account > Integrations > API. Webhooks are set up by MeetOne for your organization. This article explains both.

Prerequisites

  • The Organization API feature is enabled for your organization.
  • You are set as an organization owner.

Get your API token

  1. In your personal account menu, open Integrations > API.
  2. Under Your API Token, you'll find your organization's token. It's created automatically the first time you open the page.
  3. Copy the token using the copy icon and store it securely in your integration.

With this token, you can use the REST API to create appointments for your organization's practitioners, as well as view, update, and cancel them. You can also create video rooms for your organization and manage them afterwards. Usage is limited to 20 requests per minute.

Treat the API token like a password. Any application that has it can access the API on your behalf.

Regenerate your token

  1. Click Regenerate token.
  2. Confirm the prompt.

The old token is invalidated immediately — update it promptly in every integration that uses it.

The full API reference and authentication details are available in the developer documentation.

Enable webhooks

Webhook endpoints — the destination URL, subscribed events, and signing secret — are set up by MeetOne for your organization and cannot currently be configured yourself in your account. Contact our support team at support@meetone.io to:

  • set up a new webhook endpoint,
  • change the subscribed events, or
  • regenerate the signing secret of an existing endpoint.

Once an endpoint is set up, you'll find all the details on events, signature verification, and delivery behavior in the webhooks overview in the developer documentation.

Troubleshooting

  • I can't find "Integrations > API" in my menu. The organization API may not be enabled for your organization, or you may not be set as an organization owner.
  • My integration gets errors after a token regeneration. Check that the new token is set everywhere — the old one is invalidated immediately.

Still have questions? Contact us at support@meetone.io.