Ettajer for Developers console

Open Dashboard → Developer (or go to /dashboard/developer). Sign in as the merchant who owns the store. The developer console is separate from the store dashboard — it focuses on OAuth apps, API keys, and agent activity.

What you can do here: create applications, register redirect URIs, copy client ID / secret, create and rotate API keys, see which stores are connected (OAuth grants), revoke access, and review Activity from connected AI apps.

Create an application with a clear name (for example Claude MCP or Cursor MCP). Use the redirect presets for Claude and Cursor, or paste exact callback URLs. Redirect URIs must match character-for-character — no wildcards.

After create, a one-time banner shows Client ID and Client secret. Copy them immediately (Copy all works). The secret is hashed and never shown again. If you lose it, use Regenerate secret and update Claude or Cursor.

Expand an app to copy the client ID, regenerate the secret, create an API key (etsk_live_…), and review redirect URIs and grants. Connected grants show the store name and scopes. Revoke a grant to disconnect an agent without deleting the app.

API keys are store-scoped through the same app grant model. Create a key for scripts or non-interactive agents; rotate or revoke keys from the expanded app row. Never commit secrets or paste them into chat logs.

Activity lists recent actions from connected apps — theme creates, batches, previews, and other API calls. Use it to confirm an agent is hitting the right store.

The console also shows the production MCP endpoint (https://www.ettajer.com/api/v1/mcp) with one-click copy, plus Get help articles and docs links (Quickstart, MCP, OAuth, API).

Footer and header links: Guides, Docs, MCP, OAuth, and Store dashboard. Mobile has Console / Activity / Docs.

Related: /developers for the public developer site, /help/category/developers for all developer help articles.