Guides — Firecore | Fireball™

Guide 1schedule9 min read

Understanding FireCore API DOCS

A practical overview of the core Fireball API DOCS surface and how each service fits together.

Start with the service model

FireCore groups the platform into predictable service areas: authentication, games, sessions, transactions, reporting, and integrations. Understanding these areas first makes every API call easier to reason about.

Use the public reference

Open the API DOCS reference and identify the endpoint group that matches your workflow. Each endpoint should be treated as part of a larger lifecycle rather than as an isolated call.

Map your workflow

Before writing code, sketch the complete flow from launch to settlement. Mark where your system calls FireCore and where FireCore sends callbacks or status updates back to you.

Keep contracts stable

Use typed request and response models in your application. This keeps integrations predictable as your team adds more games, operators, environments, and reports.

Guide 2schedule6 min read

Using Guides and Q&A Effectively

Find the right Fireball guide, turn answers into implementation steps, and avoid repeated integration work.

Search by product first

Start with the product you are using: FireStation for administration, FireWorks for SDKs, FireStarter for examples, or FireFly for operator integration. FireCore connects those answers back to the underlying services.

Match the guide to your stage

Use getting-started guides for setup, implementation guides while building, and go-live checklists before production. This keeps your team from mixing exploratory work with release-critical checks.

Capture reusable answers

When a Q&A answer solves a technical issue, turn it into a short team note or internal checklist. FireCore works best when answers become repeatable team knowledge.

Escalate with context

If you need support, include the product, environment, endpoint, request ID, and expected behavior. Clear context makes Fireball support and community answers much faster.

Guide 3schedule8 min read

Core Integration Checklist

A concise checklist for teams preparing to connect their product to Fireball core services.

Confirm access and environments

Make sure your Fireball account, organization, API credentials, and sandbox environment are ready before implementation begins.

Validate authentication

Store credentials securely and verify that every server-side request signs or authenticates exactly as documented. Never place privileged keys in browser or client code.

Test the full lifecycle

Run through launch, session creation, bet placement, settlement, refunds, reporting, and failure handling in sandbox before production.

Prepare production monitoring

Log request IDs, callback results, latency, and settlement outcomes. Good FireCore integrations are observable from the first production transaction.

Get up and running fast