Parameters on REST Service connections
- Last Updated: July 16, 2025
- 1 minute read
- Corticon
- Version 6.3
- Documentation
- URL
- Path
- Post
You can specify as many of these parameters on a connection in no particular order. Each requires a name and should have a default value.
Note: The following examples use the
test URL https://qknpo561c0.execute-api.us-east-2.amazonaws.com/prod/ReimbursementRate/.
URL type
A URL parameter can specify the procedure code in the REST URL:https://TestURL?procedureCode=B5120ZZwith
the results:
{"results":[{"procedureCode":"B5120ZZ","rates":
[{"startDate":"2017-1-1","endDate":"2017-6-1","rate":0.85},
{"startDate":"2017-6-2","endDate":"2017-12-31","rate":0.83}]}]}
The API Gateway entry point is: ReimbursementRate-API You
can manually add more URL types. Path type
A path parameter can specify the procedure code in the REST URL:https://TestURL/0313090with
the results: {"results":[{"procedureCode":"0313090","rates":
You can manually add more Path types.
[{"startDate":"2017-1-1","endDate":"2017-12-31","rate":0.82
Note: Parameters that have default
values are in the Ruleflow. Parameters that do not have default values are taken to be
static parameter options that are not intended to take values; therefore, you cannot
override their values.
Post type
A Post request does not include parameters as part of the URL, instead the parameters are data in the request document. Selecting Post parameter type changes how the REST connector makes its requests to the endpoint, so it is possible that any specified URL parameters will be ignored.