![]() ![]() For example, for a subdomain, – Default Value: Include a value for this field to be used as a fallback. – Input Format: (optional) Help users figure out exactly what piece of data you need them to enter. If there is no direct link, include as clear of directions as possible to help users find the API key. – Help Text: Include a direct URL formatted with Markdown where users can obtain their API key from your app. – Type: All input fields use the string text field by default select password instead if you would like to obscure the data as users enter it. – Required? (checkbox): Check if this field is required for successful authentication. – Label: A human-friendly name for this field that will be shown to users in the authentication form. Fill in the optional fields, as appropriate, especially the Label:.Add the most commonly needed fields first, in the order users expect, as you cannot reorder fields once added.Īdd the required Key, the name your API uses to reference this field. API keys especially are often hidden under settings menus and you’ll need to include those details in your input form’s help text.Ĭlick the Add Fields button and fill in the details for your field. Note any details users may need on how to find that data in your app. Check your API documentation for what fields are required, including user or account names, domains, and more. Add authentication input fields where users will enter their API key and any other required authentication details.Open the Authentication tab in Zapier visual builder and select API key. ![]() Since API Key authentication allows you to create a custom input form, you can use it for any custom authentication type with username and password-based logins that don’t fit other authentication scheme types. Use API Key authentication if your API primarily uses an API key to identify accounts, especially with apps for weather, maps, content verification, file conversion, and other data tools that require a key for access to the service but do not contain user-specific content. In your Zapier integration using API Key authentication, the API key-and optionally any other data your API needs-is included every time a Zap step runs.Įxample API Key auth screen for users inside Zapier Add integration branding in Platform CLIĪPI Key authentication passes along a user-entered API Key with every API call.Manage a legacy web builder integration in Platform UI.Changes to your API can impact your integration.Update perform method for polling trigger.Change trigger from polling to REST Hook.Planning and implementing integration changes.Add an instant trigger using REST Hooks in Zapier Platform CLI.Test and monitor your integration in your Zapier account.Use dynamic dropdowns in Zapier Platform CLI.Output data, defining sample data and output fields.Send or receive dynamic user-defined fields through your API.Add input fields to triggers and actions.Compute a field from the data of the Test API call.Use computed fields in OAuth or Session Authentication.Add authentication with Session Authentication.Add authentication with Basic Authentication.Reference user-entered details with data bundles. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |