Get Terminal
Retrieve the current configuration and metadata for one terminal.
Purpose
Display device details in an admin UI.
Verify a terminal’s webhook URL, tender types, or enabled status before updating.
Troubleshoot by confirming whether the terminal is enabled or disabled.
Endpoint
Required header
Authorization
Bearer eyJhbGciOiJS…
Same access token used for other Terminal Management calls.
Path parameter
id
string
Terminal identifier returned by Create Terminal or List Terminals.
Request example
(No request body.)
Response example
Field descriptions
id
string
Terminal identifier.
name
string
Friendly display name.
description
string
Additional text shown in dashboards.
merchantId
string
Merchant that owns this terminal.
merchantLocationId
string
Optional sub-location (e.g., store number).
displayLogo
boolean
Show the Bead logo on hosted pages for this terminal.
webhookUrl
string | null
Device-level webhook URL.
isEnabled
boolean
false
= terminal is disabled and cannot create new payments.
tenderTypes
array
Payment methods accepted by this device.
created
string
UTC ISO-8601 timestamp when the terminal was created.
updated
string
UTC ISO-8601 timestamp of the last modification.
Response codes
200 OK
Terminal found
JSON as above
404 Not Found
Terminal id unknown
{ "code": "TerminalNotFound", "message": "Terminal {id} does not exist." }
401 / 403
Invalid or expired token
Standard auth error payload
Usage tips
Pre-update check – Load the terminal first to confirm its current
webhookUrl
ortenderTypes
before calling Set Webhook or Update Terminal.Status dashboards – Display
isEnabled
,tenderTypes
, andupdated
to help ops teams spot mis-configured devices.Audit trails – Store the response externally when doing compliance audits; the timestamps provide proof of device creation and edits.
Related pages
Create Terminal
Add a new device.
List Terminals
Retrieve all devices (optionally filtered by merchant).
Delete Terminal
Remove a device that is no longer needed.
Last updated