Adyen POS Terminal Management API
Browse all Adyen APIs✓ Official Vendor SpecPaymentsPos TerminalapiKey, basic5 EndpointsREST
For Agents
Provision, list, and reassign Adyen POS terminals across merchant accounts and stores via back-office terminal management endpoints.
Use for: Assign a new terminal to a specific store, List all terminals belonging to a merchant account, Find the store that a particular terminal is currently in, Retrieve the model, status, and config of a terminal
Not supported: Does not drive in-store transactions, order new terminal hardware, or push firmware — use only for back-office terminal assignment, listing, and inspection.
The Adyen POS Terminal Management API administers the fleet of payment terminals in an Adyen merchant's estate. The five endpoints assign terminals to merchant accounts or stores, list terminals under an account, fetch the details of a specific terminal, find the account or store a terminal currently belongs to, and list the stores under an account. It is the back-office surface for terminal provisioning and reassignment, separate from the Terminal API that drives transactions.
Install Jentic One Beta
Connect the POS Terminal Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the POS Terminal Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with POS Terminal Management API.
Reassign one or more terminals to a merchant account or store via POST /assignTerminals
List all terminals under a merchant account via POST /getTerminalsUnderAccount
Inspect the configuration and status of a specific terminal via POST /getTerminalDetails
Locate which account or store a terminal currently belongs to via POST /findTerminal
List the stores under a merchant account via POST /getStoresUnderAccount
Use the same X-API-Key or basic-auth model as the rest of Adyen's classic-platform back-office APIs
Use Cases
Patterns agents use POS Terminal Management API for, with concrete tasks.
★ Multi-Store Terminal Provisioning
Retail chains rolling out new stores order terminals from Adyen and then need to assign each terminal serial to the correct store before it goes live. POST /assignTerminals accepts a list of terminal IDs and the target merchantAccount or store, completing the assignment in one call. POST /getStoresUnderAccount lists the available stores so the agent or operator can choose the right destination.
Call POST /assignTerminals with terminals=[POIID list], merchantAccount, and store identifier to assign a batch of terminals to a new store
Terminal Audit and Inventory
Operations teams need an accurate picture of where every terminal sits and what configuration it runs. POST /getTerminalsUnderAccount lists all terminals under a merchant account; POST /getTerminalDetails returns model, firmware, and assignment for a specific terminal. POST /findTerminal answers the inverse question — given a terminal ID, where is it currently assigned — which is essential for incident response when a terminal misbehaves at a particular store.
Call POST /getTerminalsUnderAccount with the merchantAccount, then POST /getTerminalDetails for any terminal flagged in the operations dashboard
Terminal Move Between Stores
When a store reorganises or closes, terminals are moved to another location. POST /findTerminal locates the terminal's current assignment, POST /assignTerminals reassigns it to the destination store, and POST /getTerminalsUnderAccount confirms the new state. The whole move is back-office only — no firmware push or store visit is required for the assignment change itself.
Call POST /findTerminal with the POIID, then POST /assignTerminals to move it from the closing store to the destination store identifier
AI Agent Estate Management via Jentic
An estate management agent that reconciles a quarterly inventory of terminals searches Jentic for 'list Adyen terminals under an account', loads the schema for /getTerminalsUnderAccount, and runs it for each merchant account in the corporate hierarchy. The agent compares the result against the asset register, flags missing or unassigned terminals, and proposes /assignTerminals calls for review. Jentic injects X-API-Key from the encrypted vault.
Search Jentic for 'list Adyen terminals under an account', load the getTerminalsUnderAccount schema, then execute once per merchantAccount in the corporate hierarchy
Key Endpoints
5 endpoints — the adyen pos terminal management api administers the fleet of payment terminals in an adyen merchant's estate.
METHOD
PATH
DESCRIPTION
POST
/assignTerminals
Assign one or more terminals to a merchant account or store
POST
/getTerminalsUnderAccount
List all terminals under a merchant account
POST
/getTerminalDetails
Inspect a specific terminal's configuration
POST
/findTerminal
Find the account or store a terminal currently belongs to
POST
/getStoresUnderAccount
List the stores under a merchant account
POST
/assignTerminals
Assign one or more terminals to a merchant account or store
POST
/getTerminalsUnderAccount
List all terminals under a merchant account
POST
/getTerminalDetails
Inspect a specific terminal's configuration
POST
/findTerminal
Find the account or store a terminal currently belongs to
POST
/getStoresUnderAccount
List the stores under a merchant account
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adyen API keys and basic-auth credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution time — the raw X-API-Key value never enters the agent context, including in batch terminal assignment runs.
Intent-based discovery
Agents search by intent (e.g., 'assign Adyen terminals to a store' or 'list terminals under an account') and Jentic returns the matching assignTerminals or getTerminalsUnderAccount operation with its full input schema, so the agent picks the right endpoint without learning the back-office surface from documentation.
Time to first call
Direct Adyen Terminal Management integration: 1-2 days for credential setup, account/store identifier discovery, and batch assignment scripting. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using POS Terminal Management API through Jentic.
What authentication does the POS Terminal Management API use?
The API supports an API key in the X-API-Key header (ApiKeyAuth) and HTTP Basic auth (BasicAuth) using web-service user credentials. Through Jentic, the credential is held encrypted in the vault and only a scoped execution token is exposed to the agent at runtime.
Can I move a terminal between stores with this API?
Yes. POST /assignTerminals reassigns one or more terminals to a different merchantAccount or store identifier in one call. Use POST /findTerminal first to confirm the terminal's current assignment, then POST /getTerminalsUnderAccount on the destination to verify the move took effect.
How is this different from the Terminal API?
The Terminal API drives in-flight transactions on a terminal — payments, reversals, displays, prints. The POS Terminal Management API is back-office only: assigning terminals to accounts and stores, listing them, and inspecting their config. The two APIs target different roles and use different base URLs.
How do I list all terminals under a merchant account through Jentic?
Search Jentic for 'list Adyen terminals under an account', load the getTerminalsUnderAccount schema, then execute with the merchantAccount identifier. Jentic injects X-API-Key from the encrypted vault. Get an account at https://app.jentic.com/sign-up.
What are the rate limits for the POS Terminal Management API?
Adyen does not publish a fixed numeric rate limit for Terminal Management in the spec; usage is administrative and rarely high-volume. If 429 responses appear, contact Adyen support to review the merchant account's quota.
Can I list the stores under a merchant account?
Yes. POST /getStoresUnderAccount returns the stores configured under a merchantAccount, which is the standard input for /assignTerminals when you need to know which store identifier to use as the assignment target.
GET STARTED