The REST architectural style, as described by Roy Fielding in 2000, includes a uniform interface constraint
REST is defined by four interface constraints: identification of resources; manipulation of resources through representations; self-descriptive messages; and, hypermedia as the engine of application state.
Resources are a generalization of documents; /api/v1/login
would be an identifier for a document, POST /api/v1/login
would be a request that some modification be made to the document.
the URI format has nothing to do with if it is a REST API or not?
Exactly right. REST does not care what spelling conventions you use for your resource identifiers (so long as they are consistent with the syntax rules described by RFC 3986).