PORTOS Developers
  • 👋Introduction
  • 📖Glossary
  • HTTP Status codes
  • Error models
  • Error codes
  • Validation constraints
  • Resource names
  • 🔒User rights
  • Device environments
  • 🌍Localization
  • 🔍NData query syntax
  • OpenAPI specification
  • Data models
  • Authentication
    • 🔐Authentication schemes
      • JWT Bearer Authentication
      • HMAC Authentication
  • ⚡Notifications
    • SignalR
    • Webhooks
  • API reference
    • 🔑API keys
    • 🛍️Article categories
    • 💼Companies
    • 💱Currencies
    • 👫Customers
    • 📈Daily sales reports
    • 🖥️Devices
    • 🖨️Fiscals
    • ❤️Health check
    • 📃License
    • 🎚️Modifiers
    • 👨‍🍳Order endpoints
    • 🛎️Orders
    • 🪙Payment types
    • ☕Plus
    • 🔏Roles
    • 🔐Sessions
    • ⚙️Settings
    • 🔎Stock takings
    • 🔢Stock transfer numbering
    • 🚚Stock transfers
    • 📦Stocks
    • 🧾Tickets
      • Ticket Model States
      • Ticket Operations and User Rights
      • Ticket Model Mathematics
    • 👨‍💼Users
    • ⚖️Vats
    • 🪑Zones
  • 3rd Party Integrations
    • Introduction
    • Online orders API
    • Rewards API
    • PDA Files
  • Previous versions
    • Migration to V4.1
    • Migration to V4
    • Legacy documentation
Powered by GitBook
On this page
  • Successful status codes
  • Error status codes

Was this helpful?

HTTP Status codes

List of all HTTP status codes used by API

PreviousGlossaryNextError models

Last updated 2 years ago

Was this helpful?

Successful status codes

HTTP Status
Description

200

OK

Operation was successful. Payload is located in response body.

201

Created

Create operation was successful. Payload is located in response body.

202

Accepted

Operation request is accepted. The task will continue in background.

204

No Content

Operation was successful. There is no payload in response body.

Error status codes

Statuses in range 400-499 are considered as client errors, range 500-599 represents server errors.

HTTP Status
Error model
Description

400

Bad Request

Request is invalid or contains invalid data.

401

Unauthorized

User is not logged in, or user authentication has failed (invalid credentials).

403

Forbidden

User is logged in but does not have sufficient access rights, or operation itself is forbidden.

404

Not found

Resource is not found.

423

Locked

Resource is locked (temporarily used by another part of application).

500

Internal server error

Error occured on server side.

PortosValidationProblemDetails
ProblemDetails
ProblemDetails
ProblemDetails
ProblemDetails
ProblemDetails