Developer & API

Endpoint

Also known as: API endpoint, URL path

3 min read·Updated 2026-05-06

Quick definition

An endpoint is a specific URL path on an API where a particular operation is performed. For example, `POST /v1/posts` on api.codivupload.com is the endpoint for creating new posts. Each endpoint has its own URL, accepted HTTP verb, request format, and response shape.

What is an endpoint?

An endpoint is a specific URL path on an API server where a particular operation can be performed. Endpoints combine a base URL (api.codivupload.com), a path (/v1/posts), and an HTTP verb (POST) to fully specify an operation. Together, this triplet — verb + path + base URL — identifies a unique API operation. POST /v1/posts on api.codivupload.com is for creating posts. GET /v1/posts/{id} on the same base is for retrieving a specific post by ID.

A REST API typically exposes 20-100 endpoints depending on its scope. Each endpoint does one specific thing: create a resource, read a resource, update a resource, delete a resource. The pattern of resource-per-endpoint is what makes REST APIs feel uniform and predictable across providers.

Endpoint conventions in REST

Five conventions that hold across nearly every REST API. (1) Plural resource names — `/posts` not `/post`, `/users` not `/user`. (2) Specific resource via ID — `/posts/{id}` for a single post. (3) Nested resources for sub-collections — `/users/{id}/posts` for a user's posts. (4) Verbs on resources, not in URLs — `POST /posts` to create, not `/createPost`. (5) Versioning in the path — `/v1/posts` to allow future v2 without breaking v1 clients.

Not every API follows these strictly; some ship endpoints like `/login` or `/refresh` that are RPC-style rather than RESTful. Don't get hung up on purism; the conventions are guidelines, not rules.

Frequently asked questions

How do I find an API's endpoints?+

Read the docs. Most modern APIs publish an OpenAPI specification (api.codivupload.com/public-openapi.json) that lists every endpoint, request shape, and response shape. Tools like Stoplight, Swagger UI, or Scalar render OpenAPI specs as browsable interactive documentation.

Are endpoints case-sensitive?+

Generally yes. /v1/posts and /v1/Posts are typically different endpoints. Most APIs use all-lowercase to avoid confusion.

Can multiple endpoints share the same URL?+

Yes, when the HTTP verb differs. POST /v1/posts (creates) and GET /v1/posts (lists) share a path but are different operations. The verb + path combination is the unique identifier.