Developer API

REST API for Unlimited Plans

Automate license creation, status updates, and validation log exports. Available to accounts with Unlimited access — generate API keys from your dashboard.

Authentication

Send your API key in the Authorization header:

Authorization: Bearer lme_your_api_key_here

Base URL

https://licensemyea.com/api/developer

Endpoints

  • GET/v1/productsList your EA products (includes compiled file metadata)
  • GET/v1/products/:idProduct detail + compiled file metadata
  • POST/v1/products/:id/compiledAttach/replace compiled .ex4 or .ex5 (multipart field: file)
  • GET/v1/products/:id/compiled/downloadDownload compiled EA binary
  • DELETE/v1/products/:id/compiledRemove compiled EA binary
  • GET/v1/licensesList licenses (optional ?productId=)
  • GET/v1/licenses/:idLicense detail + activations (live/demo)
  • POST/v1/licensesCreate a license
  • PATCH/v1/licenses/:idUpdate license fields
  • PATCH/v1/licenses/:id/statusSet active / suspended / revoked
  • GET/v1/logsValidation logs (?accountType=live|demo&source=ea|api)
  • POST/v1/validateValidate a license key (logged as source=api)
  • GET/usageAPI usage stats for your account

Live vs demo accounts

EA validation requests include mode=live or mode=demo based on the MetaTrader account type. Activations and validation logs store this so you can filter live production usage separately from demo/testing.

Compiled EA files (.ex4 / .ex5)

Each licensing product can optionally have one compiled MetaTrader binary attached — useful when you distribute the protected MQL source separately but want to store the built EA for your own workflow or API-driven delivery. Max file size: 50MB.

Example — attach compiled EX5

curl -s -X POST "https://licensemyea.com/api/developer/v1/products/YOUR_PRODUCT_ID/compiled" \
  -H "Authorization: Bearer lme_your_api_key" \
  -F "file=@MyEA.ex5"

Validation source filter

Every validation is tagged with its origin. source=ea means the call came from a live MetaTrader EA via /api/validate. source=api means it was triggered programmatically via POST /v1/validate (e.g. a web dashboard or webhook). Use this to separate production EA traffic from developer API testing.

Example — validate a license key

curl -s -X POST "https://licensemyea.com/api/developer/v1/validate" \
  -H "Authorization: Bearer lme_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "licenseKey": "YOUR-LICENSE-KEY",
    "accountNumber": "12345678",
    "productId": "YOUR-PRODUCT-UUID",
    "mode": "live"
  }'

Example — list licenses

curl -s "https://licensemyea.com/api/developer/v1/licenses" \
  -H "Authorization: Bearer lme_your_api_key"

Need Unlimited access? View plans or contact us for Enterprise / Unlimited.