UiPath-ADPv1 API Automation Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Add a JSON body with {"api_key": "value"} in the Body property.

  Why it's wrong here

  The API expects the key as a query parameter, not in the body. Using the body is for POST/PUT requests with payloads. For a GET request, the body is typically ignored. This approach would not authenticate the request and could cause a 401 or 400 error.

• ✗

  Use the Authentication property to select "API Key" and enter the value.

  Why it's wrong here

  The HTTP Request activity does not have a built-in API Key authentication option. While some activities have authentication helpers, this one requires manual configuration. Selecting a non-existent option would not work, and the key must be placed in the URL as a query parameter.

• ✓

  Add the parameter to the URL property by appending "?api_key=value" to the endpoint URL.

  Why this is correct

  Query parameters are part of the URL. Appending "?api_key=value" directly to the URL is the correct way to pass an API key as a query parameter. This ensures the API receives the key as expected. The HTTP Request activity does not have a separate query parameter collection, so modifying the URL is necessary.

• ✗

  Add a header with Name "api_key" and Value "value" in the Headers property.

  Why it's wrong here

  Headers are used for metadata like authentication tokens, but the API specifically requires the key as a query parameter. Sending it as a header would not satisfy the API's requirement and would likely result in an authentication error. Always follow the API documentation for parameter location.