Skip to content
Learn › Share and export › Live links: open the docs menu

Manage a Mammoth live link over the API

Team and Pro · Reading needs access to the View; changing settings, reading the key or rotating needs permission to set up the View's exports · Updated 8 Nov 2026

Everything in a Live Link's settings is also an API route. Reading the settings and the fetch history needs access to the View. Changing the settings, reading the full key or rotating it needs permission to set up the View's exports. Each route takes an API token as Authorization: Bearer mm_....

The routes hang off the Live link task's export:

/api/v2/workspaces/<workspace_id>/projects/<project_id>/datasets/<dataset_id>/dataviews/<dataview_id>/pipeline/exports/<export_id>/live-link
RouteWhat it does
GET .../live-linkThe settings: url, access (open or key), key_hint, expires_at, ended, enabled, the address before the last rotate and when it stops, the last fetch, and fetches_7d / refused_7d
PATCH .../live-linkChange access, expires_at (UTC) or clear_expiry, enabled, or new_key: true (the old key stops at once)
GET .../live-link/keyThe full key and url_with_key. Not found for a link without a key
POST .../live-link/rotateA new address (and a new key for a key link). keep_old_for is none (the default), day or week
GET .../live-link/fetchesUp to the 200 most recent fetches in the last 30 days, newest first: fetched_at, tool, country (when known), result (sent, wrong_key, ended, off or not_ready) and via_previous (fetched through the address before a rotate)
curl -X PATCH -H "Authorization: Bearer $MAMMOTH_API_TOKEN" -H "Content-Type: application/json" \
  -d '{"enabled": false}' \
  "https://app.mammoth.io/api/v2/workspaces/<workspace_id>/projects/<project_id>/datasets/<dataset_id>/dataviews/<dataview_id>/pipeline/exports/<export_id>/live-link"

On an old public-file link, a PATCH or a rotate first gives it a Mammoth address. Its public file keeps working for keep_old_for.

Was this page helpful?

Something wrong? support@mammoth.io