Support for builders

Clear the blocker. Keep building.

Start with the exact guide, then open a conversation when you need help. Support should understand your integration, not make you repeat it.

Check service status→

NexoRouter / support

Documentation first

Short paths for a known issue or implementation decision.

Human when needed

A conversation for the cases that do not fit a generic answer.

A clear path

From question to next action.

  1. 01

    Find the answer

    Practical guides for authentication, models, payments, and common errors.

  2. 02

    Check the status

    Separate an integration error from an operational incident before escalating.

  3. 03

    Talk with context

    Open support from the site so the team can continue the conversation without losing the thread.

Starting points

Answers teams need most often.

Start an integration

Create a key, use the base URL, and make your first request.

Open guide →

Investigate an error

Review limits, timeouts, keys, and API responses.

Open guide →

Manage balance and payments

Understand top-ups, available balance, and Stripe confirmations.

Open guide →

Already know what you need?

Check status or open a conversation. You do not need to start from zero.

Developer support — NexoRouter