Straker Verify icon

Straker Verify

Interact with Straker Verify API
Join our community

Actions7

Overview

This node interacts with the Straker Verify API to manage API keys among other resources. Specifically, the Key - Delete operation deletes an existing API key by its ID. This is useful for revoking access or cleaning up unused keys in your Straker Verify account.

Typical use cases include:

  • Automating the removal of API keys that are no longer needed.
  • Managing API key lifecycle programmatically within workflows.
  • Enhancing security by deleting compromised or expired keys automatically.

Example: You have a workflow that audits API keys and deletes those inactive for a certain period by passing their Key IDs to this node's delete operation.

Properties

Name Meaning
Key ID The ID of the API key to delete

Output

The output JSON contains the response from the Straker Verify API after attempting to delete the specified API key. It typically includes a confirmation message or status indicating whether the deletion was successful.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "message": "API key deleted successfully"
}

Dependencies

  • Requires an API authentication token credential for the Straker Verify API.
  • The node makes HTTP DELETE requests to the endpoint ${environment}/key/{keyId}, where environment and apiKey come from the configured credentials.
  • Proper network connectivity to the Straker Verify API service is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Key ID parameter will cause the request to fail.
    • Insufficient permissions or invalid API key credential may result in authorization errors.
    • Network issues or incorrect environment URL configuration can cause request failures.

  • Error messages:

    • If the key does not exist or has already been deleted, the API might return a 404 or similar error.
    • Authorization errors if the API key credential is invalid or lacks delete permissions.
    • NodeOperationError thrown if the operation is unsupported or parameters are missing.

  • Resolution tips:

    • Ensure the Key ID is correct and corresponds to an existing API key.
    • Verify the API authentication token is valid and has appropriate permissions.
    • Check the environment URL and network connectivity.
    • Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.

Links and References

Discussion