Trigger a pipeline through an API #6129

eleonora011 · 2025-12-05T13:38:52Z

eleonora011
Dec 5, 2025

Good morning,
I wanted to trigger a pipeline through an API call. While reading the documentation, I found the following:
"GET http://localhost:8081/hop/startPipeline?name=".

When I send the request — obviously setting the correct host and port — I get the following error: 400 Bad Request, and:

<HEAD>
    <TITLE>Start of pipeline</TITLE>
    <META http-equiv="Refresh" content="2;url=pipelineStatus?name=test_pipeline">
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <link rel="icon" type="image/svg+xml" href="/static/images/favicon.svg">
</HEAD>
 
<BODY>
    <H1>The specified pipeline [test_pipeline] could not be found</H1>
    <a href="status">Back to the status page</a>
    <p>
    <p>
</BODY>
 
</HTML>

The pipeline is located at the following path on Apache Hop Web:
"default/hop-workspace/pipelines/"

hansva · 2025-12-05T13:44:43Z

hansva
Dec 5, 2025
Collaborator

That endpoint requires you to first register the pipeline using registerPipeline.
I would recommend using a Async webservice

0 replies

eleonora011 · 2025-12-09T14:17:17Z

eleonora011
Dec 9, 2025
Author

Good morning,
I am trying to configure a WebService and then schedule it.
When I invoke the call to trigger the WebService, I get the following error:
org.apache.hop.core.exception.HopException: Unable to find web service 'test_service'. You can set the metadata_folder in the Hop server XML configuration org.apache.hop.www.WebServiceServlet.doGet(WebServiceServlet.java:107) org.apache.hop.www.HopServerServlet.doGet(HopServerServlet.java:69) jakarta.servlet.http.HttpServlet.service(HttpServlet.java:564) jakarta.servlet.http.HttpServlet.service(HttpServlet.java:658) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
From the configuration we are not able to identify the error. I am attaching the configurations.
WebService:
{ "transformName": "Generate rows", "virtualPath": "", "fieldName": "id", "filename": "${PROJECT_HOME}/test.hpl", "bodyContentVariable": "", "headerContentVariable": "", "listingStatus": false, "name": "test_service", "runConfigurationName": "local", "contentType": "application/json", "enabled": true, "statusCode": "" }
Hop Server XML:

<hop-server-config>
<hop-server>
<name>server-8181</name>
<hostname>localhost</hostname>
<port>8181</port>
<shutdownPort>8182</shutdownPort>
</hop-server>
<joining>true</joining>
<max_log_lines>0</max_log_lines>
<max_log_timeout_minutes>1440</max_log_timeout_minutes>
 <object_timeout_minutes>1440</object_timeout_minutes>
 <metadata_folder></metadata_folder>
</hop-server-config>

I tried to define the metadata folder in the XML without success, as follows:
/usr/local/tomcat/webapps/root/config/projects/default/metadata
For clarity, this is the image I am using to bring up the container: apache/hop-web:latest

2 replies

hansva Dec 9, 2025
Collaborator

The Hop-Web image does not start the Hop-Server. I guess those endpoints might work because the jars are being loaded in Tomcat, but we never tested this approach. For Hop-server you have to use the apache/hop image and configure it to start with the metadata folder. Docs can be found here

eleonora011 Dec 10, 2025
Author

I shared the metadata folder between hop-web and the hop server, so now the hop server can access the metadata folder.
I tried making the call and what I get is the following error:
HTTP ERROR 500 jakarta.servlet.ServletException: Error producing web service output.
The configurations are as follows:
web-service:

{
  "transformName": "output",
  "virtualPath": "",
  "fieldName": "id",
  "filename": "${PROJECT_HOME}/test_prova.hpl",
  "bodyContentVariable": "",
  "headerContentVariable": "",
  "listingStatus": false,
  "name": "hop_service",
  "runConfigurationName": "hop-server-external",
  "contentType": "text/plain",
  "enabled": true,
  "statusCode": ""
}

pipeline-run-configuration:

{
  "engineRunConfiguration": {
    "Remote": {
      "export_resources": false,
      "resources_target_folder": "",
      "resources_source_folder": "",
      "run_config": "local",
      "server_poll_interval": "",
      "hop_server": "apache-hop-server",
      "server_poll_delay": ""
    }
  },
  "virtualPath": "",
  "defaultSelection": false,
  "configurationVariables": [],
  "name": "hop-server-external",
  "description": "remote connection for hop pipelines executions",
  "dataProfile": "first-last",
  "executionInfoLocationName": "local-audit"
}

apache-hop-server container

{
  "webAppName": "",
  "sslMode": false,
  "proxyPort": "",
  "hostname": "apache-hop-server",
  "nonProxyHosts": "",
  "password": "----",
  "virtualPath": "",
  "port": "8080",
  "name": "apache-hop-server",
  "proxyHostname": "",
  "username": "----"
}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Trigger a pipeline through an API #6129

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Trigger a pipeline through an API #6129

Uh oh!

eleonora011 Dec 5, 2025

Replies: 2 comments · 2 replies

Uh oh!

hansva Dec 5, 2025 Collaborator

Uh oh!

eleonora011 Dec 9, 2025 Author

Uh oh!

hansva Dec 9, 2025 Collaborator

Uh oh!

eleonora011 Dec 10, 2025 Author

eleonora011
Dec 5, 2025

Replies: 2 comments 2 replies

hansva
Dec 5, 2025
Collaborator

eleonora011
Dec 9, 2025
Author

hansva Dec 9, 2025
Collaborator

eleonora011 Dec 10, 2025
Author