invalid_request

HTTP status: 400 · Code: invalid_request

A bad parameter or body.

Why it happens

A parameter or the request body is wrong: a required field is missing, a value has the wrong type or is too long, or the JSON doesn’t parse. The detail in the response names the problem when the server can.

How to fix

Read the error message, then compare your request with the operation’s page in the API reference. The SDKs build the body for you, so with an SDK this usually means a value you passed is empty or out of range.

Catch it in your code

Every SDK throws one error type for a failed call. Match on its code, which is always invalid_request for this error, never on the message.

JavaScript and Next.js

import { ErrorCode, OrvanoError } from '@orvano/js'

try {
  // your Orvano call
} catch (error) {
  if (error instanceof OrvanoError && error.code === ErrorCode.invalidRequest) {
    // handle invalid_request
  } else {
    throw error
  }
}

Dart and Flutter

import 'package:orvano_flutter/orvano_flutter.dart'; // or orvano_dart on a server

try {
  // your Orvano call
} on OrvanoException catch (error) {
  if (error.code != ErrorCode.invalidRequest) rethrow;
  // handle invalid_request
}

.NET

using Orvano;

try
{
    // your Orvano call
}
catch (OrvanoException error) when (error.Code == ErrorCode.InvalidRequest)
{
    // handle invalid_request
}

The error also carries the HTTP status (400), a message, and a request ID. Quote the request ID when you report a problem: the server logs it with the failure. See Errors for how errors work in every SDK, or every error code.