Referring the customer number implicitly in RESTful API

Asked Jun 24 '20 at 12:26

Active Jun 24 '20 at 12:36

Viewed 22 times

GET /customers/{customer-id}

I am designing an API where the customer gets identified with the Authorization token passed in the request header. This means the above API doesn't require the customer-id in the URI.

Wondering what is recommended or the best options? These are some of the options which I can think of:

GET /customers/me
GET /customers/self
GET /customers/this

I have used 'me' a few times and the API consumers were fine with this. Thoughts?

edited Jun 24 '20 at 12:36

asked Jun 24 '20 at 12:26

rai.skumar

10,309
6
39
55

1

This was discussed in this post. https://stackoverflow.com/questions/36520372/designing-uri-for-current-logged-in-user-in-rest-applications. – EnterSB Jun 24 '20 at 12:30
1

I agree with /me. – Shawn de Wet Jun 24 '20 at 12:30
The question is opinion-based as all approaches are valid and there are no specific restrictions. – cassandrad Jun 24 '20 at 16:03

Referring the customer number implicitly in RESTful API

0 Answers0