Skip to content
Error codes · Authentication & API keys

RU-1010: Agent sign-up request refused

The request to start an account for a person (`POST /api/v1/signup-requests`) was not valid, so no email was sent. The `error` field names the first problem.

On the wire

Ships with HTTP status 400, carrying "code": "RU-1010" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • The body is not JSON, or `email` is missing or is not a deliverable address.
  • The address belongs to a disposable email service, which cannot open an account.
  • `agentName` is longer than 60 characters, or contains a link or characters other than letters, digits, spaces and . _ - ( ) + /.
  • `product` is not one of status, monitor or errors.

How to fix it

  1. Send a JSON body with the person's own email address, for example `{"email": "you@example.com", "agentName": "My agent"}`.
  2. Ask the person for the address they read every day, not a disposable one.
  3. Give `agentName` as a short plain name, or leave it out.

Related codes

  • RU-2011: Too many agent sign-up requests

Still stuck?

Ask support and mention RU-1010: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.