Merchant docs /docs
Site Sign in Apply as merchant

issue-ticket (V2) & Legacy paths

POST issue-ticket, Ed25519 ticket, and verify-license/bootstrap-config for compatibility only.

In the merchant dashboard: After sign-in → merchant dashboard — Sign in · Sign in to dashboard

POST issue-ticket (V2 — runtime path)

Current fivem_serverBoot.lua calls this endpoint at startup and refresh — without Authorization: Bearer or TenantApiToken on the customer server.

POST /public/fivem/v1/issue-ticket
X-Tenant-Id: <numeric store id>
Content-Type: application/json

{ "license_key": "…", "resource": "…", "build": "…" }
  • resource — FiveM resource folder name (= product name in dashboard).
  • build — build/version id from V2 metadata (build_id).
  • IP: extracted server-side (trusted_request_ip) — no server_ip in body.
  • First successful issue: auto-bind IP when license policy allows.

Common responses (issue-ticket)

  • 200 + ok:true + ticket — signed Ed25519 ticket; verified locally on server.
  • 200 + ok:false — explicit denial: not_found, expired, inactive, ip_mismatch, invalid_resource, invalid_build, …
  • 429 — REST limit exceeded — see Rate limits.

Legacy paths (V1 — not used by V2 boot)

Still available for old integrations only. Do not put TenantApiToken in customer files in V2.

POST verify-license (legacy)

POST /public/fivem/v1/verify-license
Authorization: Bearer <tenant.api_token>
X-Tenant-Id: <store id>

{ "license_key": "…", "script_name": "…", "server_ip": "…" }

GET bootstrap-config (legacy)

Called by old scripts with Bearer to populate verification URLs and webhooks — V2 boot does not call it.