Not able to get Campaign Filter over API

Identity Security Cloud (ISC) ISC Discussion and Questions
1

The API in question:
get-campaign-filter-by-id | SailPoint Developer Community

Gave it the campaign filter ID, but it came back with the following:

{
  "detailCode": "404 Not found",
  "trackingId": "<REDACTED>",
  "messages": [
    {
      "locale": "en-US",
      "localeOrigin": "DEFAULT",
      "text": "The server did not find a current representation for the target resource."
    },
    {
      "locale": "en-US",
      "localeOrigin": "REQUEST",
      "text": "The server did not find a current representation for the target resource."
    }
  ],
  "causes": []
}

Is anyone else able to get a fitler via this API? Tried the v3 API as well, no luck.

2

Hi @RandomUser4096,

I tried using my postman, it’s working for me.
Could you please verify your api-url and also make sure you are using ‘GET’ and not ‘POST’.

image
image2256×800 87.3 KB

Also, I tried using the get-campaign-filter-by-id | SailPoint Developer Community to send the api request. It actually didn’t work for me there.

image
image624×595 31.4 KB

Thanks!

3

Hi Terry,

Try without the ID first to get all campaign filters:
https://sailpoint.api.identitynow.com/v2024/campaign-filters

Then find the ID in the response and then append to the GET above, and it should be all good

https://sailpoint.api.identitynow.com/v2024/campaign-filters/<id>

4

Hi @RandomUser4096
Most probably, the id you’re using is incorrect.
Please try to GET all the filters using list-campaign-filters | SailPoint Developer Community and try to pull the id from response to use it on get-campaign-filter-by-id | SailPoint Developer Community.

5

That’s exactly what I did to get the IDs…and then I tried using one of the returned IDs for the subsequent call…and that did NOT work when you run it against get-campaign-filter-by-id | SailPoint Developer Community on the page.

Also tried with the Powershell SDK cmdlet…which also do not work (v3, v2024).

6

@RandomUser4096
Try to pull it from UI instead of GET all.
https://tenant.identitynow.com/ui/admin/#admin:cert:filters:cd04e2xxxxxxd293b1c and then use the same id to pull.

7

Thanks, the intent is not to find an API endpoint through undocumented paths, but instead, the documented API endpoints should work as intended.

SailPoint should address the issue if it is deemed to be a bug.

1 Like
8

You can use the same get-campaign-filter-by-id | SailPoint Developer Community and add the id you found from SailPoint UI.
If this works, you were probably using wrong id earlier.
I don’t see any bug here.

9

See the 2nd half of Sachin’s response above.

10

404 is usually when you enter incorrect id. Did you try the UI way ?

11

No. That’s not the concern (i.e. Not trying to ‘find some way to get the data’, but rather, what should work, should work).

Another example, the following returns the first filter’s ID without issue (PowerShell SDK):
$($(Get-V2024CampaignFilters).items | select-object -first 1).id

But, if I then do this, it wouldn’t return that particular filter object, even though it’s the exact ID that was retrieved:
Get-V2024CampaignFilterById -FilterID $($(Get-V2024CampaignFilters).items | select-object -first 1).id

12

Hi

What if you use /v3 endpoint instead of /v2024?

I have a script that does uses /v3, and have no issues

listCampaignsFiltersResponse = <GET /v3/campaign-filters>
campaignItemArray = JSON.parse(listCampaignsFiltersResponse.body)["items"] 
campaignItemArray.each {|k| 
	campaignFilterId = k['id']
13

Same behaviour / issue. V3 was my first choice…thinking it’s relatively more mature / filed tested by others…but no go.

In your code about, you’re only getting a list of filters. Yes, that works. But now, if you try to get ONLY one filter by supplying the ID, that doesn’t seem to work.

It’s the “get campaign filter by ID” that’s not working (for me).

14

Hey @RandomUser4096 ,

I have not tried with the v2024 api, but the V3 api returns the result.
Please see the below attached postman call.
Here to get the Filter ID i have used this api call: list-campaign-filters | SailPoint Developer Community

Now, just make sure that in Headers, you have Content-Type: application/json
X-SailPoint-Experimental:true
Also the body should be set as none

Here’s the screenshot of same:

image
image992×461 25.5 KB

Hope this helps :slight_smile:

15

I have also tried the V2024 endpoint.

URL: {{baseurl}}/v2024/campaign-filters/:id
Here, the ID you will again get from the list-campaign-filters | SailPoint Developer Community

Type: GET
Body: none
Headers: other than general headers include:
X-SailPoint-Experimental:true

Here’s the response i have received:

image
image965×412 21.2 KB

Hope this also helps

16

Thanks…so it would seem that there’s an issue with the API documentation interface and the PS SDK cmdlet.

From the API documentation, I get this set of items as expected (from the list campaign filter call):

image
image548×529 16.7 KB

But when trying to get that filter back individually, by supplying the ID, I get this:

image
image561×869 28.6 KB

17

Hi Terry,

Do the request locally (using Postman for example)

Dont do it through developer.sailpoint.com

18

Yes, that seems to be an issue with the documentation, but if you try with the headers and call i have provided that should work for you.

@colin_mckibben there seems to be missing headers in the API call, can we please look into this.

19

Indeed, there is an issue with the API specification that is affecting the API explorer within the API specs and possibly even the powershell sdk. I have a fix that is being pushed now. If you run this API using postman or another tool, it will work.

2 Likes
20

The API explorer is fixed. You can now query campaign filters directly in our specs.