Refer to the RAML example for /patients. What is the correct URL to perform a GET request to /patients with a year parameter of 2016?

Refer to the RAML example for /patients. What is the correct URL to perform a GET request to /patients with a year parameter of 2016?

• A. http://dev.acme.com/api/patients
• B. http://dev.acme.com/api/patients?year=2016
• C. http://dev.acme.com/api/patients?year
• D. http://dev.acme.com/patients?year=2016

Answer: (B)

Passing a value to a query parameter in a GET request is done by appending ?param=value after the resource path. For the /patients resource under the API, the full path includes the base path /api, so you combine that with the query year=2016. The correct URL is http://dev.acme.com/api/patients?year=2016. Why this fits best: it targets the /patients resource and provides the year parameter with its value, exactly as specified. The other options fail because they either omit the year value, omit the API base path, or place the parameter on a path that doesn’t match the API structure.

Passing a value to a query parameter in a GET request is done by appending ?param=value after the resource path. For the /patients resource under the API, the full path includes the base path /api, so you combine that with the query year=2016. The correct URL is http://dev.acme.com/api/patients?year=2016.

Why this fits best: it targets the /patients resource and provides the year parameter with its value, exactly as specified. The other options fail because they either omit the year value, omit the API base path, or place the parameter on a path that doesn’t match the API structure.