Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Removes a specific subscription with the given ID at a data service provider. This method is possible on all subscriptions with status equal to active and results in their status being set to inactive such that they cannot be used. (see Lifecycle of a Subscription for more information)

Data service providers MUST support a DELETE call to a /subscriptions/{id} endpoint to remove a specific subscription

Request

Authorisation

The data service provider is responsible for determining a suitable authorisation policy for their subscriptions resources. See Autorisatie for more information.

Parameters

For information about the parameters that are common to the trust framework’s API’s see Generic API Requirements, and for parameters common to all subscriptions methods, see /subscriptions.

Data service providers MUST validate that the {id} of a DELETE request to a /subscriptions/{id} is valid, exists and is available to the data service consumer

Data service providers MUST validate that the subscription resource being deleted complies with their data service specific subscription requirements

Responses

200 OK

Successful, the subscription is deleted.

Data service providers MUST respond with a 200 OK to a successful DELETE call to a /subscriptions/{id} endpoint

Data service providers MUST NOT include an HTTP body in the response to a successful DELETE call to the /subscriptions/{id} endpoint

Data service providers MUST set the “status" of subscription/{id} to "inactive" in response to a successful DELETE call to the /subscriptions/{id} endpoint

404 Not found

Data service providers MUST respond with a 404 Not found to a DELETE call to a /subscriptions/{id} endpoint when the {id} is not a valid or available to the data service consumer

  • No labels