Dots-Eco icon

Dots-Eco

Fetch a specific resource from a Dots eco API
Join our community

Actions4

Overview

This node interacts with the Dots eco API to fetch a single certificate by its ID. It is useful when you need to retrieve detailed information about a specific certificate that was previously issued or listed. Common scenarios include verifying certificate details, displaying certificate information in dashboards, or integrating certificate data into other workflows.

For example, after obtaining a list of certificates, you can use this node to fetch full details of one particular certificate by providing its unique Certificate ID.

Properties

Name Meaning
Certificate ID The unique identifier of the certificate you want to fetch. This ID can be obtained from certificate list responses or certificate request responses.

Output

The node outputs a JSON object representing the fetched certificate's details as returned by the Dots eco API. This typically includes all relevant certificate fields such as issuance data, associated allocation, user info, and any metadata provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Dots eco API.
  • Requires credentials configured with:
    • A base URL for the Dots eco API.
    • An API authentication token or key (configured in n8n credentials).
  • The node uses authenticated HTTP GET requests to fetch certificate data.

Troubleshooting

  • Missing or empty API base URL:
    Error message: "Please add API base url under the Credentials for Dots eco API."
    Resolution: Ensure the API base URL is correctly set in the node’s credentials configuration.

  • Invalid or missing Certificate ID:
    If the Certificate ID parameter is empty or incorrect, the API may return an error or no data.
    Resolution: Verify that the Certificate ID is correct and corresponds to an existing certificate.

  • Authentication errors:
    If the API key or token is invalid or expired, the request will fail.
    Resolution: Check and update the API credentials in n8n.

  • Network or API availability issues:
    Network failures or API downtime will cause request failures.
    Resolution: Confirm network connectivity and API service status.

Links and References

Discussion