# Signing Errors

{/* AUTO-GENERATED - DO NOT EDIT. Run: bun run apps/gateway/docs/scripts/generate-error-docs.ts */}

Error codes with the `signing-` prefix. See the
[Errors overview](/overviews/errors) for the response format and the code convention.

## Signing

<table className="wrap-first-col error-table">
  <thead>
    <tr>
      <th>Error Code</th>
      <th>HTTP Status</th>
      <th>Error Message</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>`signing-3000`</td>
      <td>400</td>
      <td>Tesser can't build a wallet payload for this signCreateWallet call because its query is invalid: type must be stablecoin_ethereum, name can't be empty, and the query takes only name, type, organizationId and timestampMs. Fix the name and type passed to signCreateWallet, or upgrade the SDK if they're right, and call it again; retrying unchanged won't help</td>
      <td>signCreateWallet in the Tesser SDK fetches the wallet payload it signs from Tesser, sending the wallet's name and type, the signing key's organizationId and a timestampMs. Returned when that query is invalid: type isn't stablecoin_ethereum, name or organizationId is empty, or a parameter is missing, repeated or not one of these four. The invalid_parameters param names them. Pass a non-empty name and type stablecoin_ethereum to signCreateWallet; if they're right, upgrade the SDK to 0.2.0 or later. Retrying the same call won't help.</td>
    </tr>
    <tr>
      <td>`signing-4010`</td>
      <td>401</td>
      <td>Tesser couldn't authenticate this signCreateWallet request: the X-Stamp header is missing or doesn't match the request, the signing key isn't active for this workspace in this environment, or timestampMs is more than 5 minutes from Tesser's clock. Check the signing key, apiBaseUrl and the host clock, then call signCreateWallet again; resending the same request won't help</td>
      <td>signCreateWallet authenticates its request to Tesser with an X-Stamp header: a Turnkey stamp made with your signing key over organizationId, name, type and timestampMs. Returned when the stamp is missing or malformed, its signature doesn't match the query, organizationId matches no workspace in this environment, the key isn't an active signing key of that workspace, or timestampMs isn't within 5 minutes of the current time. The reason param says when the timestamp or the header's format is the problem. Without apiBaseUrl the SDK tries production first, so a sandbox key gets this error there before the SDK tries sandbox. Check that the signing key is active for this workspace, that apiBaseUrl points at the key's environment and that the host clock is accurate, then call signCreateWallet again. Resending the same request won't help.</td>
    </tr>
    <tr>
      <td>`signing-4290`</td>
      <td>429</td>
      <td>Too many unsigned payload requests. Retry shortly</td>
      <td>Too many unsigned payload requests reached the service in a short time. Retry the same request after a short delay.</td>
    </tr>
    <tr>
      <td>`signing-5000`</td>
      <td>502</td>
      <td>Tesser couldn't read the workspace's Turnkey organization to build the unsigned payload: Turnkey failed or returned an answer Tesser couldn't read. Nothing was created. Request the unsigned payload again in a few minutes, and contact Tesser support if it keeps failing</td>
      <td>To build the unsigned payload, Tesser reads the workspace's Turnkey organization: its API keys, to check the stamp's key, and, when Tesser has no master wallet on record yet, its wallets. Turnkey failed or returned an answer Tesser couldn't read. Nothing was created. Request the unsigned payload again in a few minutes; contact Tesser support with the request_id if it keeps failing. When the organization holds no wallet, accounts-3128 is returned instead.</td>
    </tr>
  </tbody>
</table>
