MULEHUNT
MULEHUNT / GETTING STARTED

Authentication

The MuleHunt API supports two ways to obtain an access token. Both methods issue a token that can call the same MuleHunt API endpoints. Tokens expire after 3600 seconds (one hour).

Client ID and client secret

Use partner-level credentials with the OAuth client credentials flow.

EnvironmentToken URL
Productionhttps://auth.mulehunt.com/oauth2/token
Developmenthttps://auth-dev.mulehunt.com/oauth2/token
curl -X POST "$AUTH_URL" \
  -d 'grant_type=client_credentials' \
  -d "client_id=$MULEHUNT_CLIENT_ID" \
  -d "client_secret=$MULEHUNT_CLIENT_SECRET"

User API key

An authorized Partner Admin can generate a user API key in Account Settings → API Access. Exchange the key for a token:

curl -X POST "$API_BASE_URL/api/public/partner-token" \
  -H 'Content-Type: application/json' \
  -d "{\"apiKey\":\"$MULEHUNT_API_KEY\"}"

Alternatively, pass the key in the x-api-key request header.

Note: If the user who created the API key is deleted, all API keys created by that user are automatically revoked and can no longer be used to obtain an access token.

{
  "access_token": "YOUR_ACCESS_TOKEN",
  "token_type": "Bearer",
  "expires_in": 3600
}

Call the API

Use the returned access token in the Authorization header. Request a new token after it expires, and keep client secrets and API keys in a secure server-side environment.

MULEHUNT / API GUIDE