We offer two environments for integration, a playground (sandbox) and production.
You will be provided a separate API key for each.
The playground environment is intended to be used as a self contained test environment for your integration with the Ticket Engine API. Playground transactions are unmetered and will not be billed.
All transactions generated by this environment will happen on the public
testnet of the blockchain and no real funds will be used. As the name suggests, data on the public testnet is still public and accessible to anyone through a testnet blockchain explorer. Usage of mock data is highly recommended.
Data written to a Blockchain testnet does not come with guarantees around its consistency. Although wiping a testnet is uncommon, the existence of this data should not be relied upon for long periods of time.
The production environment will write transactions to the public blockchain
mainnet. Expect everything written to the mainnet to be immutable and as such should be treated with care. Real funds will be used to process mainnet transactions.
Once you have started successfully sending requests to the Ticket Engine API the natural next step may be to check the blockchain records to see the transaction written to the chain. The easiest way to do this would be to access the Ticket Explorer to view your transactions being written in real-time. Take a look at the Ticket Explorer Environments to access the explorer for your environment.
After finding the ticket that you have just created, you can navigate through to the ticket timeline page and then find a link to the blockchain explorer transaction for the request submitted.
When in playground this will write transactions to Polygon. The recommended blockchain explorer for Polygon Mainnet would be Polygonscan. In the playground environment you will want to head over to the Polygonscan Mumbai environment. It is here that you are able to enter the
txHash recieved in the callbacks to navigate to the transaction directly.