Speeda Ranking API
The Speeda Ranking API provides Japan listed company and industry rankings based on page views and engagement metrics. Use it to retrieve ranked lists of companies and industries by user activity on SPEEDA, with optional per-page-type breakdowns.
Base URL
https://datafeed.ub-speeda.com/japan/ranking/v1
Required Scopes
| Scope | Description |
|---|---|
speeda-ranking.companies | Read listed Japanese company ranking data |
speeda-ranking.industries | Read industry ranking data |
speeda-ranking.company-pages | Read listed Japanese company page-type ranking data |
Endpoints at a Glance
| Method | Endpoint | Description |
|---|---|---|
| GET | /companies | Get Japanese company rankings with engagement metrics |
| GET | /company-pages | Get Japanese company rankings with per-page-type breakdown |
| GET | /industries | Get industry rankings with engagement metrics |
Datetime Range Parameters
All ranking endpoints require a datetime range. The maximum span is 365 days.
| Parameter | Type | Required | Description |
|---|---|---|---|
start_datetime | string (date-time) | Yes | Start datetime in ISO 8601 format (yyyy-MM-dd'T'HH:mm:ss) |
end_datetime | string (date-time) | Yes | End datetime in ISO 8601 format (yyyy-MM-dd'T'HH:mm:ss) |
Pagination
All list endpoints support offset-based pagination:
| Parameter | Type | Default | Description |
|---|---|---|---|
page | integer | 1 | Page number (1-indexed) |
page_size | integer | 25 | Items per page |
note
The /industries endpoint defaults to page_size=1000.
Response metadata:
{
"data": [...],
"page": 1,
"pageSize": 25,
"total": 100
}
Error Handling
| Status Code | Description |
|---|---|
200 | Success |
400 | Bad request — invalid datetime format, end_datetime before start_datetime, or date range exceeds 365 days |
500 | Internal server error |
Error response format:
{
"error": {
"code": "INVALID_DATE_RANGE",
"message": "end_datetime must be after start_datetime",
"traceId": "abc123",
"details": [
{
"field": "end_datetime",
"issue": "must be after start_datetime"
}
]
}
}
Versioning
The API is versioned via the URL path (/v1/). Breaking changes will result in a new version. Non-breaking additions (new optional fields, new endpoints) may be introduced within the current version.