API call failed

This Error Event is part of Universal Web API Call Events.

Event ID · 600400

"API call failed for URL with error"

Overview

The API call failed Error Event indicates that the Universal Web API Call could not complete the requested operation. The Event message provides the underlying error and usually identifies the stage that failed, such as URL processing, connection setup, TLS or certificate validation, OAuth 2.0 authentication, file handling, or the server response.

Similar errors can occur in other Web and Internet Actions because they share many of the same web communication components and settings.

Event examples

The API call failed Event can be caused by many different network, security, authentication, file, and server conditions. The examples below are grouped by type. The list is not exhaustive, and the exact error message can vary depending on the failing component…

General & connections

URL, DNS, redirects, timeouts, cancellation, and other general request or connection failures.

These errors usually mean the request never reached the server, or the connection broke before a response arrived. If the message mentions a bad or illegal URL format or a bad hostname, check the address for typos, spaces, missing slashes, or doubled dots (for example, api..example.com). Pasting the URL into a web browser is a quick way to confirm it is valid.

Could not resolve host means the computer could not find the server's name. The hostname may be misspelled, the service may have moved, the internet connection or VPN may be down, or the DNS server may be unreachable.

Too many redirects usually points to a redirect loop, often caused by mixing http:// and https://, or by a server that keeps sending the request to a login page.

Timeout errors mean the server was too slow or unreachable. Check that a firewall or proxy is not blocking the connection, try again later, and consider increasing the timeout if the server is slow by nature or the download is large.

Request cancelled or terminated typically means the Task was stopped manually or the service was shutting down, for example, due Windows Update.

Run As could not switch users points to the Windows account the Task runs under, so check that its password has not changed or expired and that it still has permission to run Tasks.

Finally, an invalid HTTP header error can mean the server replied in an unexpected way. The Web profile lets you choose the HTTP version, and switching to HTTP/1.1 is worth trying.

Certificates & TLS

Client certificates, server certificate validation, TLS negotiation, certificate pinning, and HTTP/2 transport errors.

These errors occur while setting up a secure (HTTPS) connection, before any data is exchanged. If the message mentions the local SSL certificate, a certificate format compatibility error, or client cert not found in cert store, the problem lies with your own client certificate.

Verify that the certificate path is correct and any certificate password is right. When using the Windows certificate store, make sure the certificate is installed for the local comuter or account that actually runs the Task, which may differ from your own user account.

Untrusted root means the server's certificate was issued by an authority Windows does not trust, which is common with internal or self-signed certificates. Installing the issuing certificate into the Trusted Root store on the computer usually fixes it.

A hostname mismatch means the address in the URL does not match the name on the server's certificate. Use the exact hostname the certificate was issued for rather than an IP address or alias.

Public key does not match pinned public key usually means the server has renewed or replaced its certificate, so the pinned key needs updating.

Unsupported function or a general SSL connect error often indicates that the client and server could not agree on a TLS version or cipher, which can happen with outdated servers or restrictive Windows security settings.

The Local Security Authority cannot be contacted points to a Windows-level problem that may be resolved by a restart or system updates.

HTTP/2 stream reset and HTTP/2 framing layer errors can sometimes be avoided by switching to HTTP/1.1.

OAuth 2.0

OAuth credential loading, registry access, token requests, and unexpected OAuth responses.

These errors relate to the sign-in credentials used to access services such as Gmail, Microsoft 365, or other cloud APIs.

Could not load OAuth 2.0 credential or could not read OAuth 2.0 registry usually means the saved credential was deleted or renamed. Open the Action, reselect the credential, or create and authorize it again.

OAuth 2.0 request error and unexpected OAuth 2.0 response errors mean the sign-in provider rejected the request or answered in an unexpected way. Common causes include:

• an expired or revoked authorization,
• a changed account password,
• a client ID or secret that was changed or deleted at the provider,
• missing permissions (scopes) that the API requires.

Re-authorizing the credential is the first thing to try, followed by reviewing the app settings in the provider's developer console. If the message mentions not enough space on the disk, free up disk space, because the tokens received from the provider need to be saved locally.

File operations

Errors while loading, saving, deleting, or accessing files used by the Action.

These errors occur when the Action reads or writes files, such as the downloaded response, cookie files, or temporary files. The system cannot find the path specified usually means a folder in the path does not exist. Create the folder, or correct the path. If a file name has no folder (for example, just response), give a full path so the file ends up where you expect.

Keep in mind that mapped network drive letters available in your own session may not exist for the account running the Task, so use the full network path (such as \\server\share\folder) instead.

Access is denied means the account running the Task lacks permission to write there. It can also mean the file is open in another program or blocked by antivirus software. Check folder and network share permissions for that specific account.

The file exists means the Action was told not to overwrite existing files. Enable overwriting, or use a unique file name, for example one that includes the date and time.

HTTP response codes

HTTP responses returned by the server and processed as errors by the Action.

With these errors, the connection to the server itself worked, the server received the request and replied with an error code. As a rule of thumb, codes in the 400s point to a problem with the request, while codes in the 500s point to a problem on the server. View common response codes.

If a particular response is expected and harmless in your workflow, you can treat it as a warning instead of an error in the Action's Flow tab.

Summary

Start with the exact error message shown in the Event, as it usually identifies which part of the operation failed. Depending on the message, verify the URL and hostname, network connectivity and DNS, Web profile settings, authentication and certificates, file paths and permissions, or the HTTP response returned by the server.

For HTTP response errors, open the Action's Flow tab and review the Process response codes configuration. If a particular response is acceptable for the workflow, it can be handled as a warning instead of an error.

Debugging

If the cause is not clear, enable client and HTTP server communication logging in the Web profile and reproduce the issue. Detailed communication information can help identify where the request failed. If the problem persists, contact Febooti support and include the Task file, service.log file, and the communication debug log.

Note

Web operations depend on multiple components, including Windows networking, DNS, TLS, authentication, the local file system, the remote server, and the underlying web engine. As a result, the API call failed Event can contain many different error messages. The examples above are representative and are not an exhaustive list.

Web

• Get Webpage Content · Overview · Events · 610400
• Upload File to Website · Overview · Events · 611400
• Download File from Website · Overview · Events · 612400
• Save Webpage · Overview · Events · 613400
• Submit Web Form · Overview · Events · 614400

Just ask…

If you have any questions, please do not hesitate to contact our support team.