QuantaAPI
Dashboard
Guides

Endpoints

An endpoint is a path plus an HTTP method inside a collection. Its path and method together identify it.

REST only
4 min read

Endpoints are created inside a collection. Each endpoint stores its own response body, configuration, and data requirements. The same path can be reused with a different method — GET /users and POST /users are two separate endpoints.

Create an endpoint

  1. 01
    Open the collectionFrom the dashboard or the sidebar, open the collection that should own the endpoint.
  2. 02
    Click Create EndpointThe dialog asks for a path, a type, and a method.
  3. 03
    Enter a pathIt must start with /, for example /users or /v1/orders. The path is matched exactly at request time.
  4. 04
    Choose a methodPOST is preselected. Pick the method your consumers will use.
  5. 05
    SubmitThe endpoint is created with default configuration and appears as a card in the collection.
Path and method are unique per collectionCreating the same path with the same method twice is rejected with 409 CONFLICT. Use a different path or a different method.

Path rules

  • Required, and must start with /.
  • Cannot be only /, and cannot end with /.
  • At most 200 characters, with no spaces.
  • No ?, #, //, %, :, { or } — query strings and dynamic segments are not supported.
  • Allowed characters per segment: letters, numbers, -, _, . and ~.
  • No . or .. segments.
No dynamic segments/users/:id and /users/{id} are rejected. Because matching is exact, query strings are not part of the path either — send values in the request body or in headers.

Supported methods

  • GET
  • POST
  • PUT
  • DELETE
  • PATCH
  • OPTIONS
  • HEAD

For POST, PUT, and PATCH, the request body is parsed and validated against the body requirements. For every other method only headers are validated; the body is ignored even if one is sent.

Each endpoint keeps its own response body, behavior settings, and request requirements. Every part is edited in its own tab, so you never edit raw configuration by hand.

Edit or delete

The path can be edited from the endpoint header. Delete the endpoint from its card menu; deletion also removes its request logs and immediately makes matching calls return 404.