Elements Manual
Elements 3 Manual
Elements 3 Manual
  • Welcome 👋
  • QUICK START
    • Elements in Five Minutes or Less
    • Accessing the Web UI (CRM)
    • Creating A User
  • General
    • General Concepts
    • N-Tier Architecture
    • Security Model
  • Core Features
    • Core API Overview
    • Sessions
    • Applications
    • Users and Profiles
    • Digital Goods
    • Progress and Missions
    • Leaderboards
    • Matchmaking
    • Followers
    • Friends
    • Reward Issuance
    • Save Data
    • Schemas and Metadata Specifications
    • Queries
      • Base Query Syntax
      • Boolean Queries
      • Object Graph Navigation
      • Advanced Operators
        • .ref
        • .name
    • Custom Code
      • Element Structure
      • RESTful APIs
      • Websockets
    • Auth Schemes
      • OIDC
      • OAuth2
  • Web 3
    • Omni Chain Support
    • Vaults
    • Wallets
    • Smart Contracts
      • Smart Contracts: Ethereum
      • Smart Contracts: Flow
      • Smart Contracts: Solana
      • Smart Contracts: Neo
  • CONFIGURATION
    • Direct Database Access and Batch Configuration
    • Batch Samples
      • Item Upload Bash Script Sample
      • Mission Upload Bash Script Sample
  • RESTful APIs
    • Swagger and Swagger UI
    • API Specification
      • /application
      • /application/configuration
      • /auth
      • /auth_scheme
        • /custom
        • /oauth2
        • /oidc
      • /blockchain
      • /followee
      • /follower
      • /friend
      • /google
      • /index
      • /inventory
      • /item
      • /large_object
      • /leaderboard
      • /rank
      • /score
      • /match
      • /mission
      • /progress
      • /reward_issuance
      • /schedule
      • /notification
      • /profile
      • /save_data
      • /metadata_spec
      • /mock_session
      • /session
      • /health
      • /version
      • /signup
      • /user
    • Javadocs
  • Releases
    • 3.1 Release Notes
    • 3.2 Release Notes
Powered by GitBook
On this page
  1. Core Features
  2. Applications

iOS Application Configuration

Configure iOS applications in your Elements installation so users can take advantage of in-app purchases.

Last updated 3 months ago

The iOS application configuration is where you tie in iOS app and IAP compatibility for your Elements application.

You'll need an Apple Developer account and will need to create the app in App Store Connect.

  1. Edit an application in Elements

  2. Add an Application configuration in the Application Editor, as seen and select "Add iOS App Store," or edit an existing iOS Application configuration for the application.

  3. Enter the needed info and save with the "OK" button.

  4. Application Configuration Name: This is a unique name for the application configuration.

  5. Team ID: Your Apple Developer team ID for the app.

  6. Client ID: Your app's bundle ID from App Store Connect (e.g. com.company.example).

The final two fields relate to Apple Sign-In, which we'll cover below.

iOS Apple Sign-In

Apple Sign-In for your app is also configured in the iOS Application Configuration.

You'll need to create an Apple Sign-In key in the Apple Developer console.

You'll need the key ID as well as to download the key.

In the application configuration on the Elements admin console:

  • Key ID: Your apple sign in key ID.

  • Apple Sign-In Private Key: The private key you downloaded. Be sure to include the headers, as the key must be in PEM format.

You'll also need some server-side lua code and some client-side code to complete setup, which will be covered elsewhere in the manual.

here
iOS Application Configuration
Apple Sign In Config