Skip to main content

Casino Provider Data Models

This page describes the data models used in the Casino Game Provider API for the Main application. These models represent the structure of data that clients receive when interacting with casino game provider operations.

Core Models​

CasinoGameProviderModel​

Represents a casino game provider with basic information.

type CasinoGameProviderModel {
  id: ID!
  slug: String!
  name: String!
  logoUrl: String
}

Fields Description:

  • id: Unique identifier for the casino game provider
  • slug: URL-friendly and unique identifier for the casino game provider
  • name: Display name of the casino game provider
  • logoUrl: URL of the provider's logo image

Resolver Fields:

  • description: String - Description of the casino game provider (localized based on user language)
  • seo: SEOSingleLanguageModel - SEO information for the provider
  • activePlayers: ActivePlayerCountFormattedResponse - Count of active players within the last 24 hours for the provider

CasinoGameProviderWithGamesModel​

Represents a casino game provider with additional game information.

type CasinoGameProviderWithGamesModel {
  id: ID!
  slug: String!
  name: String!
  logoUrl: String
  games: [CasinoGameModel]
  activePlayers: ActivePlayerCountFormattedResponse
}

Fields Description:

  • id: Unique identifier for the casino game provider
  • slug: URL-friendly and unique identifier for the casino game provider
  • name: Display name of the casino game provider
  • logoUrl: URL of the provider's logo image
  • games: List of games from this provider
  • activePlayers: Count of active players within the last 24 hours for the provider

Enum Types​

CasinoGameProvidersOrderBy​

Ordering options for casino game providers:

enum CasinoGameProvidersOrderBy {
  NAME
  INDEX
  CREATED_AT
  UPDATED_AT
}

Values Description:

  • NAME: Order alphabetically by provider name
  • INDEX: Order by the provider's internal index (default)
  • CREATED_AT: Order by creation date
  • UPDATED_AT: Order by last update date

Input Types​

CasinoGameProviderBySlugArgs​

Input for retrieving a casino game provider by its slug:

input CasinoGameProviderBySlugArgs {
  slug: String!
}

Fields Description:

  • slug: The slug of the casino game provider to retrieve

CasinoGameProvidersArgs​

Input for retrieving casino game providers with filtering, ordering, and pagination:

input CasinoGameProvidersArgs {
  orderBy: CasinoGameProvidersOrderBy = INDEX
  filter: CasinoGameProvidersFilterInput
  limit: Int = 20
  offset: Int = 0
}

Fields Description:

  • orderBy: Ordering option for the results (defaults to INDEX)
  • filter: Optional filter criteria
  • limit: Maximum number of results to return (defaults to 20)
  • offset: Number of results to skip for pagination (defaults to 0)

CasinoGameProvidersFilterInput​

Input for filtering casino game providers:

input CasinoGameProvidersFilterInput {
  query: String
  casinoPageId: String
}

Fields Description:

  • query: Search query to filter providers by name (max 120 characters)
  • casinoPageId: MongoDB ObjectId of a casino page to filter providers that have games on that page

Response Types​

ActivePlayerCountFormattedResponse​

Represents the count of active players for a casino game provider:

type ActivePlayerCountFormattedResponse {
  count: Int!
  formattedCount: String!
}

Fields Description:

  • count: The count of active players
  • formattedCount: The formatted count of active players (e.g., "1.2K", "500")

SEOSingleLanguageModel​

Represents SEO information for a casino game provider:

type SEOSingleLanguageModel {
  title: String!
  description: String!
  socialImage: String!
}

Fields Description:

  • title: SEO title for the provider
  • description: SEO description for the provider
  • socialImage: URL of the social media image

PaginatedGameProviderResponse​

The paginated response type for casino game provider operations:

type PaginatedGameProviderResponse {
  data: [CasinoGameProviderModel!]!
  count: Int!
  offset: Int!
  limit: Int!
}

Fields Description:

  • data: Array of casino game providers
  • count: Total number of results
  • offset: Current pagination offset
  • limit: Current page size limit

Queries​

casinoGameProvider​

Retrieves a single casino game provider by its slug.

query casinoGameProvider($slug: String!) {
  casinoGameProvider(slug: $slug) {
    id
    slug
    name
    logoUrl
    description
    seo {
      title
      description
      socialImage
    }
    activePlayers {
      count
      formattedCount
    }
  }
}

Arguments:

  • slug: String! - The slug of the casino game provider to retrieve

Returns:

  • CasinoGameProviderModel - The casino game provider with all its information

casinoGameProviders​

Retrieves a paginated list of casino game providers with optional filtering and ordering.

query casinoGameProviders(
  $orderBy: CasinoGameProvidersOrderBy = INDEX
  $filter: CasinoGameProvidersFilterInput
  $limit: Int = 20
  $offset: Int = 0
) {
  casinoGameProviders(
    orderBy: $orderBy
    filter: $filter
    limit: $limit
    offset: $offset
  ) {
    data {
      id
      slug
      name
      logoUrl
      description
      seo {
        title
        description
        socialImage
      }
      activePlayers {
        count
        formattedCount
      }
    }
    count
    offset
    limit
  }
}

Arguments:

  • orderBy: CasinoGameProvidersOrderBy (optional) - Ordering option for the results
  • filter: CasinoGameProvidersFilterInput (optional) - Filter criteria
  • limit: Int (optional) - Maximum number of results to return
  • offset: Int (optional) - Number of results to skip for pagination

Returns:

  • PaginatedGameProviderResponse - Paginated list of casino game providers

Deprecated Queries​

The following queries are deprecated and should not be used in new implementations:

getCasinoGameProvider​

Deprecated: Use casinoGameProvider instead.

getCasinoGameProviders​

Deprecated: Use casinoGameProviders instead.