How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Diebold

DN TM Authorization API

Public TM Authorization API of Diebold Nixdorf used to obtain and manage access tokens for the Vynamic Transaction Middleware. 8 paths with HTTP basic and bearer schemes; OpenAPI 3.0.3, version 1.8.1.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 9 operations across 8 paths, organized into 2 resource areas, and defines 10 schemas. It is described by OpenAPI 3.0.3, at version 1.8.1.

Requests are made against 2 base URLs: http://localhost:8080/oauth-api/v1, https://localhost:8080/oauth-api/v1.

9 operations 8 paths 10 schemas 2 DELETE4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.8.1
Base URL
https://{customer-host}:8080/oauth-api/v1
Authentication
HTTP Basic, HTTP Bearer
Contact
thorsten.brinkmann@dieboldnixdorf.com
Resource Areas
2

Authentication & Security 2

DN TM Authorization API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth).

  • basicAuth — When using the basic authentication method, the base64 username and password must be specified in the HTTP authorization header - which is not recommended at a…
  • bearerAuth — When using the bearer authentication method an access token has to be provided in the HTTP authorization header

Paths & Operations 9

Across 8 paths, the API surfaces 9 operations — 2 DELETE, 4 GET, 3 POST. They span 2 resource areas: TM Authorization API, TM OAuth API. Each is listed below with its method, path, parameters, and response codes.

TM Authorization API 3
POST
/tm-authorization/authenticate
An endpoint to authenticate a user
tm-authenticate body → 200400401500
DELETE
/tm-authorization/logout
An endpoint to logout an already authenticated user.
tm-logout → 200400401500
GET
/tm-authorization/keys
An endpoint to get the public keys to verify the JWT token.
tm-get-keys → 200400500
TM OAuth API 6
GET
/authorization/login
Get redirected to the authorisation URL or retrieve the list of external authorisation systems.
login 2 params → 200500
POST
/authorization
Do NOT call this endpoint.
authenticationRedirectionEndpoint body → 200400401500
DELETE
/authorization/logout
Logout - gets redirected to the logout URL.
logout → 200400401500
POST
/token
Refresh the token and retrieve a new access token, as well as a new refresh token, expiresIn and token type.
refreshToken body → 200400401500
GET
/token
Exchange an access token for/to an PCEAdminSecurityToken.
exchangeToken 1 param → 200400401500
GET
/test
Endpoint to ease the tests of the API implementation.
sandboxTest 2 params → 200400401500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are TmKeyInfo (10 properties), TmAuthenticationResponse (9 properties), TokenResponseData (6 properties), TmAuthenticationRequest (5 properties). Each schema is shown below with its type and property counts.

Error
object
The error property is optional.
2 properties
TmRight
object
Describes a right as integer values as well as in a readable form.
3 properties 2 required
AuthenticationProviderData
object
2 properties 2 required
TokenResponseData
object
6 properties 5 required
ExchangeTokenResponseData
object
1 property 1 required
RefreshTokenRequest
object
The RefreshTokenRequest.
1 property 1 required
TmGetKeysResponse
object
1 property 1 required
TmKeyInfo
object
10 properties 4 required
TmAuthenticationRequest
object
5 properties 2 required
TmAuthenticationResponse
object
Describes the response of the authentication request.
9 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

diebold-dn-tm-authorization-api-openapi.yml Raw ↑
#Banking#Payments#ATM#Self-Service#Transaction Middleware#Vynamic#Authorization#OAuth
← Back to D APIs
API Details
ID
diebold:dn-tm-authorization-api
Base URL
https://{customer-host}:8080/oauth-api/v1
Docs
https://api.swaggerhub.com/apis/Diebold-Nixdorf/DN-TM-Authorization-API/1.8.1
Provider
Diebold
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=diebold-dn-tm-authorization-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/diebold-dn-tm-authorization-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of DN TM Authorization API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.