Exchange for Access Token

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.lwolf.com/doc/transactiondesk-api/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "TransactionDesk API MCP server": {
    "url": "https://apidocs.lwolf.com/doc/transactiondesk-api/mcp"
  }
}
Close
POST /oauth/token

Exchanges an authorization code or client credentials for a bearer access token. Parameters must be passed as query parameters in the URL.

Use grant_type=authorization_code along with the code and redirect_uri from the Authorization Code flow.

Use grant_type=client_credentials for server-to-server integrations (no user redirect required).

Query parameters

  • grant_type string Required

    The OAuth 2.0 grant type

    Values are authorization_code or client_credentials.

  • client_id string Required

    Client ID provided by Lonewolf

  • client_secret string Required

    Client Secret provided by Lonewolf

  • code string

    Authorization code received in the redirect (authorization_code flow only). One-time use, expires in 10 minutes.

  • redirect_uri string

    Redirect URI registered with Lonewolf (authorization_code flow only). Must match the URI used in the authorization request.

Responses

  • 200 application/json

    Access token issued successfully

    Hide response attributes Show response attributes object
    • access_token string

      The signed bearer token to use in Authorization headers for subsequent API requests

    • token_type string

      Token type (always 'bearer')
POST /oauth/token 
curl \
 --request POST 'https://api.pre.transactiondesk.com/oauth/token?grant_type=authorization_code&client_id=Lonewolf&client_secret=LonewolfSecret'
Response examples (200) 
{
  "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...",
  "token_type": "bearer"
}