Skip to main content

HTTP methods

HTTP methods express intent. Even before you know a specific endpoint, the method tells you what kind of operation you are attempting.

Common methods​

GET​

Use GET for reads:

  • listing resources
  • retrieving a single resource
  • low-risk smoke tests during rollout

POST​

Use POST when creating a new resource or triggering a server-side action that is not purely a read.

PATCH or PUT​

Use update methods when changing an existing resource. Check the API Reference to see which method BrowserBee exposes for a given endpoint.

DELETE​

Use DELETE for removals or cleanup operations where supported.

Why method choice matters​

Method choice affects:

  • cacheability
  • idempotency expectations
  • retry safety
  • how your application explains intent to future maintainers

Wrap BrowserBee endpoints in application code that preserves the HTTP intent clearly. For example, keep read helpers separate from write helpers instead of hiding everything behind one generic request function.