curl -X POST 'https://collab.enavvarje.se/plugins/playbooks/api/v0/playbooks' -H 'Authorization: Bearer tokenjjj' -d '{"title": "Cloud PlaybookRuns", "description": "A playbook to follow when there is a playbook run regarding the availability of the cloud service.", "reminder_timer_default_seconds": 10, "team_id": "teamid","create_public_playbook_run": true,"checklists": [{"title": "Triage issue","items": [{"title": "Gather information from customer."}]}]}'
and get “not authorized” still. The same token can list playbooks via the api and create in the web gui… i’m sure it’s a detail i’m missing here
I just recognized that the API documentation for playbooks is in a pretty bad state, so you don’t even have a fair chance to get this fixed on your own I was also unable to create a playbook using your payload on my local system, also always only got the Not authorized message until I found out that this is a licensing issue and you have to add the undocumented public parameter to the payload and set it to true.
Here are two examples of minimal payloads, the first one showing the Not authorized message and the second one working (creating a playbook without title, which is possible for whatever reason…):
Thank you so much! Adding the public-parameter enabled me to create the playbook. However, this poses a new question that maybe this is the wrong forum-section for. But I’m running the team/free-version at this time. Is it not supposed to work in that version?
From what I found out, private playbooks seem to be a paid feature, but when I found out about the discrepancy today, I already alerted the docs team and am waiting for their feedback. As soon as I know what’s going on, I’ll let you know.