More

Good practices

Habits that keep an integration safe, quick and easy to maintain.

  • One key per system, named after it, so you can revoke one without stopping the others.
  • Give each key only what it needs: the activities it reads, and no personal details when codes are enough.
  • Keep keys in your server's secret settings. If one leaks, revoke it and create a new one.
  • Create the next key before the current one expires, then switch over.
  • Ask for fields explicitly in production code: your file keeps the same columns if defaults ever grow.
  • Sync with changed_since instead of re-reading whole months every hour.
  • Filter, group and sort in the request rather than downloading everything: smaller pages, fewer requests, and the same answer every time.
Good practices — Planifizer API docs