Issues

  • Blocked Calls against the API

    Hello, As far as I can tell we have two subscriptions (Basic and Test) but when I attempt to 'try' the API calls, I get 401 Unauthorized. In the Analytics pages I see that the calls are 'Blocked'. Can someone please help me understand what the issue(s) might be? Thanks in advance.

    Status: Proposed | Reported by Hidden Wed, 05 May 2021 15:35:38 GMT
  • Share_Get API endpoint, paging overlap?

    I'm trying to automate downloading of all our content metadata like titles, knowledgestate etc using the Search_Get API. I've implemented the pagination but i keep getting duplicate results back. In total there are over 13000 articles in scope and i never get the same number after looping through the pages. Example of API call, in the example below we pull from page 1 to page 137 to get all our articles for that search https://api2.comaround.com/rest/v2/search?searchPhrase=*&sortBy=Alphabetic&knowledgeStates=Published&knowledgeStates=Approved&knowledgeStates=WorkInProgress&knowledgeStates=Draft&tags=Text&tags=Video&languages=en-US&ItemsPerPage=100&CurrentPage=1 Around 130 articles are returned several times, 81 articles occur twice, 40 three times and the worst one is 1107522 which is always returned over 20 times. We also get strange incorrect results, like article 1111121 "FSE PC Installation Guide for OSS" which is archived shows up as published through the Search API. Count Name ----- ---- 81 2 40 3 3 4 2 6 1 21 1 10 1 9 1 8 1 5 id searchResultId title knowledgeState -- -------------- ----- -------------- 1107522 1107522-92-1033-1178021 Quix applications suplier support approved 1107522 1107522-92-1033-1179721 Quix applications suplier support approved 1107522 1107522-92-1033-1179748 Quix applications suplier support approved 1107522 1107522-92-1033-1184362 Quix applications suplier support approved 1107522 1107522-92-1033-1178488 Quix applications suplier support approved 1107522 1107522-92-1033-1166467 Quix applications suplier support approved 1107522 1107522-92-1033-1184377 Quix applications suplier support approved 1107522 1107522-92-1033-1184401 Quix applications suplier support approved 1107522 1107522-92-1033-1179778 Quix applications suplier support approved 1107522 1107522-92-1033-1179802 Quix applications suplier support approved 1107522 1107522-92-1033-1184354 Quix applications suplier support approved 1107522 1107522-92-1033-1179702 Quix applications suplier support approved 1107522 1107522-92-1033-1179755 Quix applications suplier support approved 1107522 1107522-92-1033-1158913 Quix applications suplier support approved 1107522 1107522-92-1033-1178029 Quix applications suplier support approved 1107522 1107522-92-1033-1179743 Quix applications suplier support approved 1107522 1107522-92-1033-1184356 Quix applications suplier support approved 1107522 1107522-92-1033-1166487 Quix applications suplier support approved 1107522 1107522-92-1033-1178018 Quix applications suplier support approved 1107522 1107522-92-1033-1178550 Quix applications suplier support approved 1107522 1107522-92-1033-1165163 Quix applications suplier support approved

    Status: Proposed | Reported by Hidden Thu, 29 Apr 2021 19:00:27 GMT
  • Why are the backend search/ APIs not exposing knowledgestates other than published?

    The backend API only returns articles with knowledgestate published, it has always been like that but not a show stopper until now. Also, the KnowledgeStates parameter does not do anything to help this. example: (https://api2.comaround.com/rest/v2/search/?currentPage=1&searchPhrase=test) returns only published articles where the Zero frontend API returns all knowledgestates when using the "same" endpoint. (https://api2.comaround.com/zero/v2/search/?currentPage=1&searchPhrase=test) We need to be able to pull our non-published articles via the API, please advise.

    Status: Proposed | Reported by Hidden Sun, 25 Apr 2021 18:55:12 GMT
  • Get Token -- Invalid Custom Credentials

    I receive a "400 Bad Request invalid_grant Invalid custom credentials" when I post to https://api2.comaround.com/rest/v1/token/?username=[username]&password=[password] with the header "Ocp-Apim-Subscription-Key" and one of my subscription keys from my developer profile. I am using the username and password for the developer account. Should I use a different username and password? Thanks

    Status: Proposed | Reported by Hidden Thu, 28 May 2020 14:03:31 GMT
  • Getting 500 error when we invoke token API

    { "statusCode": 500, "message": "Internal server error", "activityId": "dadbd49e-c8aa-48c0-957a-96d40c2cf18f" }

    Status: Resolved | Reported by Hidden Tue, 13 Aug 2019 12:22:02 GMT
  • IE Blocks Cookies in an iFrame: IE & P3P

    We ran into a simular problem while working on an integration to Marval described in this post: https://jwcooney.com/2011/08/19/ie-blocks-cookies-in-an-iframe-ie-p3p/ Is it possible for ComAround to add an Extra header to make this work in iFrame in IE 11?

    Status: Proposed | Reported by Hidden Mon, 21 Jan 2019 12:59:08 GMT
  • Invoke-RestMethod gives an error

    I use a Powershell script that has been working without issue for months. However when I attempted to run it yesterday I am now gettign the error "The underlying connection was closed: An unexpected error occurred on a send." Has anything changed that might cause this error?

    Status: Proposed | Reported by Hidden Fri, 04 Jan 2019 16:37:04 GMT

You're not signed in. Please sign-in to report an issue or post a comment.