Exto
API Status
  • Introduction
  • Architecture
    • Microservice Architecture
    • Security
  • Release Cycle
  • Integration
    • Best Practices
    • Endpoints
    • Response Format
    • Error
    • Data Formats
    • Data API
      • Generate API Key
      • API
      • ID/Access Token
      • Azure API Gateway
      • Filter Master Record/Custom Module Records
  • Installation
    • Installing Exto on Kubernetes
      • Prerequisite
      • Installing Exto
        • Setup
        • Configuration
        • Installation
        • Purging
      • Tips and Tricks
        • AKS to use existing storage account
        • AKS with Application Gateway Ingress Controller
        • AKS Private Cluster
Powered by GitBook
On this page

Was this helpful?

  1. Integration

Error

PreviousResponse FormatNextData Formats

Last updated 3 months ago

Was this helpful?

Errors from the APIs are indicated by the HTTP response status code and also included in the body of the response, according to the . The following errors are possible:

HTTP Status
Name
Description

200

OK

The request was successful, and the response contains the requested data.

201

CREATED

The request was successful, and a new resource was created.

400

BAD REQUEST

The request is malformed or contains invalid parameters.

401

UNAUTHORIZED

The request lacks valid authentication credentials.

404

NOT FOUND

The requested resource could not be found.

405

METHOD NOT ALLOWED

The HTTP method used is not allowed for the requested resource.

413

PAYLOAD TOO LARGE

The request body is too large to be processed by the server.

414

URI TOO LONG

The URI provided in the request is too long for the server to process.

422

UNPROCESSABLE ENTITY

The request is well-formed but cannot be processed due to semantic errors.

429

TOO MANY REQUESTS

The client has sent too many requests in a given amount of time (rate limiting).

500

INTERNAL SERVER ERROR

The server encountered an unexpected condition that prevented it from fulfilling the request.

502

BAD GATEWAY

The server received an invalid response from an upstream server.

503

SERVICE UNAVAILABLE

The server is currently unable to handle the request due to temporary overload or maintenance.

504

GATEWAY TIMEOUT

The server, acting as a gateway, timed out while waiting for an upstream response.

response format