Welcome to the Gloebit Integration Guide for merchants and developers. This document will guide you through the simple steps from getting started and testing Gloebit's services, to going live on production when launching your application or game.
In order to integrate Gloebit's services, you need an OAuth key and secret for your application. These application credentials are what securely authenticate your application when it is making request to the Gloebit services, and are required for integration. Here's how to obtain application credentials and get started.
This is the ideal way to get started and it will only take a few minutes to do the following:
Please see our Getting Started Tutorial for easy to follow instructions for the above steps.
Once finished, you will be ready to integrate.
Already have a Gloebit merchant account with an application? Great, we're excited that you've chosen to return to use Gloebit again.
There's no need to create a new Gloebit merchant account. From the Merchant Tools page on your existing Gloebit account, simply click the "add application" button to create a new application within your existing account. Each application has its own OAuth key and secret and can be configured separately. You can add as many applications as you need within your Gloebit merchant account.
Once you have obtained credentials for your application, you are ready to integrate with Gloebit. When integrating, make sure to use the URL endpoints below and the application credentials from an application you created in your merchant account.
URL endpoints: https://www.gloebit.com/<endpoint>
If you're integrating our digital currency with OpenSim, we've already done all of the work for you. See the details in our OpenSim section and sign up for beta access.
All of the Gloebit Service api calls require an access token which identifies your application and stores the authorization provided from a Gloebit user to your application to interact with the user's account via each service. Begin by integrating Authorization and obtaining access tokens to use with Gloebit services. Learn more about Gloebit Authorization.
Use the application OAuth key and secret you obtained from creating an application when integrating Authorization.
Once you have integrated Authorization, you can integrate any or all of the other services which Gloebit provides. See each for more details:
Please see the following resources to aid in your integration of our services:
We are a big fan of open source tools. If, in your development, you create a tool which would be useful for our community of developers such as wrapping our calls in a new language, or designing a great front end to tie into our character system, and you are willing to make it available, please let us know. We will be happy to review it and provide it for general use.
When you are approaching launch of your application, there are a few steps to prepare before you go live. It is best to start this process before your launch date as there are a couple of reviews which must occur.
If you have not already done so, set up your Gloebit merchant account and application.
Please see our Getting Started Tutorial for easy to follow instructions for the above steps.
Submit the merchant upgrade request for your account early. When you sign up, you are required to fill out all of the information in the merchant signup form. We will need to review this and in some cases, may require some additional information to verify the data you have submitted. We recommend you do this well before the launch of your first application in case there are any delays. Until you have been approved, your applications may not be able to use balance and transact api functions and you will not be able to sell gloebits or cash out.
Set your OAuth Key Alias. If you are using an alias to set your "r=<application>" url query argument when sending a user to us to purchase gloebits, make sure you have reserved the alias you want. These aliases are unique, so grab the one you need for your application.
Back up your application api settings. We provide you functionality to download and upload settings. Downloading gives you a backup you can restore if needed. Restoring from a downloaded file will overwrite everything except the Gloebit Authorization Information section.
Make sure your application ties into the Gloebit endpoints with the OAuth key and secret from your application's api settings.
Find your application key and secret in the api settings for your application and confirm you are using those in your integration.
If you set any permitted callback URI prefixes, verify that they are correct for your application.
If you have not already done so, in the api settings for your production application, toggle the "make application findable" option on in your application information. This will make it discoverable from our partner apps page so that we can drive some traffic to your application. There may be a delay before your application appears if there have been any recent changes to your application information in your api settings which we have not yet reviewed. Please contact us if your application does not appear, or if a delay might affect your launch.
If you have a question while integrating, please contact us and we will do our best to help. If you believe you have found a bug or a mistake in any of our documentation, then please alert us and we will fix and clarify the issue. If there is a feature you would like from our service, please let us know. We will let you know if there is a way to accomplish your goal within the current feature set, and we will factor requests into our roadmap for future development.
If you have a question while integrating, please contact us and we will do our best to help. If you believe you have found a bug or a mistake in any of our documentation, then please alert us and we will fix and clarify the issue. If there is a feature you would like from our service, please let us know. We will let you know if there is a way to accomplish your goal within the current feature set, and well factor requests into our roadmap for future development.
