{"templateId":"openapi_docs","versions":[{"version":"v1","label":"v1","link":"/api-reference/merchant-api-keys","default":true,"active":false,"folderId":"1b9c9f54"},{"version":"v2","label":"v2 (Beta)","link":"/api-reference/v2/merchant-api-keys","default":false,"active":true,"folderId":"1b9c9f54"}],"sharedDataIds":{"openAPIDocsStore":"oas-api-reference/@v2/index.yaml","sidebar":"sidebar-sidebar.yaml__api-reference_v2"},"props":{"definitionId":"api-reference/@v2/index.yaml","dynamicMarkdocComponents":[],"baseSlug":"/api-reference/v2","seo":{"title":"Merchant API Keys","siteUrl":"https://developer.flute.com","description":"API keys may be managed programmatically.\nThis includes creating and deleting API keys.\nThis is the same capability as through the partner and merchant dashboards.\n\nHow the API keys are managed depends on the source of the API token used for the endpoints.\nThere are two sources: Partner and merchant.\n* A partner API key used to create the API token affects only merchants associated with the partner.\nThe partner can manage the API keys for their individual merchants.\nA partner API key can be created only in the partner dashboard.\n* A merchant API key used to create the API token affects only that one merchant.\nThis includes both merchants associated with a partner and standalone merchants (those not associated with any partner).\n\nEach Merchant API Key endpoint explains the details of using either API token source.\n\nThe API keys are specific to a single merchant.\nThey are not interchangeable from among different merchants, even if they are each associated with the same partner.\nThat is, merchants cannot use API keys from any other merchant.\nStandalone merchants (those not associated with any partner) manage their API keys directly.\n\nMerchant API keys are required only if the merchant application or account needs to integrate with the API suite.\nA merchant API key is required to create API tokens (also called access tokens), needed to make endpoint calls.\nExcept for the Merchant API Key endpoints, only merchant API tokens (API tokens created from a merchant API key) can be used with any other endpoint.\nPartner API keys cannot be used to create API tokens otherwise.\nTo generate an API token from an API key, see <a href=\"#get-oauth-token\" style=\"text-decoration: underline;\">GET /oauth-token</a>.\n\nThe number of API keys is determined by the partner or standalone merchants.\nThey may have as many or as few as required.\nFor more information about API keys, see <a href=\"/docs/getting-started/api-authentication\" target=\"_blank\">Creating an API Key</a>.\n\nThis Merchant API Key group consists of the following endpoints:\n* To list available keys, see `GET /v2/api-keys`\n* To create an API key, see `POST /v2/api-keys`\n* To revoke an API key, see `DELETE /v2/api-keys/{clientId}`","lang":"en-US","llmstxt":{"hide":true,"excludeFiles":[]}},"itemId":"merchant-api-keys","disableAutoScroll":true,"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"developer.flute.com","port":4000,"ipAddress":"216.73.217.153"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/api-reference/v2/merchant-api-keys","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}