AnsweredAssumed Answered

AssetView API endpoint results in page not found

Question asked by Alexandre Philbert on Jan 16, 2019
Latest reply on Jul 1, 2019 by charles robbins

Like • Show 1 Like1
Comment • 8

Hello,

I am trying to use the Qualys API (enterprise, student account) to search for assets similarly to how you would search them in the UI (using filters, boolean expressions, etc).

Here is the cURL command I am using for the API call:


curl -u "USERNAME:PASSWORD" -H "content-type: text/xml" -X "POST" --data-binary @- "https://qualysguard.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/" < ~/Downloads/params.xml

Here are the contents of params.xml, used in the call:

<ServiceRequest>
   <filters>
      <Criteria field="os" operator="EQUALS">Windows</Criteria>
   </filters>
</ServiceRequest>

I get a "404 - Page Not Found" when I run the previously detailed command. I am not sure what is going wrong since I have no trouble with other calls such as report downloading and authentication record manipulations.

So, is something wrong with this endpoint? Has it changed? Or, am I making a mistake?

Thank you very much!

Torsten X Jan 18, 2019 1:37 AM

Correct Answer

Now I see your mistake, your URL is wrong.

"https://qualysguard.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/"

Change it to the one in the documentation

"https://qualysapi.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/"

See the reply in context

No one else had this question

Outcomes

Alexandre Philbert @ Busby on Jan 16, 2019 1:57 PM

Thanks for the reply! Sadly it doesn't work either way.

Actions

Torsten X Jan 17, 2019 7:40 AM

Where you found the link to this call? I can't find it in the API, I guess in that link is the mistake.

Actions

Alexandre Philbert @ Torsten X on Jan 17, 2019 8:14 AM

Thanks for responding.

I found this here: https://www.qualys.com/documentation/. Look for Asset Mgmt and Tagging v2 API. Finally, turn to page 67!

Actions

Torsten X @ Alexandre Philbert on Jan 18, 2019 1:34 AM

Try to use full path instead of relative. Maybe this works for you.

< /../../../Downloads/params.xml

Otherwise, i have no idea

Actions

Torsten X @ Torsten X on Jan 18, 2019 1:37 AM

Now I see your mistake, your URL is wrong.

"https://qualysguard.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/"

Change it to the one in the documentation

"https://qualysapi.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/"

4 people found this helpful

Actions

Alexandre Philbert @ Torsten X on Jan 18, 2019 7:05 AM

Unbelievable! I have no clue how I didn't accidentally copy paste the correct one at some point... Thank you so much!

EDIT: I've been using 'qualysguard.qg3.apps.qualys.com' for all of my other work with the API and it worked. So, it seems certain endpoints are not supported by the old URL.

Actions

charles robbins Jul 1, 2019 12:46 AM

Hello

I get this message "page not found" whilst running a tagging script. It did about 100 successful calls then it starts sending this error message ( for all types of API calls). I know there is a limit to how many API calls you can do in a time period but this usually gives me a specific message. I cannot see any such resource limit messages in the activity log either. Maybe it is because of the number of calls.

thanks

Actions

8 Replies

Busby Jan 16, 2019 1:53 PM

Try taking off the final /

https://qualysguard.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/

Try
https://qualysguard.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset

Just a quick change to see if that works.

Alexandre Philbert @ Busby on Jan 16, 2019 1:57 PM
Mark Correct
Correct Answer
Thanks for the reply! Sadly it doesn't work either way.
Like • Show 1 Like1
Actions

Torsten X Jan 17, 2019 7:40 AM
Mark Correct
Correct Answer
Where you found the link to this call? I can't find it in the API, I guess in that link is the mistake.
Like • Show 2 Likes2
Actions
- Alexandre Philbert @ Torsten X on Jan 17, 2019 8:14 AM
  Mark Correct
  Correct Answer
  Thanks for responding.
  
  I found this here: https://www.qualys.com/documentation/. Look for Asset Mgmt and Tagging v2 API. Finally, turn to page 67!
  Like • Show 1 Like1
  Actions
  - Torsten X @ Alexandre Philbert on Jan 18, 2019 1:34 AM
    Mark Correct
    Correct Answer
    Try to use full path instead of relative. Maybe this works for you.
    < /../../../Downloads/params.xml
    Otherwise, i have no idea
    Like • Show 1 Like1
    Actions
    - Torsten X @ Torsten X on Jan 18, 2019 1:37 AM
      Unmark Correct
      Correct Answer
      Now I see your mistake, your URL is wrong.
      "https://qualysguard.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/"
      Change it to the one in the documentation
      "https://qualysapi.qg3.apps.qualys.com/qps/rest/2.0/search/am/hostasset/"
      4 people found this helpful
      Like • Show 4 Likes4
      Actions
      - Alexandre Philbert @ Torsten X on Jan 18, 2019 7:05 AM
        Mark Correct
        Correct Answer
        Unbelievable! I have no clue how I didn't accidentally copy paste the correct one at some point... Thank you so much!
        
        EDIT: I've been using 'qualysguard.qg3.apps.qualys.com' for all of my other work with the API and it worked. So, it seems certain endpoints are not supported by the old URL.
        Like • Show 0 Likes0
        Actions
charles robbins Jul 1, 2019 12:46 AM
Mark Correct
Correct Answer
Hello
I get this message "page not found" whilst running a tagging script. It did about 100 successful calls then it starts sending this error message ( for all types of API calls). I know there is a limit to how many API calls you can do in a time period but this usually gives me a specific message. I cannot see any such resource limit messages in the activity log either. Maybe it is because of the number of calls.
thanks
Like • Show 1 Like1
Actions

AssetView API endpoint results in page not found

Outcomes

Related Content

Recommended Content