I am building a REST API using IBM i Integrated Web Services (IWS).

Currently, the API works correctly when I pass a single path parameter (customer number) and returns the expected record.
For example, the following URL returns a valid response when I pass customer number 01010:

http://localhost:10099/web/services/CUSTQRYXX/01010

Now I would like to pass multiple path parameters, such as customer number and area code, to retrieve a record using both values.

I tried calling the API with an additional path parameter (area code 02) as shown below, but this results in a 404 Not Found error:

http://localhost:10099/web/services/CUSTQRYXX/01010/02

The parameters in IWS are configured as path parameters.

My questions are:

• Is it supported to specify multiple path parameters in an IWS REST service?

• If so, what configuration is required on the IWS side to handle multiple path parameters?

• Are there common causes of a 404 error in this scenario (IWS service definition, parameter mapping, ILE program interface, URL format, etc.)?

Any guidance or examples would be greatly appreciated...

Thank you

------------------------------
SAKURA KOGA
------------------------------

I am building a REST API using IBM i Integrated Web Services (IWS).

Currently, the API works correctly when I pass a single path parameter (customer number) and returns the expected record.
For example, the following URL returns a valid response when I pass customer number 01010:

http://localhost:10099/web/services/CUSTQRYXX/01010

Now I would like to pass multiple path parameters, such as customer number and area code, to retrieve a record using both values.

I tried calling the API with an additional path parameter (area code 02) as shown below, but this results in a 404 Not Found error:

http://localhost:10099/web/services/CUSTQRYXX/01010/02

The parameters in IWS are configured as path parameters.

My questions are:

• Is it supported to specify multiple path parameters in an IWS REST service?

• If so, what configuration is required on the IWS side to handle multiple path parameters?

• Are there common causes of a 404 error in this scenario (IWS service definition, parameter mapping, ILE program interface, URL format, etc.)?

Any guidance or examples would be greatly appreciated...

Thank you

------------------------------
SAKURA KOGA
------------------------------

In order to specify multiple pieces of information in path, you must deploy web service with URI path template.  Something like /{custno}/{areaCode}.  And then you need to inject those parameters in corresponding input parameter.  

Example is given in https://www.ibm.com/support/pages/system/files/inline-files/IWS-Building-REST-Service-Part-3_0.pdf, figure 11. 

------------------------------
Nadir K Amra

Original Message:
Sent: Tue January 06, 2026 01:36 AM
From: SAKURA KOGA
Subject: 404 error when using multiple path parameters in IBM i IWS

I am building a REST API using IBM i Integrated Web Services (IWS).

Currently, the API works correctly when I pass a single path parameter (customer number) and returns the expected record.
For example, the following URL returns a valid response when I pass customer number 01010:

http://localhost:10099/web/services/CUSTQRYXX/01010

Now I would like to pass multiple path parameters, such as customer number and area code, to retrieve a record using both values.

I tried calling the API with an additional path parameter (area code 02) as shown below, but this results in a 404 Not Found error:

http://localhost:10099/web/services/CUSTQRYXX/01010/02

The parameters in IWS are configured as path parameters.

My questions are:

• Is it supported to specify multiple path parameters in an IWS REST service?

• If so, what configuration is required on the IWS side to handle multiple path parameters?

• Are there common causes of a 404 error in this scenario (IWS service definition, parameter mapping, ILE program interface, URL format, etc.)?

Any guidance or examples would be greatly appreciated...

Thank you

------------------------------
SAKURA KOGA
------------------------------

Hi , @Nadir K Amra ,

Please double check that URL (it seems its got a "," at the end) which could be misleading to some who things the document is not available anymore. 

Thank you

In order to specify multiple pieces of information in path, you must deploy web service with URI path template.  Something like /{custno}/{areaCode}.  And then you need to inject those parameters in corresponding input parameter.  

Example is given in https://www.ibm.com/support/pages/system/files/inline-files/IWS-Building-REST-Service-Part-3_0.pdf, figure 11. 

I am building a REST API using IBM i Integrated Web Services (IWS).

Currently, the API works correctly when I pass a single path parameter (customer number) and returns the expected record.
For example, the following URL returns a valid response when I pass customer number 01010:

http://localhost:10099/web/services/CUSTQRYXX/01010

Now I would like to pass multiple path parameters, such as customer number and area code, to retrieve a record using both values.

I tried calling the API with an additional path parameter (area code 02) as shown below, but this results in a 404 Not Found error:

http://localhost:10099/web/services/CUSTQRYXX/01010/02

The parameters in IWS are configured as path parameters.

My questions are:

• Is it supported to specify multiple path parameters in an IWS REST service?

• If so, what configuration is required on the IWS side to handle multiple path parameters?

• Are there common causes of a 404 error in this scenario (IWS service definition, parameter mapping, ILE program interface, URL format, etc.)?

Any guidance or examples would be greatly appreciated...

Thank you

I am building a REST API using IBM i Integrated Web Services (IWS).

Currently, the API works correctly when I pass a single path parameter (customer number) and returns the expected record.
For example, the following URL returns a valid response when I pass customer number 01010:

http://localhost:10099/web/services/CUSTQRYXX/01010

Now I would like to pass multiple path parameters, such as customer number and area code, to retrieve a record using both values.

I tried calling the API with an additional path parameter (area code 02) as shown below, but this results in a 404 Not Found error:

http://localhost:10099/web/services/CUSTQRYXX/01010/02

The parameters in IWS are configured as path parameters.

My questions are:

• Is it supported to specify multiple path parameters in an IWS REST service?

• If so, what configuration is required on the IWS side to handle multiple path parameters?

• Are there common causes of a 404 error in this scenario (IWS service definition, parameter mapping, ILE program interface, URL format, etc.)?

Any guidance or examples would be greatly appreciated...

Thank you

Dear Sakura, 

Error 404 (Not Found) makes me think of a misconfigured path template (as Nadir mentioned) and therefore a problem with the service configuration (not the *pgm).
If the problem persists, could we have a screenshot of the configuration page for the service in question? (with a stop + redeploy command to return to it).

Best regards,

Gautier

I am building a REST API using IBM i Integrated Web Services (IWS).

Currently, the API works correctly when I pass a single path parameter (customer number) and returns the expected record.
For example, the following URL returns a valid response when I pass customer number 01010:

http://localhost:10099/web/services/CUSTQRYXX/01010

Now I would like to pass multiple path parameters, such as customer number and area code, to retrieve a record using both values.

I tried calling the API with an additional path parameter (area code 02) as shown below, but this results in a 404 Not Found error:

http://localhost:10099/web/services/CUSTQRYXX/01010/02

The parameters in IWS are configured as path parameters.

My questions are:

• Is it supported to specify multiple path parameters in an IWS REST service?

• If so, what configuration is required on the IWS side to handle multiple path parameters?

• Are there common causes of a 404 error in this scenario (IWS service definition, parameter mapping, ILE program interface, URL format, etc.)?

Any guidance or examples would be greatly appreciated...

Thank you