Update Terminal
Updates an existing terminal configuration.
Endpoint
PUT https://api.test.devs.beadpay.io/Terminals/{id}
Authentication
Use your admin API key in the request header for terminal management operations.
Request headers
X-Api-Key
{adminApiKey}
Content-Type
application/json
Accept
application/json
Path parameter
id
string
Terminal identifier returned by Create Terminal, List Terminals, or Get Terminal.
Request body
name
string
Yes
Friendly name for the terminal.
description
string
Yes
Terminal description.
displayLogo
boolean
Yes
Controls whether the logo is displayed where supported.
isEnabled
boolean
Yes
Controls whether the terminal can create new payments.
tenderTypes
array
No
Tender types enabled for this terminal.
extendRedirectUrl
boolean
No
Adds paymentPageId as a query parameter to the redirect URL.
maxTransactionAmount
number
No
Optional maximum transaction amount for this terminal.
useSandboxSharedWalletcannot be set or changed via this endpoint. This Sandbox-only setting is applied at terminal creation time only. If a terminal is missinguseSandboxSharedWallet: trueand USDC payments are failing as a result, the terminal must be recreated with the flag included. See Create Terminal.
Example request
Example response
Notes
Use this endpoint to update terminal settings such as name, description, enabled status, tender types, branding, and transaction limits.
useSandboxSharedWalletis not editable via this endpoint. It is a creation-time setting. If it is missing from an existing terminal, recreate the terminal with"useSandboxSharedWallet": trueusingPOST /Terminals. Terminals created automatically from a boarding approval have this set correctly by default.Use your admin API key for terminal management operations.
Use the terminal payments API key for payment activity performed by that terminal.
Treat
apiKey.secretas sensitive and do not expose it in logs or client-side code.Updating a terminal does not replace the terminal payments API key. If you need to rotate the terminal key, use the terminal API key reset operation.
Response codes
200
Terminal updated successfully.
202
Update accepted for processing.
204
Update completed with no response body.
400
The request body is invalid or missing required fields.
401
The admin API key is missing or invalid.
403
The caller is authenticated but not permitted to update the specified terminal.
404
No terminal was found for the supplied id.
409
A conflicting terminal state prevented the update.
Related operations
Last updated