Developer reference

Current capability boundaries

Documentation should distinguish implemented controls from planned services.

1 min read · 132 words

Documentation should distinguish implemented controls from planned services. The developer console supports app records, scoped API keys, and webhook registration. Registration does not mean webhook delivery is enabled. No isolated sandbox, published quota system, or generic /api/v1 API is documented here. Keep secret credentials on trusted servers.

What to expect

The developer console supports app records, scoped API keys, and webhook registration. Registration does not mean webhook delivery is enabled. No isolated sandbox, published quota system, or generic /api/v1 API is documented here. Keep secret credentials on trusted servers.

Documentation should distinguish implemented controls from planned services. This guide covers 3 practical actions, in the order they usually happen.

Do this first

Use app and key management where available..

Treat webhook registration as configuration only..

Then finish with

Ask support before relying on a feature without a documented working route..

Good to know

Everything here reflects the current Merchant Bridge interface. Labels and buttons may move as the product evolves, but the flow stays the same: prepare, act on the page this guide references, and confirm the result before moving on.

When something does not match what you see, the destination page for this guide is the source of truth.

Open the developer console

Need help with a specific error? Contact Merchant Bridge with the page and visible error, without passwords or secret keys.