Get help

:wave: Hey all! I'm trying to convince my Engineering and Product Teams that we should use the *Guru Manual API to feed our new Dev site into Guru.* Did anyone have any winning arguments that helped make the case? @klecornu shared some great examples with me yesterday, so I know a few of you have done it! Would love some additional pro tips.

Hey Team :wave: I'm working with one of our devs to build out an MVP for automating card verification when a user adds a card URL to a specific field in Zendesk. It's built on Rails. We've a couple of questions we're hoping you could answer. We can't find any reference to the verifier endpoint in the API docs. - Would it be possible to get an example of a POST updating a cards verifier via the `https://api.getguru.com/api/v1/cards//verifiers/` endpoint? An example in Ruby would be amazing, but curl would be fine too. - What are the required fields for this request? - We're also wondering if it's possible to update the verification interval without also having to "update" the `preferredPhrase` or content by sending the same current value? Our previous MVP used the `https://api.getguru.com/api/v1/facts//extended` endpoint but we'd like to work around updating the title/content with every request. Can you recommend an alternative?

Another question about API responses. Does anyone know whether it's possible to get a list structure of ALL users who have modified a card, rather than just the record of the *last* person to modify it? I'm keen to understand the full audit trail of a card's history. Thank you!

Hi team, I think that I have found a bug in the API. I am using the search/query with success in our code. I have noticed that it *doesn't* return any archived card details when we use the simple `q` query parameter. I know that there is another query parameter called `showArchived` which takes true or false. When I set this extra parameter to true, then it *only* returns archived cards: that's correct behavior. When I set it to false, it *only* returns non-archived cards: that correct behavior. However, when I *omit* the `showArchived` parameter, I believe that it should return BOTH archived and non-archived cards. Unfortunately, this is not the case. It does not return any archived cards. Please can you investigate? If this behavior is intentional, how am I supposed to return both archived and non-archived cards without making two separate API calls…? Thank you :slightlysmilingface:

Not sure if someone has already said this. My HR person is wanting me to use Trainual in addition to Guru (or instead of). The reason being is that she wants us to use Trainual for our employee handbook so that people can sign off on having reviewed different aspects of it. Does Guru do this or is there anything on the roadmap to have people sign off on having reviewed cards? I need to document that policies have been reviewed somehow. I COULD work around it... but it would be a bit cumbersome. Any ideas? Thanks!

Hey folks, first time caller long time fan :wave: 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 suggestion

Hi friends! I was wondering if an SOP exists for a best practice on "*How to write a good Guru Card*". In short, we are running into a situation in which employees are creating cards and just throwing links to other documentation within the card without clear explanation of what that link even is in the first place. Thanks!

hi - add a task directly from slack to create a card with XYZ information :tada:

Hi! I have an API question! I want to set up a way to pipe super duper old & dusty unverified cards into a Slack channel using Workato. In theory I can do this if I can update a Google spreadsheet using API calls, but that's where I'm getting stuck. Right now, I use the Card Manager to look a set of parameters to pull it manually - but I'd like to take myself out of the process and operationalize this process! Has anyone done anything similar to this?

• More info. on the Guru Developer Network, including API documentation, how to sign up for a developer account, and examples of how others are using the API: https://www.getguru.com/developers • Deck from today: https://app.getguru.com/card/crkRA9Xi/121819-Virtual-Guru-the-Gathering-online-Extending-Guru-through-the-API • Questions for @mhouston about the API and/or Guru Developer Network? Feel free to reach out here in Slack, or via email: