Straker Verify icon

Straker Verify

Interact with Straker Verify API

Actions8

Overview

This node interacts with the Straker Verify API to manage API keys among other resources. Specifically, for the Key - Create operation, it allows users to create a new API key by specifying a name and assigning a role to it. This is useful in scenarios where you want to programmatically generate API keys with specific permissions for accessing the Straker Verify platform.

Practical examples include:

  • Automating the creation of API keys for different team members or services.
  • Managing access control by assigning roles such as "Admin" or "User" when creating keys.
  • Integrating API key management into larger workflows that require dynamic credential provisioning.

Properties

Name Meaning
Name The name to assign to the new API key. This helps identify the key later.
Role The role assigned to the API key. Determines the permission level. Options are: "Admin" (full access) and "User" (limited access).

Output

The output JSON contains the response from the Straker Verify API after creating the API key. Typically, this will include details about the newly created key such as its identifier, name, role, and possibly the key string itself or metadata related to it.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "string",
  "name": "string",
  "role": "ADMIN" | "USER",
  "key": "string",
  "createdAt": "timestamp"
}

Dependencies

  • Requires an active connection to the Straker Verify API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the API can be customized but defaults to http://localhost:11001 if not set.

Troubleshooting

  • Common issues:

    • Missing required parameters ("Name" or "Role") will cause the request to fail.
    • Invalid or expired API authentication token will result in authorization errors.
    • Network connectivity problems to the Straker Verify API endpoint.

  • Error messages:

    • "Request failed with status code 4xx": Usually indicates client-side errors such as invalid input or unauthorized access. Verify the input parameters and API credentials.
    • "Request failed with status code 5xx": Indicates server-side issues; retry later or contact support.
    • "The operation 'create' is not supported for resource 'key'": Means the node configuration is incorrect; ensure the correct resource and operation are selected.

To resolve errors:

  • Double-check that all required properties are provided.
  • Confirm the API key credential is valid and has sufficient permissions.
  • Ensure the API endpoint URL is reachable from your environment.

Links and References

Discussion