Disabling the CyberApp

A callback handler must support a case when an MSP wants to disable the CyberApp. When MSP attempts to disable the CyberApp, Acronis Cyber Platform will send a POST request to the callback handler to remove the mapping for this MSP in the ISV’s service.

The callback request will:

  • Specify the cti.a.p.acgw.callback.v1.0~a.p.enablement.reset.v1.0 callback identifier.

  • Specify the cti.a.p.acgw.request.v1.0~a.p.empty.v1.0 callback request type.

  • Omit the payload field.

This request can be represented with the following cURL command:

curl -i -s -X POST <callback_handler_url> \
    --header 'Content-Type: application/json' \
    --header 'X-CyberApp-Auth: base64(<identity>:<secret>)' \
    --header 'X-CyberApp-Extra: base64(<json_extra_data>)' \
    --data '{"type": "cti.a.p.acgw.request.v1.0~a.p.empty.v1.0", "request_id": "<request_id>", "created_at": "2023-04-10T15:33:01+00:00", "context": {"callback_id": "cti.a.p.acgw.callback.v1.0~a.p.enablement.reset.v1.0", "endpoint_id": "<endpoint_id>", "tenant_id": "<acronis_tenant_id>", "datacenter_url": "<acronis_datacenter_url>"}}'

The callback response code must be 200 and the response body must:

  • Specify the cti.a.p.acgw.response.v1.0~a.p.success_no_content.v1.0 response type.

  • Omit the payload field.

HTTP/1.1 200 OK

    "type": "cti.a.p.acgw.response.v1.0~a.p.success_no_content.v1.0",
    "request_id": "<request_id>",
    "response_id": "<response_id>"