forked from mrwyndham/fastpocket
40 lines
256 KiB
Markdown
40 lines
256 KiB
Markdown
# How to Create and Configure a Restricted API Key for Fast Pocket
|
|
|
|
Creating a restricted API key is crucial for ensuring the security and proper functionality of Fast Pocket. This guide will walk you through the steps to create a new restricted API key and configure it with the necessary permissions.
|
|
|
|
[](https://youtu.be/3N2jtjBVxc8)
|
|
|
|
## Accessing the Developer Portal
|
|
|
|
To begin, navigate to the developer's portal. This is where you will create a new API key specifically for your Fast Pocket project.
|
|
|
|
|
|
|
|
## Creating a New Restricted API Key
|
|
|
|
Once you're in the developer's portal, follow these steps to create a new API key:
|
|
|
|
1. Click on the option to create a new API key.
|
|
2. Name the new API key. For example, you can name it `fast_pocket_test_demo_one`.
|
|
|
|
|
|
|
|
## Assigning Permissions
|
|
|
|
After naming your API key, you need to assign the appropriate permissions. It's important to ensure that the key has write permissions for most sections to maintain connectivity with Stripe.
|
|
|
|
1. Assign write permissions to all necessary sections.
|
|
2. Ensure that sections which don't require write access are left without it.
|
|
|
|
|
|
|
|
The reason for assigning these permissions is to ensure that Fast Pocket can connect to Stripe without any issues. If you don't assign the correct permissions, you may encounter connectivity problems.
|
|
|
|
## Troubleshooting Tips
|
|
|
|
If you encounter any issues with Fast Pocket, make sure to check the following:
|
|
|
|
1. Verify that you have created a restricted API key.
|
|
2. Ensure that the API key has the correct permissions.
|
|
|
|
 |