1. Error Code Guide
Storm OpenAPI(en)
  • Welcome to STORM
    • Introduction
  • Quickstart
    • Getting Started
      • Account Creation
      • Creating an Agent
    • Core Scenario
      • Document Upload
      • Workflow Design
      • Test
      • Deployment
      • Channel Integration
  • Feature Guide
    • Console
      • Agent Management
      • Dashboard
      • Permission Management
    • Agent Template
      • Deep Knowledge Exploration
      • Explore knowledge
      • Free Chat
      • Create reports
      • FAQ Chatbot
      • Resume Screening
      • Character Conversation
      • Analyze chat history
      • Write articles
      • Write SQL queries
    • Agent Builder
      • Knowledge
        • Documents
        • Folders
        • Feedback
      • Workflow
        • Node Description
          • LLM
          • Search(RAG)
          • Agentic RAG
          • API
          • IF ELSE
          • Variable Declaration and Assignment
          • Postprocessing
          • Response
          • Loop
          • Document Generation
      • Test
      • Log
      • Dashboard
    • Admin Tools
      • Deployment Management
      • Channel Integration
      • Model Fine-Tuning
      • Training Data Quality Management
      • Other Settings
      • Teams Channel Integration
  • Apis
    • Agent
      • Deploy Agent
      • View Agent Deployment History
      • View Agent
    • Bucket
      • Create Bucket
      • View Bucket
    • Document
      • Document Training Request by file
      • Document Training Request by URL
      • View Documents
      • Delete Document
    • Chat
      • File upload during chat
        • File creation and presigned URL issuance
        • File upload completion handling
        • File status lookup
      • Chat Sending (OpenAI Compatible)
      • Send Chat (non-stream)
      • Send Chat (stream)
      • Search Context
    • STORM Parse
      • /convert/md
    • Instance Agent
      • Add Instance Session
      • Upload Instance Document
      • Request RAG Source For Query
      • Delete Instance Session
  • Learn More
    • FAQ
    • Pricing
    • Error Code Guide
      • AgentRag
      • ApiCall
      • DocGen
      • Function
      • IfElse
      • Loop
      • OpenLLM
      • Post
      • Rag
      • Response
      • Variable
  1. Error Code Guide

ApiCall

Validation Errors#


APICALL_MISSING_METHOD#

The HTTP method (method) is not set in the ApiCall node.
In the node settings, select one of the following HTTP methods for method: GET, POST, PUT, DELETE, PATCH, HEAD, or OPTIONS.
Check whether a value has been entered in the method property of the ApiCall node.

APICALL_MISSING_URL#

The URL to call is not specified in the ApiCall node. Workflow execution has been stopped.
Enter a URL in the url property in the ApiCall node settings.
Check whether the URL is in the correct format.

APICALL_INVALID_URL_FORMAT#

The value of the url property in the ApiCall node is not in a valid format.
Check whether the url value starts with http:// or https://.
Check whether the url value contains any spaces.
Re-enter the url value in the workflow builder.

APICALL_INVALID_HTTP_METHOD#

An unsupported HTTP method is being used in the ApiCall node.
Enter one of the following in the method property: GET, POST, PUT, DELETE, PATCH, HEAD, or OPTIONS.
Check the ApiCall node settings and select a valid HTTP method.

APICALL_INVALID_BODY_TYPE#

An unsupported body_type is set in the ApiCall node. Workflow execution failed.
Change the body_type value to one of the following: json, form, text, none.
Check which body_type is required by the API.

Network Errors#


APICALL_CONNECTION_FAILED#

The ApiCall node failed to connect to the server. Check whether the url is correct and whether the network connection is working properly.
Check whether the url is entered correctly in the node settings.
Check the network connection status.
Check whether the API server is operating properly.

APICALL_CONNECTION_TIMEOUT#

The ApiCall node failed because the API call timed out.
Check whether the url of the ApiCall node is correct.
Check whether the API server is operating properly.
Increase the timeout setting of the ApiCall node.

APICALL_READ_TIMEOUT#

The API call failed due to a timeout. The server accepted the connection, but the response took too long.
Increase the timeout value of the ApiCall node.
Check whether the API server is operating properly.
Change the API call method to reduce the response time of the API server.

APICALL_WRITE_TIMEOUT#

The API call timed out before the request could be completed.
Check the timeout setting of the ApiCall node and increase it if necessary.
Check whether the API server is operating properly.
Check the network connection status.

APICALL_DNS_FAILURE#

DNS resolution failed during the API call. Check whether the host name entered in the url is correct and accessible.
Check whether the correct host name is entered in the url property.
Check whether the host name is accessible over the network.
Review the url setting of the ApiCall node again in the workflow builder.

