We're in the process of adapting how one of our teams verifies content in Guru to more closely align with our KCS methodology. We've built an MVP where once a card has been added to a custom field in Zendesk and the ticket is submitted, we catch the hook, get the card ID from the Guru URL, and once it passes our validation, use PUT to update the card's verifier. We want to be able to set the verifier of the card as the ticket submitter, verify said card, and set its verification interval to 90 days.The MVP is functioning as expected but we've hit a roadblock with API credentials. The issue is that AFAIK we don't have a general or admin API token with read/write access. The collection API token would work for our use case, but they're read-only.
As a result, while we can assign the card to the SME who submits the ticket, we can't set the verification status to trusted. Without the ability to do so its purpose is defeated. Any suggestions on resolving or working around this? Can we get a general token with read/write access?
Additionally, while building out the MVP we ran into a couple of issues that we think would be useful feature requests. I've added them to the thread :slightlysmilingface:
Hi @ruairi.murphy , our engineers are still working on the documentation for managing and issuing individual tokens for you to use when changing the verifiers. In the meantime, we are hoping to help with your other questions:
1. *Can we work around having to update the card content when changing the verifier through the API?* You can do a POST call to this url `https://api.getguru.com/api/v1/cards/{cardid}/verifiers/` to change the verifier and that doesn't make a new version of the card.
2. *Why is `Preferred Phase` the object for the card title?* Our original thinking (back when Guru was just the extension :exploding_head:) was that cards could have multiple "phrases" associated with them and one would be designated as the "preferred" one and that'd be used as the title. A basic rule of thumb is that we don't want to make object changes that could break other clients solutions, so that is now the object name.
3. *It doesn't appear to be possible to query team members by email, which would be useful.* Are you looking for cards by user? Or looking to find team members? Either way I think you'd use emails. We never use the 32-digit IDs for users like we use for cards or collections, the unique ID for a user is their email address. We have query language for User Expressions used to filter cards associated for specific users using their emails - example would be `creatorId = ""` cards created by Gary (see query language documentation for more details.)
4. *We're wondering why `dateCreated` is required as part of the `verifier` object?* What API call is this for? Curious why this would be required as well
5. *SDK?* In Q2, we are focusing on improving our documentation with more endpoints exposed and writing new use cases on our developer page, so unfortunately we are not focusing on any SDK research/build out this quarter.
View original
1. *Can we work around having to update the card content when changing the verifier through the API?* You can do a POST call to this url `https://api.getguru.com/api/v1/cards/{cardid}/verifiers/` to change the verifier and that doesn't make a new version of the card.
2. *Why is `Preferred Phase` the object for the card title?* Our original thinking (back when Guru was just the extension :exploding_head:) was that cards could have multiple "phrases" associated with them and one would be designated as the "preferred" one and that'd be used as the title. A basic rule of thumb is that we don't want to make object changes that could break other clients solutions, so that is now the object name.
3. *It doesn't appear to be possible to query team members by email, which would be useful.* Are you looking for cards by user? Or looking to find team members? Either way I think you'd use emails. We never use the 32-digit IDs for users like we use for cards or collections, the unique ID for a user is their email address. We have query language for User Expressions used to filter cards associated for specific users using their emails - example would be `creatorId = "
4. *We're wondering why `dateCreated` is required as part of the `verifier` object?* What API call is this for? Curious why this would be required as well
5. *SDK?* In Q2, we are focusing on improving our documentation with more endpoints exposed and writing new use cases on our developer page, so unfortunately we are not focusing on any SDK research/build out this quarter.
. I checked with our engineering team and they think the best way would be to use the user token of the individual you are setting as the verifier (which means you would need to have Admin privileges to issue individual tokens via the API). One of our engineers is working on providing some documentation so we can share this workaround with you.
