Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DEVDOCS-4695 [new]: Store-level API accounts, add authorized users #382

Merged
merged 4 commits into from
Jul 23, 2024
Merged

DEVDOCS-4695 [new]: Store-level API accounts, add authorized users #382

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
eaff5cf
specify authorized user
bc-andreadao Jul 19, 2024
7110e30
test
bc-andreadao Jul 19, 2024
57715e4
remove extra space
bc-andreadao Jul 22, 2024
3bd7a6d
active voice
bc-andreadao Jul 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/integrations/apps/guide/auth.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ It may be more appropriate for your application to use an API client to handle t

<Callout type="info">
#### Store owner access_token constraint
Typically, only [store owners](https://support.bigcommerce.com/s/article/Store-API-Accounts#creating) and authorized users can create API accounts and `access_token`s for a store. However, when an app is approved to be publicly available for additional stores to install, it can generate `access_token`s *on behalf* of store owners.
Typically, only [store owners](https://support.bigcommerce.com/s/article/Store-API-Accounts#creating) and authorized users can create API accounts and `access_token`s for a store. However, when an app is approved to be publicly available for additional stores to install, it can generate `access_token`s *on behalf* of store owners and authorized users.
</Callout>

## Overview
Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/apps/guide/types.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ keywords: app extensions

# Types of Apps

The first step when developing an app is deciding which type of app to develop. The two types of apps, single-click and connector, are defined by the method of authentication. [Single-click](#single-click) apps use an OAuth Authorization Code Grant flow. [Connector apps](#connector) require store owners to manually generate and configure store API credentials. In addition to the authentication method, apps can differ by [visibility](#visibility).
The first step when developing an app is deciding which type of app to develop. The two types of apps, single-click and connector, are defined by the method of authentication. [Single-click](#single-click) apps use an OAuth Authorization Code Grant flow. [Connector apps](#connector) require store owners or authorized users to manually generate and configure store API credentials. In addition to the authentication method, apps can differ by [visibility](#visibility).

## Single-Click

Expand All @@ -22,7 +22,7 @@ Once granted, the app can request a permanent `access_token` for making REST API
Single-click apps can use [App Extensions](/docs/integrations/apps/app-extensions).

## Connector
Connector apps use manual OAuth token creation instead of the single-click app flow. Store owners manually generate [store-level API credentials](/docs/start/authentication/api-accounts#revoking-store-level-api-credentials) and enter them into the app's configuration. While single-click apps are recommended, the following use cases might not be compatible:
Connector apps use manual OAuth token creation instead of the single-click app flow. Store owners and authorized users manually generate [store-level API credentials](/docs/start/authentication/api-accounts#revoking-store-level-api-credentials) and enter them into the app's configuration. While single-click apps are recommended, the following use cases might not be compatible:
bc-andreadao marked this conversation as resolved.
Show resolved Hide resolved

- Customized integrations that vary per store.
- Integrations that do not provide any content for an iFrame.
Expand Down
Loading