You need to have the following before you can start using Lens APIs:
- Granted access to our API service.
- Create an Access Token from your user profile page.
- Basic knowledge of API structure and JSON formatting.
- Any API Client (cURL, Postman, etc.)
As of the current version, Lens offers the following API endpoints:
- Scholarly Works:
Swagger Documentation is available here:
Authorization: Bearer your-access-token
To ensure our public API endpoints remain usable by everyone and to maintain the server’s optimal availability, a rate limiting mechanism is being used to temporarily block any clients that reduce the server’s performance. The applied rate limits will be included in the following HTTP response headers:
x-rate-limit-remaining-request-per-minute: Number of requests allowed in a minute
x-rate-limit-retry-after-seconds: Time in seconds until next request can be performed
x-rate-limit-reset-date: Rate limit will get reset at this date
x-rate-limit-remaining-request-per-month: Number of API calls allowed till the reset date above
x-rate-limit-remaining-record-per-month: Number of remaining records that can be fetched
Once you go over any rate limit you will receive a
429 - Too many requests error with respective messages.
|200 - Ok||Valid response from the server|
|400 - Bad Request||Malformed request or incorrect fields/values provided|
|401 - Unauthorized||Authentication credentials might be incorrect or missing|
|404 - Not Found||Incorrect Resource URL / Empty Result for supplied queries / Expired
|415 - Unsupported Media Type||Request body is not json or
|429 - Too Many Requests||You have exceeded the number of allowed calls|
|50x - Internal Server Error||An error occurred on API server side.|