Skip to main content
1

Sign in

With access to the hosted console’s password gate, open console.gol.network, unlock it, then enter your email address and the six-digit code we send you. The gate and developer sign-in are separate. When the Google option is available, you can use it instead. Both methods use the same developer account when the verified email matches. If Google does not verify the address, as with a Google account that uses a third-party email provider, sign in with the email code instead. The console renews the session when you return; browser cookie limits or clearing may still require a new sign-in. No wallet is needed.
The GOL console sign-in page with a work email entered
The screenshot shows developer sign-in after the separate access gate. It uses mock data from the deployed console source.
2

Create a project

After verified sign-in, your personal workspace can start with no projects. The optional Get started checklist lets you name the workspace, create the first test project, invite a teammate, and create a test API key. You can skip any step or the whole checklist and return later. Name your first project there, or create one from the workspace overview. Its test environment is active. The live environment is not available yet.Use the workspace selector above the project switcher in the sidebar. You can create more test projects if your workspace role permits it, or switch among projects you can access. Each project has its own API keys, webhooks, gas activity, and audit history. The URL includes its stable Project ID, so you can bookmark a project page.
Naming the first project in the console
3

Review team access

Workspace Owners and Admins can open Team to invite members, choose their role and project scope, and review pending invitations. An invitation needs the recipient to sign in with the invited email and accept. A workspace role never grants wallet or mandate authority. See workspaces and team access for exact permissions and offboarding.
4

Copy the Project ID

Copy the UUID from Overview or Project settings. Public API and SDK project routes use this ID. You can change the project’s display name in Project settings without changing its ID.
5

Create an API key

Open API keys and choose Create API key. For a full integration keep the Full integration preset:Choose fewer scopes for keys that need less.
The new API key form with the Full integration preset selected

Full integration selects all six scopes. Read only selects only the read scopes.

6

Copy the secret

The secret is shown once. Store it in a server-side secret store or environment variable, never in browser code or a repository. If you lose it, rotate or create a key.
The one-time API key reveal with the secret hidden and a Copy button
An API key identifies your project and environment. It cannot create, widen, or revoke an owner’s authority, and it cannot move funds by itself. Continue with make your first request.