Join our Newsletter — 33% off our NHI Course
Foundations & NHI Taxonomy

POST

← Back to Glossary
By NHI Mgmt Group Updated November 18, 2026 Domain: Foundations & NHI Taxonomy

POST is the HTTP request method used to submit data to a server for processing, often to create a resource or trigger an action. It usually carries data in the request body and is not idempotent, so repeated requests can create duplicate records or repeat a state change.

What HTTP POST Means for Web Requests

POST is one of the core HTTP request methods, so the most important idea is that it carries data to a server for processing rather than simply retrieving a representation. In practice, that makes it the method used when a browser, script, or API client submits form data, starts a workflow, or asks the server to create or change state.

Because POST is a transport and action verb rather than a security control, its significance comes from how applications implement it. The same method can be used for benign business operations, authenticated workflows, or sensitive actions such as account changes, record creation, or approval steps.

Why POST Is Not Idempotent

POST is usually non-idempotent, which means repeating the same request can produce a different result each time. That property is useful when the server is expected to create a new object, enqueue work, or record an event, but it also means retries, duplicate submissions, or network glitches can lead to repeated side effects.

This is why POST behaves differently from methods that are intended to be safe to repeat. If a client replays a POST without server-side deduplication, the application may create duplicate rows, duplicate orders, repeated notifications, or multiple workflow executions.

For teams designing APIs, the key point is not that POST is inherently unsafe, but that the server must define clear semantics for repeated submission. If the business action must happen once, the application needs an application-level idempotency strategy rather than relying on HTTP method behavior alone.

POST in APIs and Application Design

In modern web and API design, POST is often the default method for operations that do not fit clean resource retrieval. That includes creating records, triggering commands, submitting login forms, or sending data that is too large or sensitive to place in a URL.

Many security and reliability decisions flow from that design choice. POST requests may carry credentials, session-related form data, JSON payloads, or user-entered content, so the receiving endpoint must validate input, enforce authorization, and handle state changes carefully. A POST endpoint is only as safe as the server-side checks behind it.

For example, an API may accept a POST to create an invoice, submit a support ticket, or request a password reset. The method itself does not guarantee that the action is legitimate, authorized, or unique, which is why the surrounding application logic matters more than the verb alone.

Common Failure Modes and Security Implications

POST introduces operational and security concerns when applications assume the client will behave perfectly. Duplicate submissions can appear after users double-click a button, browsers retry requests, reverse proxies replay traffic, or integrations resend messages after a timeout.

Failure mode: repeated POSTs can create duplicate objects, inconsistent business state, or unintended repeated side effects when the server lacks replay protection, deduplication keys, or transactional safeguards.

Impact: users may be charged twice, records may be duplicated, automation may run more than once, and downstream systems may treat the same action as distinct events. In sensitive workflows, that can become an integrity issue as much as a usability issue.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP ASVS and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV2 — Validation and Business LogicPOST handlers depend on server-side validation and action logic.
V8 — AuthorizationPOST commonly triggers privileged or state-changing operations that must be authorized.
V16 — Security Logging and Error HandlingRepeated or failed POST submissions need observable logging and safe error handling.
Recommendation — Validate POST inputs and business rules before allowing state-changing actions. Enforce authorization on every POST endpoint that changes data or triggers actions. Log POST outcomes and handle failures without exposing sensitive processing details.
NIST SP 800-53 Rev 5SI-10 — Information Input ValidationPOST request bodies are application input that must be validated before use.
AC-3 — Access EnforcementPOST endpoints often create or change records and therefore require access checks.
Recommendation — Validate POST bodies and reject malformed or unexpected data before processing. Apply access enforcement to every POST action that changes protected resources.

Practitioner Guidance

Why practitioners should care: POST is the method most likely to change server state, so the backend must treat every POST handler as a potential business-critical entry point. Design the endpoint so that authorization, validation, logging, and duplicate suppression happen on the server, not in the client.

What to watch for: repeated submissions after retries, network interruptions, and user refreshes are normal conditions, not exceptional ones. If the action cannot safely happen twice, the implementation should include idempotency keys, transaction controls, or equivalent deduplication logic.

Practitioner takeaway: POST is not dangerous by itself, but it demands stricter server-side control than a read-only method because its repeated execution can change state more than once.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org