MSPro Services
About
  • MSPro.Services
    • Endpoints
      • Documents
        • Document Properties
          • Rank
          • Context
        • Use-Cases
          • Service Requests
          • CSV Files Import and data processing
      • Render Engine
        • The Basics
        • Templates on the /docs endpoint
          • Page 1
      • The Mirror
    • Hosting
    • Plans
    • Accounts
      • SharedAccount
    • General Information
      • HTTP-Status Codes
      • Custom Headers
      • Response Schema
  • MSPro Client
Powered by GitBook
On this page
  • 200 - Ok: Success with data
  • 204 - NoContent: Success no data
  • 400 - Bad Request
  • 404 - Not Found
  • 500 - Internal Server Error
  1. MSPro.Services
  2. General Information

HTTP-Status Codes

The web-service uses five different responses with a dedicated meaning (see also Response Schema).

200 - Ok: Success with data

The endpoint returned the expected data.

204 - NoContent: Success no data

The endpoint's expectations have been meet (success) but there is not data returned.

400 - Bad Request

The endpoint could not provide the requested results because of the request parameters. If you would change the request parameters the endpoint would eventually respond the expected data.

This status-code is used with query parameters or request bodies, only. A path-segment which is used as a resource-id, for example, is not considered to be request data. It is a URL

See HTTP-Status Codes

404 - Not Found

The not-found status code is used only when a URL path is invalid.

It is not used to respond that a resource was not found. Finding a resource is a business use-case while 404 is a technical representation of a "URL endpoint not found".

HTTP 404 (Not Found) is a standard response code indicating that the requested resource could not be found on the server.

500 - Internal Server Error

Something went wrong on the server (Exception). See response details for more information.

Last updated 3 months ago