How to get Stripe API key?
Here are the steps to acquire API key from Stripe.
Step-by-step walkthrough: How to get Stripe API Key
Go to Stripe Dashboard
Click Developers
in the bottom left corner in Stripe Dashboard Page.
Go to API Keys
In the top-left corner, click API keys.
Click restricted key
Click on the ”+ Create restricted key” button.
Give Third Party Access
Select 3rd party access and click on Continue.
Give Third Party Access
Enter Superjoin’s details and check the “Customise permissions for this key” checkbox and click on “Create Restricted Key”.
Set a name for the key and manage the permissions
Choose a Key name, and select permissions based on what data you need to access. Below is a suggested set of permissions that will work well with Superjoin, but you can customize these based on exactly what data you want to integrate.
Recommended Permissions Table
Below is a comprehensive table of suggested permissions for your Stripe Restricted API key. You can adjust these based on what specific data you want to access through Superjoin.
Note: Most resources are set to “Read” permission to allow accessing data while maintaining security by not allowing write operations. Resources marked as “None” are typically not needed for data integration purposes.
Category | Resource Type | Permissions |
---|---|---|
Core Resources | ||
Core | Apple Pay Domains | Read |
Core | Balance | Read |
Core | Balance transaction sources | Read |
Core | Balance Transfers | Read |
Core | Charges | Read |
Core | Confirmation token | None |
Core | Confirmation token (client) | None |
Core | Customers | Read |
Core | Customer session | Read |
Core | Disputes | Read |
Core | Ephemeral keys | None |
Core | Events | None |
Core | Files | None |
Core | Funding Instructions | None |
Core | Payment Intents | None |
Core | Payment Methods | Read |
Core | Payment Method Domains | Read |
Core | Payouts | Read |
Core | Products | Read |
Core | Setup Intents | None |
Core | Shipping Rates | Read |
Core | Sources | Read |
Core | Test clocks | None |
Core | Tokens | None |
Billing Resources | ||
Billing | Coupons | Read |
Billing | Promotion Codes | Read |
Billing | Credit notes | Read |
Billing | Customer portal | Read |
Billing | Invoices | Read |
Billing | Prices | Read |
Billing | Subscriptions | Read |
Billing | Quote | Read |
Billing | Tax IDs | Read |
Billing | Tax Rates | Read |
Billing | Usage Records | Read |
Billing | Meter Events | Read |
Billing | Meter Event Adjustments | Read |
Checkout Resources | ||
Checkout | Checkout Sessions | Read |
Connect Resources | ||
Connect | Application Fees | None |
Connect | Login Links | None |
Connect | Account Links | None |
Connect | Top-ups | None |
Connect | Transfers | None |
Orders Resources | ||
Orders | Orders | Read |
Orders | SKUs | Read |
Reporting Resources | ||
Reporting | Report Runs and Report Types | Read |
Tax Resources | ||
Tax | Tax Calculations and Transactions | Read |
Tax | Tax Settings and Registrations | Read |
Issuing Resources | ||
Issuing | Authorizations | None |
Issuing | Cardholders | None |
Issuing | Cards | None |
Issuing | Disputes | None |
Issuing | Tokens | None |
Issuing | Token Network Data | None |
Issuing | Transactions | None |
Issuing | Issuing Settlement | None |
Other Resources | ||
Sigma | Sigma API Permission | None |
Financial Connections | Financial Connections | None |
Identity | Verification Sessions and Reports | None |
All Webhook | Webhook Endpoints | None |
Stripe CLI | Debugging tools | None |
Payment Links | Payment Links | None |
Terminal | Configurations | None |
Terminal | Locations | None |
Terminal | Readers | None |
Terminal | Connection Tokens | None |
Radar | Reviews | None |
Climate | Climate Orders | None |
Create Key
Click on Create key. You may be prompted to enter a confirmation code sent to your mobile or email address.
The permissions table above provides a suggested configuration that works well for most Superjoin integrations with Stripe. You can modify these permissions based on what specific data you want to access through your integration. In general, Read-only permissions are safest and sufficient for data integration purposes.