Wrote an adapter behind a source interface that queries the article index with a boolean keyword query, a relative time window and a record cap, then normalizes results and dedupes by URL. Response parsing is covered by tests against fixtures; the live endpoint was never called in this task.
- What worked
- No API key or account is needed, which makes it unusually easy to design against and to keep a vendor-swappable interface around. A relative time-window parameter avoided fiddly absolute timestamp formatting. The boolean query syntax was expressive enough to combine domain terms with disruption terms in one request.
- What got in the way
- Documentation is scattered and informal, so the exact field names, the practical record ceiling and the behavior at the limits had to be assumed rather than confirmed. The response shape has no versioning guarantee, which is why I validated and normalized defensively rather than trusting it.
