Skip to main content

Tech Glossary

This glossary provides definitions for key terms and technologies used in our CRM documentation. It is designed to help developers and technical teams understand the concepts and tools available within the platform.

A​

  • API (Application Programming Interface): A set of rules and protocols that allows different software applications to communicate with each other.
  • API Gateway: A server that acts as an entry point for all API requests, managing traffic, authentication, and routing to the appropriate microservices.
  • Authentication: The process of verifying the identity of a user or system before granting access.
  • Authorization: The process of determining if a user or system has permission to access a specific resource or perform an action.
  • API Key: A unique identifier used to authenticate and authorize access to an API, ensuring secure communication between clients and the API server.

B​

  • Base URL: The root address of an API, used as a starting point for all endpoint calls (e.g., https://api.example.com).
  • Bearer Token: A type of token used in authorization headers to verify API requests securely.
  • BET: A wager placed by a player on the outcome of a game, event, or activity, typically involving a risk of losing the staked amount in exchange for the possibility of winning a larger sum.

C​

  • Cache: A temporary storage layer that holds data to reduce latency and improve API response times.
  • Channel: A method of communication used to engage with users, such as email, SMS, or push notifications.
  • CRM (Customer Relationship Management): A system designed to manage and analyze customer interactions and data throughout the customer lifecycle.
  • CMS (Casino Management System): A software platform designed to manage and streamline the operations of a casino, including player tracking, gaming machine monitoring, financial reporting, loyalty programs, and compliance management.
  • CSM (Customer Success Manager): A role focused on ensuring customers achieve their desired outcomes when using a product or service by providing support, guidance, and fostering long-term relationships.
  • CORS (Cross-Origin Resource Sharing): A mechanism that allows restricted resources on a web page to be accessed from a domain other than the one serving the web page.
  • CASHOUT: The option for a player to withdraw or redeem a portion of their bet before the event or game has finished, typically for a reduced amount based on the current odds and outcome likelihood.

D​

  • Data Payload: The actual data being sent in an API request or response, typically in JSON or XML format.
  • Documentation: Technical instructions and examples that explain how to use an API or software system effectively.

E​

  • Endpoint: A specific URL where an API service is accessible to send or receive data.
  • Error Code: A numeric or textual code returned by an API to indicate the status or nature of a failed request (e.g., 404 for "Not Found").

H​

  • Hard Delete: A process to permanently remove data from the database. Once executed, the information cannot be recovered.
  • HTTP Methods: The verbs used in REST APIs to specify the desired action, such as GET, POST, PUT, DELETE, and PATCH.

I​

  • Idempotent: An operation that produces the same result no matter how many times it is performed (e.g., a GET request should always return the same result for the same input).
  • Integration: The process of connecting two or more systems to work together seamlessly.
  • In-App Notifications: Messages sent directly within a mobile application to engage users in real time.
  • ISO (International Organization for Standardization): An independent, non-governmental international organization that develops and publishes global standards to ensure quality, safety, efficiency, and interoperability across industries.
  • ISO 639-1: A part of the ISO 639 standard that defines two-letter codes for the representation of the names of languages, widely used in software localization and internationalization (e.g., "EN" for English, "FR" for French).
  • ISO 4217: A standard that defines three-letter and two-letter codes for currencies and their subdivisions, used internationally for financial and currency-related transactions (e.g., "USD" for US Dollar, "EUR" for Euro).
  • ISO 3166-1 (Alpha-3): A part of the ISO 3166 standard that defines three-letter country codes used to represent countries and dependent territories (e.g., "USA" for the United States, "FRA" for France).

J​

  • JSON (JavaScript Object Notation): A lightweight data-interchange format widely used for API request and response payloads.

L​

  • Latency: The time it takes for a request to travel from the client to the server and back.

M​

  • Microservices: A software architecture style in which applications are composed of small, independent services that communicate through APIs.
  • Multi-Channel Marketing: A strategy that uses multiple communication channels to engage with customers, such as email, SMS, and push notifications.

O​

  • OAuth: An open-standard protocol for authorization, allowing users to grant access to their resources without sharing credentials.
  • On-Site Notifications: Real-time messages displayed directly on a website to engage users while they browse.

P​

  • PAMS (Player Account Management System): A centralized system used to manage player accounts, including registration, authentication, account balances, activity tracking, and compliance with regulatory requirements.
  • Pagination: A technique used to divide large data sets into smaller, more manageable chunks for API responses.
  • Payload: The body of a request or response in an API call, typically containing data in JSON or XML format.
  • PEP: Gamanza Player Engagement Platform .
  • Push Notifications: Brief messages sent directly to a user’s device, such as mobile phones or web browsers, to deliver updates, promotions, or alerts.

R​

  • Rate Limiting: A mechanism used to control the number of API requests a client can make in a given time period, preventing abuse.
  • REST (Representational State Transfer): An architectural style for designing APIs using standard HTTP methods and stateless communication.
  • RFC 3339: A standard that defines a date and time format for use in internet protocols and data interchange, based on the ISO 8601 standard. It specifies a representation of date and time in the format YYYY-MM-DDTHH:MM:SSZ or with an optional time zone offset (e.g., 2025-01-10T12:00:00Z).

S​

  • SDK (Software Development Kit): A collection of tools and libraries that developers use to build software applications.
  • Soft Delete: A process that removes a record from active queries and operations but retains it in the database for potential recovery or compliance purposes.
  • Status Code: A 3-digit number in HTTP responses indicating the result of a request (e.g., 200 for success, 500 for server error).
  • SETTLEMENT: The process of determining the result of a bet or wager, including the calculation of winnings or losses, and updating the player's account balance accordingly.
  • SSO (Single Sign-On): An authentication process that allows users to access multiple applications or systems with a single set of credentials, reducing the need for multiple logins and improving security and user experience.

T​

  • Token: A piece of data used for authentication and authorization in API requests, often in the form of a JSON Web Token (JWT).
  • Throttling: The process of limiting the number of API requests a client can make to ensure system stability and performance.

U​

  • UI (User Interface): The space where interactions between humans and machines occur, including the layout, design, and functionality of elements such as buttons, menus, and forms that allow users to interact with software or hardware.
  • Upstream Server: A server that handles requests from a downstream server or client, often in a distributed system or a reverse proxy setup. The upstream server processes the requests and forwards the response to the downstream server, typically for further processing or delivery to the end user.

W​

  • Webhook: A method of delivering real-time data to external applications by sending an HTTP request when an event occurs.

Notes​

This glossary will continue to grow as new features and terms are introduced. If you encounter unfamiliar terminology, refer to this document or reach out to our support team.