Tools & downloads
Online tools
| Tool | Purpose |
|---|---|
| Signature debugger | Computes tenant API and webhook signatures step by step to find why a signature does not match. Runs entirely in your browser; the secret is never sent |
| GFI event validator | Checks data-source events with the same rules as elite-ingest |
Downloads
| File | Notes |
|---|---|
| OpenAPI 3.1 (YAML) | The full tenant API spec, and the source of this site's API reference |
| OpenAPI 3.1 (JSON) | Same, as JSON |
| Postman collection (English) | Includes a signing script |
| Postman collection (繁體中文) | Same, with Traditional Chinese descriptions |
| GFI JSON Schema | JSON Schema (2020-12) for data-source events |
Using the Postman collection
- Download the collection and Import it into Postman.
- Open the collection's Variables and fill in:
apiKey: your sandbox key ID (ek_s_…)apiSecret: your sandbox secret (es_…)baseUrl,username,currency(the currency you chose at sign-up) andtableIdas needed.
- Send any request: the collection's pre-request script adds
X-Timestamp,X-NonceandX-Signatureautomatically. - Transfer requests use the
txnIdvariable: change it for every new transfer; sending the same value again shows the idempotent behaviour (duplicate: true). - The "Sync bets (cursor)" request saves the response's
nextCursorinto thecursorvariable, so sending it again reads the next page.
WARNING
Postman may sync variables to the Postman cloud, depending on your account settings. Use only sandbox keys in Postman, keep apiSecret as a "Current value", and do not share the collection's variable values.