# Flute Test - The API Reference Guide Build date: 9.23.2026 9:59 AM
⚠️ Beta Release The v2 API is currently in active development. Functionality, request and response formats, field names, and behavior may change before the stable release. Review the release notes regularly for updates. Contact [Developer Support](mailto:developer@flute.com?subject=About%20Flute%20API) for further details.
Version: V2 Beta ## Servers Sandbox environment ``` https://sandbox.api.flute.com ``` Production environment ``` https://api.flute.com ``` ## Security ### Bearer Specify the authorization token. Type: http Scheme: bearer Bearer Format: JWT ## Download OpenAPI description - [Flute Test - The API Reference Guide](https://developer.flute.com/_bundle/api-reference/@v2/flute-v2.yaml) ## Getting Started - [Creating a Flute Account](https://developer.flute.com/api-reference/v2/flute-v2/getting-started/creating-a-flute-account.md): # Creating a Flute Account Before using Flute payment capabilities or the Flute API suite, you must create a Flute sandbox account. All development and testing occurs first in a sandbox account. The s - [Developing in the Sandbox Environment](https://developer.flute.com/api-reference/v2/flute-v2/getting-started/developing-in-the-sandbox-environment.md): # Developing in the Sandbox Environment The sandbox account is a fully isolated account that mirrors production behavior. It does not process real transactions. Use the sandbox for all testing and app - [Going Live](https://developer.flute.com/api-reference/v2/flute-v2/getting-started/going-live.md): # Going Live When your product is ready to be deployed live, the Flute support team will work with you to ensure compliance. This compliance follows the production readiness checklist. It ensures the ## API Suite Fundamentals - [baseURL Environments](https://developer.flute.com/api-reference/v2/flute-v2/api-suite-fundamentals/baseurl-environments.md): # baseURL Environments Flute provides different environments to run endpoints. **Sandbox** The sandbox environment is for development and testing. No payments, charges, or invoices will be enforced. I - [OAuth Token baseURLs](https://developer.flute.com/api-reference/v2/flute-v2/api-suite-fundamentals/oauth-token-baseurls.md): # OAuth Token baseURLs The OAuth token endpoint (used to generate an API token) uses its own base URL, separate from the API baseURLs above. **Sandbox** Endpoint: `POST https://sandbox.oauth.api.flut - [Payment Flow](https://developer.flute.com/api-reference/v2/flute-v2/api-suite-fundamentals/payment-flow.md): # Payment Flow The following is a generalized workflow. ## Card Present / Card Not Present ## Flute-Defined Enums - [Account Holder Types (AccountHolderType)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/account-holder-types-(accountholdertype).md): #### Account Holder Types (AccountHolderType) Identifies whether the account holder is a business or an individual. | Id | Name | Explanation | | --- | --- | --- | | 1 | Business | The account is hel - [Account Types (AccountType)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/account-types-(accounttype).md): #### Account Types (AccountType) Identifies the type of bank account used for an ACH transaction. | Id | Name | Explanation | | --- | --- | --- | | 1 | Checking | A standard checking account used for - [Credit Card Types (CardBrand)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/credit-card-types-(cardbrand).md): #### Credit Card Types (CardBrand) Identifies the card network associated with a payment card. | Id | Name | Explanation | | --- | --- | --- | | 1 | Visa | Card issued on the Visa network. | | 2 | M - [Transaction Creator Types (SourceType)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/transaction-creator-types-(sourcetype).md): #### Transaction Creator Types (SourceType) Identifies the method or channel used to create an ACH transaction. | Id | Name | Explanation | | --- | --- | --- | | 1 | Portal | Created from the Flute - [Payment Method Types (PaymentMethodType)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/payment-method-types-(paymentmethodtype).md): #### Payment Method Types (PaymentMethodType) Identifies the payment method used for a transaction. | Id | Name | Explanation | | --- | --- | --- | | 1 | Card | Payment made with a credit or debit ca - [Payment Processor Types (PaymentProcessorType)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/payment-processor-types-(paymentprocessortype).md): #### Payment Processor Types (PaymentProcessorType) Identifies the payment processor used to route a transaction. | Id | Name | Explanation | | --- | --- | --- | | 1 | TSYS | Transactions are routed - [Payment Session Statuses (PaymentSessionStatusDto)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/payment-session-statuses-(paymentsessionstatusdto).md): #### Payment Session Statuses (PaymentSessionStatusDto) Indicates the current status of a payment session. | Id | Name | Explanation | | --- | --- | --- | | 1 | Created | The payment session has been - [Transaction Statuses (TransactionStatus)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/transaction-statuses-(transactionstatus).md): #### Transaction Statuses (TransactionStatus) Indicates the current status of a transaction, along with the actions still available for that status. | Status Code | Status | Description | Available A - [Transaction Types (TransactionType)](https://developer.flute.com/api-reference/v2/flute-v2/flute-defined-enums/transaction-types-(transactiontype).md): #### Transaction Types (TransactionType) Identifies the type of operation performed for a transaction. | Id | Name | Explanation | | --- | --- | --- | | 1 | Authorization | Reserves funds on the car ## API Token Authorization - [POST /oauth2/token](https://developer.flute.com/api-reference/v2/flute-v2/api-token-authorization/get-oauth-token.md): POST {{authBaseURL}}/oauth2/token This endpoint obtains or refreshes an API token. Each Flute endpoint (with the exception of this authentication endpoint) requires an API token, also called an access ## Customers - [GET /v2/customers](https://developer.flute.com/api-reference/v2/flute-v2/customers/flute-v2-get-customers.md): GET {{baseURL}}/v2/customers This endpoint lists customers. Results are returned in pages of `pageSize` items, with a default of 20 and a maximum of 100 per page. The `pageIndex` parameter selects whi - [POST /v2/customers](https://developer.flute.com/api-reference/v2/flute-v2/customers/flute-v2-post-customers.md): POST {{baseURL}}/v2/customers This endpoint creates a customer record for the authenticated merchant. Only `firstName` and `lastName` are required. Everything else, such as company name, email, mobile - [GET /v2/customers/{customerId}](https://developer.flute.com/api-reference/v2/flute-v2/customers/flute-v2-get-customers-customerid.md): GET {{baseURL}}/v2/customers/{{customerId}} This endpoint retrieves a customer by ID. See Also: To create a new customer, see POST /v2/customers. To list customers, see GET /v2/customers. To update a - [PATCH /v2/customers/{customerId}](https://developer.flute.com/api-reference/v2/flute-v2/customers/flute-v2-patch-customers-customerid.md): PATCH {{baseURL}}/v2/customers/{{customerId}} This endpoint performs a partial update to an existing customer's record. Send only the fields needed to be changed. Any field left out of the request is - [DELETE /v2/customers/{customerId}](https://developer.flute.com/api-reference/v2/flute-v2/customers/flute-v2-delete-customers-customerid.md): DELETE {{baseURL}}/v2/customers/{{customerId}} This endpoint deletes the customer identified by `customerId`. The deletion is permanent. A later call to this customer's `customerId`, such as `GET /v2/ ## Merchant API Keys - [GET /v2/api-keys](https://developer.flute.com/api-reference/v2/flute-v2/merchant-api-keys/flute-v2-get-api-keys.md): GET {{baseURL}}/v2/api-keys This endpoint lists a merchant's API keys. Each entry returns the key's `clientId`, `merchantId`, and `apiKeyName`. It does not return the key's secret. A partner-level API - [POST /v2/api-keys](https://developer.flute.com/api-reference/v2/flute-v2/merchant-api-keys/flute-v2-post-api-keys.md): POST {{baseURL}}/v2/api-keys Creates a new API key for a merchant. If the API token used for this endpoint was created from a partner API key, an API key can be created only for merchants associated w - [DELETE /v2/api-keys/{clientId}](https://developer.flute.com/api-reference/v2/flute-v2/merchant-api-keys/flute-v2-delete-api-keys-clientid.md): DELETE {{baseURL}}/v2/api-keys/{{clientId}} This endpoint revokes a merchant API key. Once revoked, the key's `clientId` and `clientSecret` no longer authenticate API requests. A partner-level API tok ## Payment Links - [GET /v2/payment-links](https://developer.flute.com/api-reference/v2/flute-v2/payment-links/flute-v2-get-payment-links.md): GET {{baseURL}}/v2/payment-links This endpoint lists payment links for the authenticated merchant. The response is a paginated set of payment links. Results are returned in pages of `pageSize` items, - [POST /v2/payment-links](https://developer.flute.com/api-reference/v2/flute-v2/payment-links/flute-v2-post-payment-links.md): POST {{baseURL}}/v2/payment-links This endpoint creates a new payment link. A `paymentMethods` entry without `processorId` is pinned to the merchant's default active processor of that type at creation - [GET /v2/payment-links/{paymentLinkId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-links/flute-v2-get-payment-links-paymentlinkid.md): GET {{baseURL}}/v2/payment-links/{{paymentLinkId}} This endpoint retrieves a payment link by ID. See Also: To list payment links, see GET /v2/payment-links. To create a new payment link, see POST /v2/ - [PATCH /v2/payment-links/{paymentLinkId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-links/flute-v2-patch-payment-links-paymentlinkid.md): PATCH {{baseURL}}/v2/payment-links/{{paymentLinkId}} This endpoint updates a payment link. `paymentMethods` is replaced wholesale when present. A type absent from the new array stops being accepted. A - [DELETE /v2/payment-links/{paymentLinkId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-links/flute-v2-delete-payment-links-paymentlinkid.md): DELETE {{baseURL}}/v2/payment-links/{{paymentLinkId}} This endpoint deletes a payment link. This marks the payment link as `Inactive`. This in contrast to permanently erasing the link and its history. - [POST /v2/payment-links/{paymentLinkId}/share](https://developer.flute.com/api-reference/v2/flute-v2/payment-links/flute-v2-post-payment-links-paymentlinkid-share.md): POST {{baseURL}}/v2/payment-links/{{paymentLinkId}}/share This endpoint shares a payment link with a customer by SMS or email. This sends the link's URL to the recipient over the selected channel. Onl ## Payment Methods - [GET /v2/payment-methods](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-get-payment-methods.md): Lists saved card and ACH payment methods on file for a customer, with support for filtering, sorting, and pagination. GET {{baseURL}}/v2/payment-methods This endpoint lists a customer's payment metho - [POST /v2/payment-methods/cards](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-post-payment-methods-cards.md): POST {{baseURL}}/v2/payment-methods/cards This endpoint creates a card (credit or debit) payment method. The card information is tokenized and stored, assigning it to the merchant. Tokenization means - [POST /v2/payment-methods/ach](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-post-payment-methods-ach.md): POST {{baseURL}}/v2/payment-methods/ach This endpoint creates an ACH (automated clearing house) payment method. The ACH account information is tokenized and stored, assigning it to the merchant. Token - [GET /v2/payment-methods/{paymentMethodId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-get-payment-methods-paymentmethodid.md): GET {{baseURL}}/v2/payment-methods/{{paymentMethodId}} This endpoint retrieves a payment method by ID. See Also: To add a new card payment method, see POST /v2/payment-methods/cards. To add a new ACH - [PATCH /v2/payment-methods/{paymentMethodId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-patch-payment-methods-paymentmethodid.md): PATCH {{baseURL}}/v2/payment-methods/{{paymentMethodId}} This endpoint updates a payment method. Renames the payment method. The payment method is identified by `paymentMethodId` within the merchant. - [DELETE /v2/payment-methods/{paymentMethodId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-delete-payment-methods-paymentmethodid.md): DELETE {{baseURL}}/v2/payment-methods/{{paymentMethodId}} This endpoint deletes a payment method. See Also: To list payment methods, see GET /v2/payment-methods. To retrieve a payment method by ID, se - [POST /v2/payment-methods/{paymentMethodId}/set-default](https://developer.flute.com/api-reference/v2/flute-v2/payment-methods/flute-v2-post-payment-methods-paymentmethodid-set-default.md): POST {{baseURL}}/v2/payment-methods/{{paymentMethodId}}/set-default This endpoint set the specified payment method as the default payment method. Only one payment method can be set as the default. Whe ## Payment Sessions - [POST /v2/payment-sessions](https://developer.flute.com/api-reference/v2/flute-v2/payment-sessions/flute-v2-post-payment-sessions.md): POST {{baseURL}}/v2/payment-sessions This endpoint creates a new payment session. This endpoint is Idempotent. See the `idempotency-key` header entry. For more information, see Idempotency. See Also: - [GET /v2/payment-sessions/{paymentSessionId}](https://developer.flute.com/api-reference/v2/flute-v2/payment-sessions/flute-v2-get-payment-sessions-paymentsessionid.md): GET {{baseURL}}/v2/payment-sessions/{{paymentSessionId}} This endpoint retrieves the details of the specified payment session by ID. See Also: To create a new payment session, see POST /v2/payment-ses - [POST /v2/payment-sessions/{paymentSessionId}/cancel](https://developer.flute.com/api-reference/v2/flute-v2/payment-sessions/flute-v2-post-payment-sessions-paymentsessionid-cancel.md): POST {{baseURL}}/v2/payment-sessions/{{paymentSessionId}}/cancel This endpoint cancels a payment session. A payment session can only be canceled successfully if: * The payment session must belong to t ## Ping - [GET /v2/ping](https://developer.flute.com/api-reference/v2/flute-v2/ping/flute-v2-get-ping.md): GET {{baseURL}}/v2/ping This endpoint pings an endpoint to validate the API token is active and valid. Returns 200 OK if the service is reachable. There is no response body. ## POS Transactions - [GET /v2/pos/transactions](https://developer.flute.com/api-reference/v2/flute-v2/pos-transactions/flute-v2-get-pos-transactions.md): GET {{baseURL}}/v2/pos/transactions This endpoint lists POS transactions. Each item in the response contains a reduced transaction object. Fields are limited to the most relevant transaction informati - [POST /v2/pos/transactions](https://developer.flute.com/api-reference/v2/flute-v2/pos-transactions/flute-v2-post-pos-transactions.md): POST {{baseURL}}/v2/pos/transactions This endpoint creates a new card present payment transaction on a semi-Integrated terminal. A semi-integrated terminal is one that is connected to a POS system, ty - [GET /v2/pos/transactions/{posTransactionId}](https://developer.flute.com/api-reference/v2/flute-v2/pos-transactions/flute-v2-get-pos-transactions-postransactionid.md): GET {{baseURL}}/v2/pos/transactions/{{posTransactionId}} This endpoint retrieves a POS transaction by ID. See Also: To list POS transactions, see GET /v2/pos/transactions. To create a new POS transact - [POST /v2/pos/transactions/{posTransactionId}/cancel](https://developer.flute.com/api-reference/v2/flute-v2/pos-transactions/flute-v2-post-pos-transactions-postransactionid-cancel.md): POST {{baseURL}}/v2/pos/transactions/{{posTransactionId}}/cancel This endpoint cancels a POS transaction by ID. This sends a cancellation signal to the gateway to abort an in-progress POS transaction. - [POST /v2/pos/transactions/{posTransactionId}/print-receipt](https://developer.flute.com/api-reference/v2/flute-v2/pos-transactions/flute-v2-post-pos-transactions-postransactionid-print-receipt.md): POST {{baseURL}}/v2/pos/transactions/{{posTransactionId}}/print-receipt This endpoint prints a POS transaction receipt. The terminal must be in semi-integrated mode and available (online and ready). A - [POST /v2/pos/transactions/reversal](https://developer.flute.com/api-reference/v2/flute-v2/pos-transactions/flute-v2-post-pos-transactions-reversal.md): POST {{baseURL}}/v2/pos/transactions/reversal This endpoint reverses a POS transaction. Provide the `originalTransactionId` to reverse a specific transaction. Only card transactions can be reversed th ## Settings - [GET /v2/settings/payment-config](https://developer.flute.com/api-reference/v2/flute-v2/settings/flute-v2-get-settings-payment-config.md): GET {{baseURL}}/v2/settings/payment-config This endpoint lists the payment configuration settings. See Also: To retrieve the contact information, see GET /v2/settings/contact-information. To retrieve - [GET /v2/settings/contact-information](https://developer.flute.com/api-reference/v2/flute-v2/settings/flute-v2-get-settings-contact-information.md): GET {{baseURL}}/v2/settings/contact-information This endpoint lists contact information for the merchant. See Also: To retrieve the payment configuration, see GET /v2/settings/payment-config. To retri - [GET /v2/settings/transaction-autofill](https://developer.flute.com/api-reference/v2/flute-v2/settings/flute-v2-get-settings-transaction-autofill.md): GET {{baseURL}}/v2/settings/transaction-autofill This endpoint lists levels 2 and 3 autofill settings. The additional levels 2 and 3 information must be included in transactions requiring that level. - [PATCH /v2/settings/transaction-autofill](https://developer.flute.com/api-reference/v2/flute-v2/settings/flute-v2-patch-settings-transaction-autofill.md): PATCH {{baseURL}}/v2/settings/transaction-autofill This endpoint updates or sets levels 2 and 3 autofill settings. The additional levels 2 and 3 information must be included in transactions requiring ## Settlements - [GET /v2/settlements/batches](https://developer.flute.com/api-reference/v2/flute-v2/settlements/flute-v2-get-settlements-batches.md): GET {{baseURL}}/v2/settlements/batches This endpoint lists transaction batch settlements. `createdOn` is `null` for the currently open batch, since its record is only materialized once settlement comp - [POST /v2/settlements/batches/close](https://developer.flute.com/api-reference/v2/flute-v2/settlements/flute-v2-post-settlements-batches-close.md): POST {{baseURL}}/v2/settlements/batches/close This endpoint closes the merchant's currently open batch and submits its unsettled transactions for settlement with the specified payment processor. Settl ## Terminals - [GET /v2/terminals](https://developer.flute.com/api-reference/v2/flute-v2/terminals/flute-v2-get-terminals.md): GET {{baseURL}}/v2/terminals This endpoint lists all available terminals for the authenticated merchant. Only active terminals are returned. Terminals in the following conditions are excluded: * Pre-a - [GET /v2/terminals/{terminalId}/status](https://developer.flute.com/api-reference/v2/flute-v2/terminals/flute-v2-get-terminals-terminalid-status.md): GET {{baseURL}}/v2/terminals/{{terminalId}}/status This endpoint Retrieves a merchant's terminal POS status by ID. information includes the connection and network state, hardware info and software ver ## Transactions - [GET /v2/transactions](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-get-transactions.md): GET {{baseURL}}/v2/transactions This endpoint returns a paginated list of settlement batches for the authenticated merchant. Supports filtering by batch status, date range, specific batch identifiers, - [POST /v2/transactions](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions.md): POST {{baseURL}}/v2/transactions This endpoint creates a transaction. This endpoint is Idempotent. See the `idempotency-key` header entry. For more information, see Idempotency. See Also: To list tran - [GET /v2/transactions/{transactionId}](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-get-transactions-transactionid.md): GET {{baseURL}}/v2/transactions/{{transactionId}} This endpoint retrieves a transaction by ID. See Also: To list transactions, see GET /v2/transactions. To create a new transaction, see POST /v2/trans - [POST /v2/transactions/{transactionId}/capture](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-transactionid-capture.md): POST {{baseURL}}/v2/transactions/{{transactionId}}/capture This endpoint captures a transaction. This captures a previously authorized transaction and settling it for the specified amount. It is used - [POST /v2/transactions/{transactionId}/reversal](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-transactionid-reversal.md): POST {{baseURL}}/v2/transactions/{{transactionId}}/reversal This endpoint reverses, or refunds, a transaction. Payment method (card vs ACH) is auto-detected. This endpoint is Idempotent. See the `idem - [POST /v2/transactions/reversal](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-reversal.md): POST {{baseURL}}/v2/transactions/reversal This endpoint refunds or returns funds. This includes refunding to a credit card or provides an ACH credit. See Also: To list transactions, see GET /v2/transa - [POST /v2/transactions/credit](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-credit.md): POST {{baseURL}}/v2/transactions/credit This endpoint refunds or returns funds without a reference. This includes refunding to a credit card or provides an ACH credit. Without a reference means the cu - [POST /v2/transactions/{transactionId}/tip-adjustment](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-transactionid-tip-adjustment.md): POST {{baseURL}}/v2/transactions/{{transactionId}}/tip-adjustment This endpoint adjusts, or adds, for tips to transaction. This may only be used with card-present transactions. Specifically, this is f - [POST /v2/transactions/{transactionId}/ach-hold](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-transactionid-ach-hold.md): POST {{baseURL}}/v2/transactions/{{transactionId}}/ach-hold This endpoint holds an ACH transaction. This endpoint is Idempotent. See the `idempotency-key` header entry. For more information, see Idemp - [POST /v2/transactions/{transactionId}/ach-release](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-transactionid-ach-release.md): POST {{baseURL}}/v2/transactions/{{transactionId}}/ach-release This endpoint releases a held ACH transaction. This endpoint is Idempotent. See the `idempotency-key` header entry. For more information, - [POST /v2/transactions/calculate-amount](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-calculate-amount.md): POST {{baseURL}}/v2/transactions/calculate-amount This endpoint calculates transaction amounts. The amounts are based on the merchant's ZCP (zero cost processing) mode. This includes dual pricing, cas - [POST /v2/transactions/{transactionId}/share-receipt](https://developer.flute.com/api-reference/v2/flute-v2/transactions/flute-v2-post-transactions-transactionid-share-receipt.md): POST {{baseURL}}/v2/transactions/{{transactionId}}/share-receipt This endpoint shares a transaction receipt by SMS. The following is a typical workflow: 1) For authorization: POST /v2/transactions 2) ## Webhooks - [GET /v2/webhooks/endpoints](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-get-webhooks-endpoints.md): GET {{baseURL}}/v2/webhooks/endpoints This endpoint lists all webhook endpoints. The endpoints are for both active and inactive webhooks. See Also: To create a webhook, see POST /v2/webhooks/endpoints - [POST /v2/webhooks/endpoints](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-post-webhooks-endpoints.md): POST {{baseURL}}/v2/webhooks/endpoints This endpoint creates a new webhook endpoint. New endpoints default to `Active` on creation. Only `Active` endpoints are eligible for real event dispatch. See Al - [GET /v2/webhooks/endpoints/{endpointId}](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-get-webhooks-endpoints-endpointid.md): GET {{baseURL}}/v2/webhooks/endpoints/{{endpointId}} This endpoint retrieves a webhook endpoint by ID. See Also: To list all available webhooks, see GET /v2/webhooks/endpoints. To update a webhook, se - [PATCH /v2/webhooks/endpoints/{endpointId}](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-patch-webhooks-endpoints-endpointid.md): PATCH {{baseURL}}/v2/webhooks/endpoints/{{endpointId}} This endpoint updates a webhook endpoint. See Also: To list all available webhooks, see GET /v2/webhooks/endpoints. To retrieve a specified webh - [DELETE /v2/webhooks/endpoints/{endpointId}](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-delete-webhooks-endpoints-endpointid.md): DELETE {{baseURL}}/v2/webhooks/endpoints/{{endpointId}} This endpoint deletes a webhook endpoint. All outstanding pending and scheduled retries for this specified webhook are canceled. References in l - [POST /v2/webhooks/endpoints/{endpointId}/ping](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-post-webhooks-endpoints-endpointid-ping.md): GET {{baseURL}}/v2/webhooks/endpoints/{{endpointId}}/ping This endpoint validates connectivity to the registered endpoint URL. - [GET /v2/webhooks/event-types](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-get-webhooks-event-types.md): GET {{baseURL}}/v2/webhooks/event-types This endpoint lists available webhook event types. The list of available webhook event types are provided by Flute. These are the only events types available to - [GET /v2/webhooks/delivery-logs](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-get-webhooks-delivery-logs.md): GET {{baseURL}}/v2/webhooks/delivery-logs This endpoint lists webhook delivery logs for the merchant account. Results are returned in pages of `pageSize` items, with a default of 20 and a maximum of 1 - [GET /v2/webhooks/delivery-logs/{deliveryLogId}](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-get-webhooks-delivery-logs-deliverylogid.md): GET {{baseURL}}/v2/webhooks/delivery-logs/{{deliveryLogId}} This endpoint retrieves a delivery log by ID. See Also: To list all available webhooks, see GET /v2/webhooks/endpoints. To test a webhook, s - [GET /v2/webhooks/delivery-logs/export](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-get-webhooks-delivery-logs-export.md): GET {{baseURL}}/v2/webhooks/delivery-logs/export This endpoint exports webhook delivery logs as a CSV or JSON file. Query parameters may be combined to filter the exported results. See Also: To list a - [POST /v2/webhooks/delivery-logs/{deliveryLogId}/retry](https://developer.flute.com/api-reference/v2/flute-v2/webhooks/flute-v2-post-webhooks-delivery-logs-deliverylogid-retry.md): POST {{baseURL}}/v2/webhooks/delivery-logs/{{endpointId}}/retry This endpoint manually retries a failed webhook delivery. This is a single try each time. It does not automatically retry multiple times