Jump to Content
Neon
GuidesRecipesAPI ReferenceChangelogDiscussions
v1.0.0

Log InNeon
Guides
Log In
v1.0.0GuidesRecipesAPI ReferenceChangelogDiscussions

Documentation

  • Getting Started with Neon
  • Storefront
    • Environments and API Keys
    • Managing Offers
    • Storefront Images
    • Offer Images
    • Text Localization
    • Offer Segmentation
    • Web Purchase Limits
  • Checkout
    • Setting Up Your Checkout Experience
    • Initiating a Checkout
    • Embedded Checkout
    • Accept Payments with Neon in iOS Games
  • Post-Purchase Management
    • Updating Your Game
    • Get Purchase Details
    • Refunds
    • Get all purchases
  • Testing and Launching Your Store
  • Webhooks and Callbacks
    • Webhook: purchase.completed
    • Webhook: refund.processed
    • Callback: account.getInventory
    • Callback: account.validate
    • Webhook: dispute.opened
    • Webhook: dispute.closed
    • Webhook: checkout.abandoned
    • Webhook: cart.abandoned
  • Additional
    • Analytics
    • Player & Game Authentication
    • Authentication API
      • Auth API User Behavior
    • International Support
    • Pricing
    • Test Inputs
    • Payouts
    • Currencies
    • Promo Codes
    • Disputes
    • Migrating from Xsolla to Neon
    • Transactions
  • Support
  • Subscriptions (beta)
Powered by 

Callback: account.validate

Suggest Edits

The account.validate endpoint validates that the account with a given id is present in your system and should be authenticated by the web store.

Example Request

{
  "accountId": "86436542684"
}

Example Response

The isValid field should be set to true when player with the provided accountId exists . The metadata field is optional but, when present, it will be passed in the request of the purchase.completed webhook.

{
  "isValid": true,
  "displayName": "Player Name",
  "metadata": {}
}

Updated over 1 year ago


  • Table of Contents
    • Example Request
    • Example Response