If you are wanting to access Moshtix's API to integrate with other platforms, then a KEY is required. Client and Moshtix Admins can generate new keys themselves directly from the Moshtix control room.
API Keys are used to retrieve information and perform actions within your Moshtix client account. They should only be shared with trusted parties.
How to Generate
1) Log into Moshtix Control Room here.
2) Under 'Account' click 'API Keys'
If you cannot see this option, contact your Moshtix client account manager by selecting 'Get Help' in the bottom left.
3) Click 'Add Key' and enter a name for your new API key.
This name should be unique and easily identifiable, You may want to name the Key after the app or service you will be using with the Moshtix API.
4) Click 'Create Key'.
5) The Key is generated and can be copied directly to the clipboard to be pasted into the API set-up on the external platform / app.
How to View Existing API Keys
1) Log into Moshtix Control Room here.
2) Under 'Account' click 'API Keys'
If you cannot see this option, contact your Moshtix client account manager by selecting 'Get Help' in the bottom left.
3) All existing keys are listed on this page, Click the three dots on any existing key.
4) Click 'View'
5) The key will be opened to view and copied.
FAQ
|
Q: How do I update or delete an API Key?
|
|
A: Any API keys that need to be updated or deleted out of your client account can be requested via your Client Manager.
|
|
Q: Can I share my API key with anyone?
|
|
A: API Keys are used to retrieve information and perform actions within your Moshtix client account. They should only be shared with trusted parties
|
|
Q: What do I use an API key for?
|
|
A: An API key is a secret code used by one system to perform privileged requests or actions upon another system via its API. They act as a unique identifier and provide a secret to facilitate authentication and authorization. They are are used by API integrations to retrieve information and perform actions within your Moshtix client account.
|
Comments
0 comments
Article is closed for comments.