API DOCUMENTATION Last Update: July 2025

Delete a Depreciation

Removes a campaign depreciation entry from an account's campaign.

 

Headers

  Key   Value   Note
api_access_key user_api_key Optional

 

 

The data to be submitted to the API is composed of the following fields:

 

  field   Example   Note
user_id john1970 Required
user_password 1959caadac9b13dcb3 Required if not included in the headers
type depreciation_delete Required
account_id greatwidgets Required
campaign_id 1234567890123456 Required
depreciation_id 456 Required
Output Format:
output JSON or XML Optional. If not provided, defaults to XML
callback someFunctionName Optional: JSONP format
condensed yes Optional (No white space)
Applies only to JSON(P) output

 

Notes:

  • Headers: the user_api_key value can be included in either the header section or the body of the request. If the key is provided in both locations, the API will process and validate only the value provided in the headers.

  • The ability to delete depreciations is based on the permissions of the user_id that is making the call.
  • When identifying the depreciation to the API, you must use the <id> that is returned in the XML constructs, for example from the Campaign - List Depreciations call
  • Only one depreciation can be deleted at a time.

 

Example PHP Request:

If you are using PHP, the $data array would look like this:

  1. $data['user_id'] = 'john1970';
  2. $data['user_password'] = '1959caadac9b13dcb3';
  3. $data['type'] = 'depreciation_delete';
  4. $data['account_id'] = 'greatwidgets';
  5. $data['campaign_id'] = '1234567890123456';
  6. $data['fee_id'] = '456';

 

Success XML Response:

  1. <response status="success">
  2. <depreciation status="deleted">
  3. <id>456</id>
  4. </depreciation>
  5. </response>

 

Error XML Response:

  1. <response status="error">
  2. <error>Error message</error>
  3. </response>