Delete a Subscription — Guide

First-request guide for Delete a Subscription.

API GUIDE

Delete a Subscription

Delete a Subscription

DELETE/subscriptions/{subscriptionId}No request bodyAuthentication required

Overview

Permanently delete a subscription using its subscription ID. This operation removes the subscription from the system and halts all future notifications or alerts related to it.

Call the endpoint

Send a DELETE request to /subscriptions/{subscriptionId} with the required authentication and parameters.

Supply endpoint parameters

Review the parameter table to see which path, query, or header values the endpoint accepts.

Inspect the response

Use the success response shape to validate the fields your integration receives.

Quickstart

Follow these two steps to make a request and recognize a successful response.

STEP 1

Make a request

REQUEST
curl --request DELETE \
  --url https://uapi.demandbase.com/data/b2b/v1/subscriptions/287ea0c8-99de-4f0c-addc-097f78b48ba6 \
  --header "Authorization: Bearer $DB_API_KEY" \
  --header "Accept: application/json"
STEP 2

Read the response

SUCCESS RESPONSE · HTTP 200
{
  "subscriptionId": "63914a27-a5ca-4fdf-80b0-ffc985f53c14",
  "message": "Subscription deleted successfully"
}

Request anatomy

Build the request from the method, path, parameters, and payload described below.

Parameters

NameLocationTypeRequiredDescription
subscriptionIdpathstringRequiredUnique identifier for the subscription

Request body

This endpoint does not define a JSON request body.

Response anatomy

The endpoint returns 200 for the documented success case. Subscription was deleted successfully.

The response schema does not enumerate fields; inspect the example response and status code.

Rules

  • Use DELETE with the path /subscriptions/{subscriptionId}.
  • Required inputs: subscriptionId.
  • Authenticate every request with a valid Demandbase access token.
  • This endpoint does not require a JSON request body.

Filters

The published schema exposes the following endpoint inputs. Use the location column to place each value correctly.

NameLocationTypeRequiredDescription
subscriptionIdpathstringRequiredUnique identifier for the subscription

Errors

Handle non-success responses explicitly so your integration can report actionable failures.

StatusMeaning
401Unauthorized. The request lacks valid authentication credentials.
404Subscription not found or already deleted.

Next steps

Try the quickstart

Start with the request example, then replace the sample values with your credentials and data.

Return to the API area

Back to subscription-api

Back to top