Skip to content

Docs - Remove the "Manage API Keys and Webhooks programatically" page #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bassgeta opened this issue May 9, 2025 · 4 comments
Closed
Assignees

Comments

@bassgeta
Copy link

bassgeta commented May 9, 2025

Problem

Devs get confused how to manage API keys and webhooks.

Solution

Remove the Manage API Keys and Webhooks programatically page from the docs.

History

Old Issue description:

As mentioned in this issue we need to decide if we want to hide the page from the docs, and if we're going to do it, let's open a PR and close this issue.

Opening this for visibility.

@MantisClone
Copy link
Member

I lean towards removing it - even though the Gitbook page is more clear and the risk of misunderstanding is lower.
It's OK to push app builders to use the portal to manage their API keys and webhooks.

@MantisClone
Copy link
Member

Per meeting today with The Accountant Quits (TAQ), their developer clicked the programmatic page first. WE should remove it.

@MantisClone
Copy link
Member

I updated the Title and description.

@MantisClone MantisClone changed the title Docs - Decide what to do with the "Manage API Keys and Webhooks programatically" page and commit Docs - Remove the "Manage API Keys and Webhooks programatically" page May 21, 2025
@MantisClone MantisClone moved this from 🆕 New to ✅ Done in Request Network Tech Backlog May 22, 2025
@MantisClone MantisClone closed this as completed by moving to ✅ Done in Request Network Tech Backlog May 22, 2025
@MantisClone
Copy link
Member

Implemented in 19b3bfa

@MantisClone MantisClone self-assigned this May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants