Subscriptions

Webhook subscriptions let you receive real-time notifications when specific events occur on the platform.

A subscription defines:

  • The endpoint URL: The URL on your server where you want to receive the webhook events.
  • The event type: The specific type of event you want to be notified about. Event types follow a resource.action naming convention (for example, user.created, group.deleted).

When an event of the subscribed type occurs, a webhook event is automatically dispatched to your specified URL.

Manage your subscriptions

You can manage webhook subscriptions either via the API or through the 360Learning admin interface.

Via API

Using our API v2, you can:

📚

For full details on managing webhook subscriptions and available event types, see the Webhook API section in our main API Reference. This section is organized into:

  • Subscriptions: Provides all API endpoints for creating, retrieving, updating, and deleting subscriptions.
  • Events: Lists all specific event types available for subscription and their payload structures.

Via your 360Learning platform

If you prefer a visual interface, you can create, edit, and delete your webhooks directly within the 360Learning platform.

Access the Webhooks menu

  1. Log in ↗ to your 360Learning admin account.
  2. In the left sidebar, hover over the platform group and click Settings (gear icon).
  3. Click Webhooks.

Create a subscription

  1. At the top right, click Create subscription.
  2. Fill in the following details:
    • Subscription label: Choose a short, meaningful name to identify this webhook.
    • Subscription endpoint: Enter the URL that will receive the events.
    • Event: Select the specific event type from the dropdown.
  3. Click Confirm.

Edit a subscription

  1. Next to the subscription you wish to edit, click Edit (pen icon).
  2. Update the details.
  3. Click Confirm.

Delete a subscription

  1. Next to the subscription you wish to delete, click Delete (bin icon).
  2. Click Delete.

Subscription limits

To ensure stability and prevent misuse or human error, the following rules apply per company account:

  • Each subscription for a given event type must use a unique endpoint URL.
    • If you attempt to create a subscription where the event type and URL combination already exists, the API will return a 400 Bad Request with the error code subscriptionAlreadyExists.
  • You may create up to 3 subscriptions for the same event type.
    • If you attempt to create a fourth distinct subscription for the same event type (after already having 3 with different URLs), the API will return a 400 Bad Request with the error code subscriptionsLimitReached.
💡

Recommendation:

If you need to deliver the same event type to more than 3 destinations, we recommend using a single webhook subscription as an intermediate router. Your webhook handler can then forward events to multiple downstream systems as needed.