Actions19
- Allocation Actions
- Application Actions
- Certificate Actions
- Eco Club Actions
- Flow Card Actions
- Impact Actions
- Notification Actions
- Utility Actions
Certificate → Get By App and External ID
AI-generatedOverview
This node operation retrieves a certificate from the dots.eco API using a combination of an external unique identifier and a numeric application ID. It is useful for scenarios where you need to fetch specific certificate data linked to an external system or application, ensuring precise lookup by these identifiers. For example, you might use this to verify or display certificate details associated with a particular order or app in an integrated environment.
Use Case Examples
- Retrieve a certificate by providing the external unique ID 'order-12345' and the corresponding app ID to fetch its details from dots.eco.
- Use the node to check if a certificate already exists for a given external ID and app before creating a new one.
Properties
| Name | Meaning |
|---|---|
| External Unique ID | External identifier used to deduplicate or retrieve certificates. Must be unique per app when creating a certificate. Reusing the same value returns a 422 error from the dots.eco API. |
| App ID | Numeric application ID used with the external unique ID lookup. Required to specify the app context for the certificate retrieval. |
Output
JSON
json- The JSON object representing the retrieved certificate data from the dots.eco API.
Dependencies
- Requires an API key credential for dots.eco API authentication.
Troubleshooting
- If the external unique ID is not unique per app, the API returns a 422 error indicating a duplicate entry. Ensure the externalUniqueId is unique for each app.
- If the app ID is missing or invalid, the request will fail. Provide a valid numeric app ID greater than zero.
- Network or authentication errors may occur if the API key credential is missing or incorrect. Verify the API credentials in the node settings.