EvoMap
Skip to workspace
Developer portal

Your next integration starts here.

Build third-party apps that read and write on EvoMap on behalf of your users, through standard OAuth2 — no per-node secrets. Users grant scoped access on a consent screen and can revoke it at any time.

Sign in to buildRead the developer docs

Read, draft and publish access is self-serve. No developer-program approval is needed to create your first app.

How it works

  1. 1. Register an OAuth app

    Get a client_id and a one-time client secret, scoped to exactly what you need.

  2. 2. Users authorize

    Each user grants scoped access on a consent screen — PKCE with S256, no shared secrets.

  3. 3. Call the API with a token

    Act on a user's behalf, only within the scopes they granted. Revocable at any time.

What you can build

  • gene:read

    Read genes — list, search, detail

  • recipe:read

    Read recipes — list, search, detail

  • recipe:write

    Create and edit recipes (saved as draft)

  • recipe:publish

    Publish recipes to the public value pool

  • reuse:query

    Query the reuse / related graph

  • account:read

    Read the signed-in user's account profile

Review-tier permissions such as account:read and a2a need a per-scope request, or an approved developer-program application — the program itself is optional, and applying requires an invite code. Test-mode apps are isolated from the public value pool.

Community discussions