{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "item": { "id": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "slug": "remove-one-axis-data-hub-subscription-without-stopping-the-others", "url": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others.md", "json": "https://update.dsesecurity.com/api/v1/posts/remove-one-axis-data-hub-subscription-without-stopping-the-others/" }, "title": "Remove one Axis Data Hub subscription without stopping the others", "summary": "Retain each Axis Data Hub subscription ID and remove only the intended subscription. Verify that other required subscriptions continue in the same session.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-29T19:50:03+00:00", "modified_at": "2026-10-29T19:50:07+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 507, "potentially_affected": "Axis products exposing the documented Device Data Hub WebSocket API interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends keeping a subscription registry in the client and verifying retained subscriptions during an individual removal.", "primary_source": { "name": "Axis Communications — Device Data Hub WebSocket API", "url": "https://developer.axis.com/vapix/device-data-hub/websocket/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Retire a Data Hub subscription by its recorded identifier. Keep the remaining subscriptions explicit so removing one consumer’s data selection does not become an unexplained shutdown of the entire shared connection.

\n

Source fact: documented behavior

\n

Axis’s Device Data Hub WebSocket API supports several subscriptions in one session, with separate filters and a distinct subscriptionId for each.

\n

The documented unsubscribe operation removes the subscription named by its ID; the other subscriptions on that connection continue operating.

\n

A topicSample notification identifies its subscription and topic and includes sample data and a timestamp.

\n

What the source does not establish

\n

Do not infer missed-sample recovery or application-level continuity from this removal behavior. Keep a session-close or reconnect procedure separate from removing one subscription. Confirm the device’s interface support and the actual client’s subscription handling before sharing a connection between operational consumers.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends keeping a subscription registry in the client and verifying retained subscriptions during an individual removal.

\n
    \n
  1. List the intended consumers and assign each an identifiable subscription record in the integration. Preserve the ID returned or accepted by the documented workflow with its filter and owning component. Avoid choosing a removal target from a topic name alone when the design permits several filtered subscriptions. Record which consumers are deliberately unaffected by the requested retirement.
    2. \n
  2. Prepare a proposed pilot with two harmless supported topic selections and distinct subscription IDs. Label the selections as fixtures rather than actual site requirements. Establish each subscription through the supported interface and capture permitted sample observations before removal. Keep the connection and each subscription’s state as separate entries in the client’s diagnostic record.
    3. \n
  3. Remove only the selected ID and retain the operation outcome. Check the remaining subscription with an appropriate approved input and reconcile its sample identifier with the registry. If the client closes the session or loses another required subscription, treat that as an integration result to investigate. Restore the approved arrangement before expanding the change to operational consumers.
    4. \n
\n

Verification and evidence

\n

Retain the session identity, sanitized subscription definitions, selected removal ID, response and before-and-after sample observations. Have another reviewer match each observed sample to its intended subscription. Exclude credentials and unnecessary payload content from shared diagnostic records.

\n

For the proposed exercise, include a client-side selection review in which the wrong ID belongs to the consumer that must remain. Require the operator to reject that removal before sending it. Record actual results after execution; this article does not report a completed subscription test or guarantee that an application received every sample.

\n

Official references

\n\n

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.

\n", "content_text": "Bottom line: Retire a Data Hub subscription by its recorded identifier. Keep the remaining subscriptions explicit so removing one consumer’s data selection does not become an unexplained shutdown of the entire shared connection.\nSource fact: documented behavior\nAxis’s Device Data Hub WebSocket API supports several subscriptions in one session, with separate filters and a distinct subscriptionId for each.\nThe documented unsubscribe operation removes the subscription named by its ID; the other subscriptions on that connection continue operating.\nA topicSample notification identifies its subscription and topic and includes sample data and a timestamp.\nWhat the source does not establish\nDo not infer missed-sample recovery or application-level continuity from this removal behavior. Keep a session-close or reconnect procedure separate from removing one subscription. Confirm the device’s interface support and the actual client’s subscription handling before sharing a connection between operational consumers.\nApplicability questions\n\nWhich component owns each subscription identifier?\nWhich topic and filter selection belongs to the subscription being retired?\nWhich other subscriptions must remain on the same session?\nWhat permitted sample will demonstrate each retained consumer’s required data path?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends keeping a subscription registry in the client and verifying retained subscriptions during an individual removal.\n\nList the intended consumers and assign each an identifiable subscription record in the integration. Preserve the ID returned or accepted by the documented workflow with its filter and owning component. Avoid choosing a removal target from a topic name alone when the design permits several filtered subscriptions. Record which consumers are deliberately unaffected by the requested retirement.\nPrepare a proposed pilot with two harmless supported topic selections and distinct subscription IDs. Label the selections as fixtures rather than actual site requirements. Establish each subscription through the supported interface and capture permitted sample observations before removal. Keep the connection and each subscription’s state as separate entries in the client’s diagnostic record.\nRemove only the selected ID and retain the operation outcome. Check the remaining subscription with an appropriate approved input and reconcile its sample identifier with the registry. If the client closes the session or loses another required subscription, treat that as an integration result to investigate. Restore the approved arrangement before expanding the change to operational consumers.\n\nVerification and evidence\nRetain the session identity, sanitized subscription definitions, selected removal ID, response and before-and-after sample observations. Have another reviewer match each observed sample to its intended subscription. Exclude credentials and unnecessary payload content from shared diagnostic records.\nFor the proposed exercise, include a client-side selection review in which the wrong ID belongs to the consumer that must remain. Require the operator to reject that removal before sending it. Record actual results after execution; this article does not report a completed subscription test or guarantee that an application received every sample.\nOfficial references\n\nDevice Data Hub WebSocket API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "content_markdown": "Bottom line: Retire a Data Hub subscription by its recorded identifier. Keep the remaining subscriptions explicit so removing one consumer’s data selection does not become an unexplained shutdown of the entire shared connection.\n\n## Source fact: documented behavior\n\nAxis’s [Device Data Hub WebSocket API](https://developer.axis.com/vapix/device-data-hub/websocket/) supports several subscriptions in one session, with separate filters and a distinct subscriptionId for each.\n\nThe documented unsubscribe operation removes the subscription named by its ID; the other subscriptions on that connection continue operating.\n\nA topicSample notification identifies its subscription and topic and includes sample data and a timestamp.\n\n## What the source does not establish\n\nDo not infer missed-sample recovery or application-level continuity from this removal behavior. Keep a session-close or reconnect procedure separate from removing one subscription. Confirm the device’s interface support and the actual client’s subscription handling before sharing a connection between operational consumers.\n\n## Applicability questions\n\n- Which component owns each subscription identifier?\n\n- Which topic and filter selection belongs to the subscription being retired?\n\n- Which other subscriptions must remain on the same session?\n\n- What permitted sample will demonstrate each retained consumer’s required data path?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends keeping a subscription registry in the client and verifying retained subscriptions during an individual removal.\n\n- List the intended consumers and assign each an identifiable subscription record in the integration. Preserve the ID returned or accepted by the documented workflow with its filter and owning component. Avoid choosing a removal target from a topic name alone when the design permits several filtered subscriptions. Record which consumers are deliberately unaffected by the requested retirement.\n\n- Prepare a proposed pilot with two harmless supported topic selections and distinct subscription IDs. Label the selections as fixtures rather than actual site requirements. Establish each subscription through the supported interface and capture permitted sample observations before removal. Keep the connection and each subscription’s state as separate entries in the client’s diagnostic record.\n\n- Remove only the selected ID and retain the operation outcome. Check the remaining subscription with an appropriate approved input and reconcile its sample identifier with the registry. If the client closes the session or loses another required subscription, treat that as an integration result to investigate. Restore the approved arrangement before expanding the change to operational consumers.\n\n## Verification and evidence\n\nRetain the session identity, sanitized subscription definitions, selected removal ID, response and before-and-after sample observations. Have another reviewer match each observed sample to its intended subscription. Exclude credentials and unnecessary payload content from shared diagnostic records.\n\nFor the proposed exercise, include a client-side selection review in which the wrong ID belongs to the consumer that must remain. Require the operator to reject that removal before sending it. Record actual results after execution; this article does not report a completed subscription test or guarantee that an application received every sample.\n\n## Official references\n\n- [Device Data Hub WebSocket API](https://developer.axis.com/vapix/device-data-hub/websocket/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "url": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Remove one Axis Data Hub subscription without stopping the others", "item": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/#article", "identifier": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "url": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/", "headline": "Remove one Axis Data Hub subscription without stopping the others", "description": "Retain each Axis Data Hub subscription ID and remove only the intended subscription. Verify that other required subscriptions continue in the same session.", "abstract": "Retain each Axis Data Hub subscription ID and remove only the intended subscription. Verify that other required subscriptions continue in the same session.", "articleBody": "Bottom line: Retire a Data Hub subscription by its recorded identifier. Keep the remaining subscriptions explicit so removing one consumer’s data selection does not become an unexplained shutdown of the entire shared connection.\nSource fact: documented behavior\nAxis’s Device Data Hub WebSocket API supports several subscriptions in one session, with separate filters and a distinct subscriptionId for each.\nThe documented unsubscribe operation removes the subscription named by its ID; the other subscriptions on that connection continue operating.\nA topicSample notification identifies its subscription and topic and includes sample data and a timestamp.\nWhat the source does not establish\nDo not infer missed-sample recovery or application-level continuity from this removal behavior. Keep a session-close or reconnect procedure separate from removing one subscription. Confirm the device’s interface support and the actual client’s subscription handling before sharing a connection between operational consumers.\nApplicability questions\n\nWhich component owns each subscription identifier?\nWhich topic and filter selection belongs to the subscription being retired?\nWhich other subscriptions must remain on the same session?\nWhat permitted sample will demonstrate each retained consumer’s required data path?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends keeping a subscription registry in the client and verifying retained subscriptions during an individual removal.\n\nList the intended consumers and assign each an identifiable subscription record in the integration. Preserve the ID returned or accepted by the documented workflow with its filter and owning component. Avoid choosing a removal target from a topic name alone when the design permits several filtered subscriptions. Record which consumers are deliberately unaffected by the requested retirement.\nPrepare a proposed pilot with two harmless supported topic selections and distinct subscription IDs. Label the selections as fixtures rather than actual site requirements. Establish each subscription through the supported interface and capture permitted sample observations before removal. Keep the connection and each subscription’s state as separate entries in the client’s diagnostic record.\nRemove only the selected ID and retain the operation outcome. Check the remaining subscription with an appropriate approved input and reconcile its sample identifier with the registry. If the client closes the session or loses another required subscription, treat that as an integration result to investigate. Restore the approved arrangement before expanding the change to operational consumers.\n\nVerification and evidence\nRetain the session identity, sanitized subscription definitions, selected removal ID, response and before-and-after sample observations. Have another reviewer match each observed sample to its intended subscription. Exclude credentials and unnecessary payload content from shared diagnostic records.\nFor the proposed exercise, include a client-side selection review in which the wrong ID belongs to the consumer that must remain. Require the operator to reject that removal before sending it. Record actual results after execution; this article does not report a completed subscription test or guarantee that an application received every sample.\nOfficial references\n\nDevice Data Hub WebSocket API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "datePublished": "2026-10-29T19:50:03+00:00", "dateModified": "2026-10-29T19:50:07+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/remove-one-axis-data-hub-subscription-without-stopping-the-others/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Remove one Axis Data Hub subscription without stopping the others" }, "articleSection": [ "IT", "Video Surveillance" ], "keywords": [ "IT", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 507, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Device Data Hub WebSocket API", "url": "https://developer.axis.com/vapix/device-data-hub/websocket/" } } ] } }