Platform
Everything in this section is shared across Invokation products. Sign up once, and the same organisation, portal, and credentials cover IVK Match and whatever you add later.
Organisations and games
Section titled “Organisations and games”Tenancy has two levels.
An organisation is the ownership and billing boundary. It holds your team members, your billing relationship, and one or more games.
A game (or app) is the unit of tenancy for the services themselves. It holds your queues, your credentials, and your usage records. Isolation is per game: nothing is shared between two games, and nothing is shared between two organisations.
Most teams start with one organisation and one game, and add games as they ship titles. Sign up for a free-tier organisation to get started; no contract or sales conversation is needed to build an integration.
The portal
Section titled “The portal”The portal is where you administer an organisation and its games without going through an API:
- Create the organisation and invite the rest of your team.
- Create a game and issue, rotate, and revoke its API credentials.
- Author and edit queue configuration, and see what is currently live.
- Watch usage against your plan.
Configuration made in the portal takes effect on the running service; there is no deploy step on your side. See Queue Configuration for what a queue declares.
Credentials
Section titled “Credentials”Credentials are issued per game from the portal and belong in your game backend’s secret store. They authenticate your backend to the API, so they must never ship in a game client, where anyone can extract them and act on your queues.
See Authentication for how to attach them to a call.
Where things run
Section titled “Where things run”You do not run anything. Invokation operates the service, and your backend talks to a hosted endpoint over TLS. Nothing in the product documentation assumes access to a container, a filesystem, or a message broker.