Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Articulate connector page.How webhooks are set up
Reach 360 delivers events through a webhook subscription, and StackOne provisions it for you on connection. When you connect your account, StackOne creates one Reach 360 webhook (POST /webhooks) pointing at a StackOne callback URL, subscribed to the events you enable. When you disconnect, StackOne deletes that webhook (DELETE /webhooks/{id}). There is nothing to configure in Reach 360.
Connect with your API key
Authorize the connection with your Reach 360 API Key and Region so StackOne can create and delete the webhook subscription on your behalf. No further setup is needed in Reach 360.
Enable the events you need
Enable the Reach 360 events you want in StackOne. StackOne subscribes the webhook to exactly those event types and dispatches each delivery onward.
Available webhook events
The following Reach 360 events can be enabled. Only events selected in StackOne are included in the subscription — Reach 360 will not deliver events that are not subscribed.
Course events
Events related to courses.
- Course Completed (
course.completed) — Fired when a learner completes a course. - Course Submitted (
course.submitted) — Fired when an author submits a course to be reviewed by an admin for publication.
Enrollment events
Events related to course and learning path enrollments.
- Enrollments Created (
enrollments.created) — Fired when users or groups are enrolled in a course or a learning path.
User events
Events related to account users.
- User Created (
user.created) — Fired when a user is added to your Reach 360 account.
Delivery format
Details of how Reach 360 delivers events to StackOne.
Single JSON object
Each delivery is a single JSON object (not batched) with top-level id (unique event id), createdAt (timestamp), type (the event type), webhookId, apiVersion, and a data object with the event-specific content. Reach 360 retries a non-200 response up to 14 more times over the next 48 hours.
Optional signature
If a signing secret is set on the subscription, Reach 360 adds an X-Hook-Signature header (an HMAC-SHA1 digest of the request body). StackOne routes each delivery to its matching event handler.