Will return data for that asset. You'll have to double-URL encode '-' (i.e. replace it with '%252d')
Kjetil Samuelsen
–
13 years ago
This was working well for a while, but today the same URL gives no results. I've tried with other asset id's as well.
active Admin
–
13 years ago
Hey Kjetil,
We recently made a change to the Search API whereby only events we do registration for are returned. This reduces the volume of events available in the API by about 20%, and is likely why you're not getting results for certain asset IDs. To compensate, you can use a new endpoint that has the old behavior (returning all events whether or not we do registration for them). Simply substitute "/search" with "/search-all". Everything else works exactly the same.
After testing for myself and reading other posts in this forum I know that the Asset Details API only returns certain asset types (for instance, the following URL will return an HTTP 500 status: http://api.amp.active.com/resource/assetservice/asset/017d9c4e-9926-4419-8e10-b59485e55804?api_key=u2hcu6p5qvwksr54gdz9rppz)
Is there any way to use the Search API to return a specific asset - either by asset id, event id or some other identifier?
Message edited by Kjetil Samuelsen 13 years ago
Tags
active Admin – 13 years ago
Yes, given assetId 458575e1-9a03-41f2-a550-54f728890556, for example, a query like this:
http://api.amp.active.com/search?m=meta:assetId=458575e1%252d9a03%252d41f2%252da550%252d54f728890556&v=xml&api_key=wuhmn9ye94xn3xnteudxsavw
Will return data for that asset. You'll have to double-URL encode '-' (i.e. replace it with '%252d')
Kjetil Samuelsen – 13 years ago
This was working well for a while, but today the same URL gives no results. I've tried with other asset id's as well.
active Admin – 13 years ago
Hey Kjetil,
We recently made a change to the Search API whereby only events we do registration for are returned. This reduces the volume of events available in the API by about 20%, and is likely why you're not getting results for certain asset IDs. To compensate, you can use a new endpoint that has the old behavior (returning all events whether or not we do registration for them). Simply substitute "/search" with "/search-all". Everything else works exactly the same.