Lucror Analytics — Reference
For detailed API documentation and to test the endpoints interactively, visit the Swagger UI: https://data.sqn.lucroranalytics.com/swagger/index.html
This guide will walk you through the steps to use the AuthenticateClient endpoint using Postman.
https://data.sqn.lucroranalytics.comOpen the Postman application on your machine.
AuthenticateClient endpoint:
POST https://data.sqn.lucroranalytics.com/data/authenticate/client
Key: Content-Type Value: application/json
{
"Username": "email@mail.com",
"Password": "pass****"
}
Click on the Send button to send the request.
After sending the request, you should see a response from the server. If the authentication is successful (HTTP 200), you will receive a JSON response containing the authentication token. Example response:
{
"Username": "email@mail.com",
"Token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}
If the supplied credentials are incorrect, the endpoint returns HTTP 401 Unauthorized with the body Invalid username or password.. A genuine server-side problem returns HTTP 500 Internal Server Error with the body Unable to authenticate client..
Copy the token from the response and use it in the Authorization header for subsequent requests to authenticate your API calls.
Key: Authorization Value: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
Once authenticated, you can use the following GET endpoints to retrieve data. Ensure that the token is included in the Authorization header. Each endpoint has a limit of 10 requests per second.
Score access: access to C-Score data is controlled per account. These endpoints require your account to be enabled for C-Score data; if it is not, the request is rejected with 403 Forbidden.
Endpoint: GET /data/issuer/cscore/latest?issuer={issuerName}&correlationId={correlationId}
Parameters:
:text). Omit to return all eligible issuers.Description: Returns C-Score data on the most recent snapshot date that has data — one row per issuer. Omit issuer for all issuers, or supply it to filter to a single issuer.
Endpoint: GET /data/issuer/cscore/timeseries?issuer={issuerName}&start={startDate}&end={endDate}&correlationId={correlationId}
Parameters:
:text). Omit to return all eligible issuers.:date yyyy-MM-dd).:date yyyy-MM-dd). Must be on or after start, and the range must not exceed your account's configured limit (1–365 days; 365 by default).Description: Returns one row per (issuer, snapshot date) in the supplied range.
Throttle and quota: the global per-IP rate limit of 10 requests/second applies. On the time-series endpoint, the date range may not exceed your account's configured limit (1–365 days; 365 by default). Unlike the issue endpoints, the C-Score endpoints have no per-user distinct-issuer quota and no cap on the number of issuers per request.
Score access: access to V-Score data is controlled per account. These endpoints require your account to be enabled for V-Score data; if it is not, the request is rejected with 403 Forbidden.
Endpoint: GET /data/issuer/vscore/latest?issuer={issuerName}&correlationId={correlationId}
Parameters:
:text). Omit to return all eligible issuers.Description: Returns V-Score data on the most recent snapshot date that has data — one row per issue (ISIN). Omit issuer for all issuers, or supply it to filter to a single issuer.
Endpoint: GET /data/issuer/vscore/timeseries?issuer={issuerName}&start={startDate}&end={endDate}&correlationId={correlationId}
Parameters:
:text). Omit to return all eligible issuers.:date yyyy-MM-dd).:date yyyy-MM-dd). Must be on or after start, and the range must not exceed your account's configured limit (1–365 days; 365 by default).Description: Returns one row per (issue, snapshot date) in the supplied range.
Throttle and quota: the global per-IP rate limit of 10 requests/second applies. On the time-series endpoint, the date range may not exceed your account's configured limit (1–365 days; 365 by default). Unlike the issue endpoints, the V-Score endpoints have no per-user distinct-issuer quota and no cap on the number of issuers per request.
These endpoints take one or more ISINs and return each issue's issuer C-Score and issue V-Scores in a single response. Multiple ISINs may be supplied as a comma-separated list (up to 50 per request). Each response row contains date, isin, issuerName, issuerCScore, inferredCScore (Y/N), issueVScore, and issueVScoreI.
Score access: access to C-Score and V-Score data is controlled per account. The C-Score fields (issuerCScore, inferredCScore) are returned only if your account is enabled for C-Score data, and the V-Score fields (issueVScore, issueVScoreI) only if your account is enabled for V-Score data. If your account is enabled for only one, the fields you are not entitled to are returned as null. If your account is enabled for neither, the request is rejected with 403 Forbidden.
Endpoint: GET /data/issue/scores/timeseries?isin={isin}&start={startDate}&end={endDate}&correlationId={correlationId}
Parameters:
:text). e.g. US1234567890,US0987654321.:date yyyy-MM-dd).:date yyyy-MM-dd). Must be on or after start, and the range must not exceed your account's configured limit (1–365 days; 365 by default).Description: Returns one row per (ISIN, snapshot date) in the supplied range, each containing the issuer C-Score and issue V-Scores.
Endpoint: GET /data/issue/scores/latest?isin={isin}&correlationId={correlationId}
Parameters:
:text). e.g. US1234567890,US0987654321.Description: Returns the issue scores on the most recent snapshot date that has data across the requested ISINs — one row per ISIN that has data on that date. ISINs with no data on the latest snapshot date are omitted, and an empty array is returned if none of the requested ISINs have data.
Throttle and quota: in addition to the global per-IP rate limit (10 requests/second), the issue endpoints enforce a per-user cap of 2,000 distinct ISINs queried within a rolling 1-year window. Re-querying an ISIN already counted in that window does not consume additional quota; each new ISIN in a request counts once. A maximum of 50 ISINs may be supplied per request, and the time-series date range may not exceed your account's configured limit (1–365 days; 365 by default).
These are essential for tracking individual requests through the system for debugging and tracing purposes. Always provide a correlationId if available, as it makes it easier to find and track logs if issues arise.
For all endpoints that require date parameters, use the yyyy-MM-dd format.
Ensure you have the correct JWT token in your cookies for authorization. If the token is missing or invalid, the system will return an error.
If something goes wrong, the API will return appropriate HTTP status codes:
/data/authenticate/client, the supplied username or password is incorrect. On data endpoints, the bearer token is missing or invalid.issuer value./data/authenticate/client). This will be logged with details if it occurs.The system logs all requests and responses along with any issues encountered. This helps with debugging if anything unexpected happens.