Since couple days, when trying tyo add or modify an existing API Request node, I am getting an error nodes.tool.server.credentialld must be a UUID. Seems a bug to me as everything worked flawless before

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

To resolve the error, ensure your API Request node's

server.credentialId

is set to a valid UUID. For example:

json
"server": {
  "timeoutSeconds": 20,
  "credentialId": "550e8400-e29b-41d4-a716-446655440000",
  "url": "https://your-api-endpoint.com",
  "headers": {}
}

Double-check that your

credentialId

matches the required UUID format as shown above (according to the documentation I have found: [Vapi API Reference](https://docs.vapi.ai/api-reference/webhooks/server-message)). Source: - [Vapi API Reference: Webhooks Server Message](https://docs.vapi.ai/api-reference/webhooks/server-message)

This error happens because Vapi recently updated how API Request nodes validate credentials, and now the field tool_serverCredentialId must contain a valid UUID instead of older or blank values. When you try to add or edit an API Request node that was created before this change, the system flags it as invalid and throws the error. To fix it, you need to open your tool’s settings and either re-select your server credential or create a new one so Vapi can assign a fresh UUID. After updating the credential, the API Request node should save normally again. If the issue still persists, contacting Vapi support with the workflow ID helps them patch the bug on their side.

It is an outgoing unauthenticated API call to a test webhook. I do not think anything on my end. Tried the above and no change. Seems a general bug on their end. How do I reach out to the support. Btw many users are complaining about this for days now

Hi Andy, This issue occurs due to a recent update in Vapi’s validation for API Request nodes, where

server.credentialId

must now be a valid UUID. To resolve this, you will need to update your tool's settings: 1. Re-select your server credential or create a new one in the Vapi dashboard. 2. Ensure the

credentialId

is correctly set to a valid UUID. You can find this by navigating to your Vapi dashboard and copying the UUID from your credentials. Here's an example setting:

json
"server": {
  "timeoutSeconds": 20,
  "credentialId": "550e8400-e29b-41d4-a716-446655440000",
  "url": "https://your-api-endpoint.com",
  "headers": {}
}

If you continue experiencing issues, it may help to report your workflow ID to Vapi support to assist them in patching any remaining bugs. You can also check the [Vapi API Reference](https://docs.vapi.ai/api-reference/webhooks/server-message) for more details.