Developer / Referensi
Fetch several series in one request
GET /v1/series
Isi referensi
Multi-series fetch per **ER-D5** (`docs/strategy/DECISIONS.md`, "Decided: Ade — approved"): comma-separated `ids`, capped at 50 distinct series per request.
Same response shape as `/series/{seriesId}`, wrapped in an array so the two are interchangeable. `not_found` is **always present**, even when empty — a consumer assembling a brief has to be able to tell "this series has no observations in the window" from "this series does not exist", and an absent key makes those identical.
The whole request is rejected if any `id` is malformed, rather than that id being dropped: a silently short array cannot be reconciled against what the caller asked for.
Deskripsi endpoint berasal dari spesifikasi dan masih berbahasa Inggris.
Parameter
| Parameter | Lokasi | Tipe | Aturan |
|---|---|---|---|
| ids | query | string | Wajib |
| from | query | string (date) | Opsional |
| to | query | string (date) | Opsional |
| limit | query | integer | Opsional |
Hak redistribusi mengikuti lisensi seri. Data tampilan saja tidak tersedia sebagai baris mentah.
Respons
| Kode | Keterangan |
|---|---|
| 200 | Series found, plus the ids that do not exist |
| 400 | `missing_ids`, `empty_series_id`, `invalid_series_id`, `too_many_series`, `invalid_from`, `invalid_to`, `invalid_limit` |
| 401 | missing_api_key |
| 429 | rate limit exceeded |
Dibangkitkan dari openapi.yaml, spesifikasi yang sama dengan /v1/openapi.yaml.
Permintaan / contoh
curl -H "x-api-key: $SUMBER_KEY" \
"https://api.sumber.io/v1/series"