Sanoflow API Secret

the sanoflow api secret is used to securely generate access tokens for authenticating and sending external api requests to the sanoflow platform this allows developers and third party systems to integrate with sanoflow using authorized, controlled access once created, the secret will be displayed only once, and should be stored securely for more advanced usage, refer to the api documentation linked within the interface getting here log in to your sanoflow account from the left hand menu, go to settings > integrations select the add channel tab under the other section step 1 navigate to integrations log in to your sanoflow account click on settings from the left hand menu select integrations and locate sanoflow api secret under the "other" category click the + add button next to sanoflow api secret configuration steps to create a new api secret api secret name enter a name to identify the secret use something descriptive (e g , “crm integration” or “webhook sync”) to easily recognize its purpose access token type choose the type of token you want to generate short term best for time limited sessions or temporary access long term use for persistent, ongoing access without frequent re authentication expire token after set the lifespan of the generated token for short term access, options like 1 hour, 24 hours, etc , are available after this period, a new token must be generated click save once saved, your secret will be displayed once be sure to copy and store it securely, as it cannot be retrieved again best practices store secrets securely use a password manager or secure environment variable storage use descriptive names to easily manage and revoke secrets when needed keep expiry short for temporary integrations, and rotate secrets periodically for added security faqs where do i use the api secret? the api secret is used to generate an access token, which you then include in your api requests for authentication can i see the secret again after saving? no for security reasons, the secret is shown only once during creation make sure to store it in a secure location is there detailed developer documentation? yes you can access the full api docs via the “api docs” button within the interface can i revoke an api secret after it's been created? yes, you can revoke an api secret at any time from the integrations page once revoked, it can no longer be used to generate access tokens what’s the difference between short term and long term tokens? short term tokens are ideal for temporary or limited access integrations and automatically expire long term tokens remain valid for ongoing use until manually revoked or expired can i create multiple api secrets for different integrations? yes, you can create multiple api secrets, each with its own name, purpose, and expiration settings this helps manage access by integration or team what happens if i forget to copy the secret after creation? you’ll need to delete the existing one and generate a new api secret always store it securely when first created can i track which requests are using a specific api secret? currently, sanoflow does not provide granular request level tracking per secret, but access logs may show token based activity for auditing is there a rate limit for using the api with an access token? yes, depending on your plan and use case, rate limits may apply refer to the api documentation for specifics can api secrets be used for both read and write operations? yes, api secrets can be used for full access, including reading data, writing data, and triggering actions, unless otherwise restricted by scope in future updates