APICALL_SSL_ERROR#

The SSL/TLS secure connection failed during the API call. There may be a problem with the server certificate.
Check whether the SSL certificate of the target API server is valid.
Check whether the url property of the ApiCall node is correct.
Review the ApiCall node settings again in the workflow builder and rerun the workflow.

HTTP Status Errors#


APICALL_HTTP_400#

A bad request (400) occurred in the ApiCall node. The server rejected the request.
Check whether the url property is correct.
Check whether the request body or query parameters meet the server requirements.
Refer to the API provider’s documentation to verify the request format.

APICALL_HTTP_401#

The API call failed. This API requires authentication, and the authentication information is invalid.
Check whether the API key or authentication header is correct in the ApiCall node settings.
Request a valid API key from the API provider.
Check the required authentication method in the API documentation and apply it to the workflow.

APICALL_HTTP_403#

The API call failed. You do not have permission to access the API.
Request the required permissions from the API provider.
Check whether the API key or authentication information is correct.
Check whether the url of the ApiCall node is correct.

APICALL_HTTP_404#

The API call failed. The server responded that it could not find the requested URL.
Check whether the url property of the ApiCall node is correct.
Check again for any typos in the URL path.
Check whether the API you are trying to call is available at that path.

APICALL_HTTP_408#

The API call failed because it timed out. The server closed the connection before completing the request.
Check whether the url of the ApiCall node is valid.
Check whether the API server is operating properly.
Increase the timeout setting of the ApiCall node.

APICALL_HTTP_429#

The API call rate limit has been exceeded. Too many requests were sent in a short period of time.
Increase the interval between API calls.
Reduce the frequency of workflow execution.
Check the API provider’s rate limits and request a higher limit if needed.
Implement retry logic in the ApiCall node to handle temporary errors.

APICALL_HTTP_500#

An unexpected error occurred on the server during the API call.
Check whether the API server is operating properly.
Contact the API provider to check the server status.
Check whether the url of the ApiCall node is correct.

APICALL_HTTP_502#

The API call failed because the server was temporarily unavailable.
Run the workflow again after a short wait.
Check the service status of the API provider.
Check whether the url of the ApiCall node is correct.

APICALL_HTTP_503#

The API call failed. The target service is temporarily unavailable.
Run the workflow again after a short wait.
Check whether the target service is operating properly.
Contact the API provider to check the service status.

APICALL_HTTP_504#

The API call failed because the server took too long to respond.
Check whether the API server is operating properly.
Check whether the url of the ApiCall node is correct.
Increase the timeout setting of the ApiCall node.
Contact the API server provider to identify the cause of the delayed response time.

APICALL_HTTP_CLIENT_ERROR#

A client error (4xx) occurred in the ApiCall node. Check the request URL, headers, and body.
Check whether the url property is correct.
Check whether the request headers are configured correctly.
Check whether the request body meets the API requirements.
Contact the API provider to resolve the issue.

APICALL_HTTP_SERVER_ERROR#

An unexpected server error occurred during the API call. The target service may be temporarily unavailable.
Run the workflow again after a short wait.
Check whether the API service is operating properly.
Check whether the url setting of the ApiCall node is correct.

Processing Errors#


APICALL_JSON_PARSE_ERROR#

The API call failed because the API response format is not JSON.
Check whether the API server returns a response in JSON format.
Check whether the url of the ApiCall node is correct.
Use a different API endpoint or contact the API provider.

APICALL_RESPONSE_PARSE_ERROR#

The API response format is different from what was expected, so the data cannot be processed.
Check whether the API response format is correct.
Contact the API provider to confirm the response format.
Adjust the response data handling method in the ApiCall node settings.

APICALL_PLACEHOLDER_ERROR#

A required value for the API call was not entered correctly. The referenced node ID or field name may not exist.
Check whether the referenced node ID and field name are correct in the ApiCall node settings.
Check whether the referenced node exists in the workflow.
Check whether any required input fields are missing.

APICALL_URL_ENCODING_ERROR#

URL encoding failed during the API call. Check whether there are invalid characters in the URL or query parameters.
Check the URL entered in the url property of the ApiCall node.
If the URL contains special characters or spaces, encode them properly.
Check and correct any invalid characters in the query parameters.

Unknown Error#


APICALL_UNKNOWN_ERROR#

An unexpected error occurred in the ApiCall node. The API server may not be responding, or the node settings may be incorrect.
Check whether the API server is operating properly.
Check whether the url of the ApiCall node is correct.
Check whether the other properties of the ApiCall node are configured correctly.
Modified at 2026-05-27 11:23:16
Previous
AgentRag
Next
DocGen
Built with