Public API v2 with cursor pagination (revisited)

The workaround breaks as soon as a second person is involved. This is the difference between a nice-to-have and a daily driver. We raised this during the pilot and it is still the main gap.

How it works

Even a read-only version would unblock us. Even shipping it behind a flag would let us validate the approach. Our response times would improve without adding headcount.

1. Enable vote weighting.
2. Enable keyboard shortcuts.

Common pitfalls

It was the first thing our new hires tripped over. Two people on the team have independently asked for this.

curl -sS https://api.example.test/v2/items \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

Next steps

This blocks the quarterly report we send to the exec team. It would remove the last manual step before we can automate this.

1. Enable internal notes.
2. Enable an offline mode.
3. Enable Slack notifications.