Reference

Changelog

Additive changes ship as they are ready. Anything that could break a working integration is announced by email to key owners before it happens, and listed here.

How changes are handled

New fields, new endpoints and new enum members can appear at any time. They will not break a client that ignores what it does not recognise, so build one that does.

Removing a field, renaming one, changing a type or tightening validation counts as breaking. Those get at least 90 days of notice by email to every team with an active API key, and stay listed here for a year afterwards.

2026

September

First public release of these docs. The API itself has been running behind the portal since the platform launched; this is the point where it becomes something you can build against with a key of your own.

• Scoped API keys, with separate live and sandbox environments.
• Public documentation for projects, engagements, iwi lookup, teams, users, groups and uploads.
• A machine readable OpenAPI specification at https://api.iwiconnect.com/openapi.json, covering every endpoint on these pages.

On the list

Webhooks are the most requested thing and the most likely next addition, which would replace the polling described in pagination. Nothing is promised here with a date on it, because a date we miss is worse than no date at all.

If there is something you need, email support@iwiconnect.com and tell us what you are trying to build. Requests that describe a real workflow get built ahead of requests that describe an endpoint.