> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/advanced-and-api/api-reference/scrobbling-and-webhooks.md).

# Scrobbling and webhooks

Use these endpoints for real-time playback processing.

### Scrobbler configuration

| Method   | Endpoint                                     | Purpose                                               |
| -------- | -------------------------------------------- | ----------------------------------------------------- |
| `GET`    | `/api/scrobbler/overview`                    | Return sources, routes, profiles, and generated URLs. |
| `POST`   | `/api/scrobbler/webhooks/profile`            | Create or update a profile webhook.                   |
| `POST`   | `/api/scrobbler/webhooks/profile/disable`    | Disable or remove a profile webhook.                  |
| `POST`   | `/api/scrobbler/webhooks/profile/regenerate` | Regenerate a webhook token.                           |
| `POST`   | `/api/scrobbler/routes`                      | Create a Watcher route.                               |
| `PUT`    | `/api/scrobbler/routes/{route_id}`           | Update a route.                                       |
| `DELETE` | `/api/scrobbler/routes/{route_id}`           | Delete a route.                                       |
| `POST`   | `/api/scrobbler/settings`                    | Save global scrobbler settings.                       |

Use the generated URLs. Do not construct webhook tokens manually.

### Watcher runtime

| Method | Endpoint                        | Purpose                               |
| ------ | ------------------------------- | ------------------------------------- |
| `GET`  | `/api/watch/status`             | Return Watcher route and group state. |
| `GET`  | `/api/watch/currently_watching` | Return active playback streams.       |
| `GET`  | `/api/watch/logs`               | Return selected Watcher logs.         |
| `POST` | `/api/watch/start`              | Start configured routes.              |
| `POST` | `/api/watch/stop`               | Stop all routes.                      |
| `POST` | `/api/watch/refresh`            | Reload route configuration.           |

### Inbound webhooks

| Method | Endpoint               | Source              |
| ------ | ---------------------- | ------------------- |
| `POST` | `/webhook/plex`        | Plex playback.      |
| `POST` | `/webhook/jellyfin`    | Jellyfin playback.  |
| `POST` | `/webhook/emby`        | Emby playback.      |
| `POST` | `/webhook/plexwatcher` | Plex rating events. |

Webhook handlers often acknowledge events with HTTP `200`, including ignored events. Inspect the JSON body for the processing result.

Legacy aliases remain available at `/webhook/plextrakt`, `/webhook/jellyfintrakt`, and `/webhook/embytrakt`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.crosswatch.app/crosswatch/advanced-and-api/api-reference/scrobbling-and-webhooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.