Use Environments for testing and authentication
isProd | Name | Description |
---|---|---|
false | development | Use this default environment, and it’s associated test API keys, as you build with Flatfile. |
true | production | When you’re ready to launch, create a new environment and swap out your keys. |
publishableKey
and secretKey
are specific to an environment therefore to create a new Environment, you’ll have to use a personal access token.
accessToken
. You can present that as your Bearer token
in place of the secretKey
.magic_link
: This method dispatches an email to your guests, which includes a magic link to facilitate login.shared_link
: This method transforms the Space URL into a public one, typically used in conjunction with embedded Flatfile.guestAuthentication
be left unspecified, both magic_link
and shared_link
types are enabled by default.
It’s important to note that guestAuthentication
settings can be applied at both Environment and Space levels. However, in case of any conflicting settings, the authentication type set at the Space level will take precedence over the Environment level setting. This flexibility enables customization based on specific needs, ensuring the right balance of accessibility and security.
Type | Id | Description |
---|---|---|
Secret key | sk_23ghsyuyshs7dcrty | On the server-side: Store this securely in your server-side code. Don’t expose this key in an application. |
Publishable key | pk_23ghsyuyshs7dcert | On the client-side: Can be publicly-accessible in your application’s client-side code. Use when embedding Flatfile. |