VideoDB icon

VideoDB

Interact with the VideoDB API
Join our community

Actions37

Overview

This node integrates with the VideoDB API to manage video-related resources such as collections, videos, audios, and images. Specifically, the "Delete Image" operation allows users to delete an image from a specified collection in their VideoDB account. This is useful for maintaining or cleaning up media assets by removing outdated or unwanted images.

Practical examples include:

  • Automatically deleting images that are no longer relevant after a video update.
  • Managing image assets programmatically as part of a content pipeline.
  • Cleaning up storage by removing unused images from collections.

Properties

Name Meaning
Collection Name or ID Select or specify the collection from which the image will be deleted. Options are dynamically loaded from your VideoDB collections.
Image Name or ID Select or specify the image to delete within the chosen collection. Options are dynamically loaded based on the selected collection.

Output

The node outputs JSON data representing the response from the VideoDB API after attempting to delete the image. The structure typically contains confirmation of deletion or error details if the operation failed.

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "success": true,
  "message": "Image deleted successfully",
  "deletedImageId": "image_id_value"
}

Dependencies

  • Requires an API key credential for authenticating with the VideoDB API.
  • The base URL defaults to https://api.videodb.io but can be customized via credentials.
  • The node uses HTTP requests authenticated with the provided API key to interact with the VideoDB service.

Troubleshooting

  • Common issues:

    • Invalid or missing API key: Ensure the API key credential is correctly configured.
    • Specifying a non-existent collection or image ID: Verify that the collection and image exist and are correctly selected.
    • Network connectivity problems: Check internet connection and API endpoint accessibility.

  • Error messages:

    • Authentication errors (e.g., 401 Unauthorized): Confirm the API key is valid and has necessary permissions.
    • Not found errors (e.g., 404): The specified collection or image does not exist; double-check IDs.
    • Validation errors: Required parameters missing or invalid; ensure all required fields are filled.

Resolving these usually involves verifying credentials, input parameters, and network status.

Links and References

Discussion