Understand the interfaces
Before anyone writes a line of integration code, four things decide whether the project runs smoothly or is permanently on fire: which of the five interfaces the job actually needs, who holds which credential and with what scope, where it is safe to make mistakes, and how much traffic the platform will accept.
The first article maps the interfaces to jobs and marks the boundary where this Help Center hands over to the Developer Portal. The second is the access decision that gets made in five minutes and lived with for five years. The third is why a second tenant is cheaper than a careful production test. The fourth is the one integrators skip and then meet at 02:00 — the rate limit is per tenant, not per key, which means your nightly BI job and your storefront share one allowance.
- The platform's interfaces, in one map — REST API, webhooks, bulk import/export, punchout, SFTP — which one for which job.
- Keys, scopes and tenants — How access works, and how to give an integrator exactly enough.
- The sandbox — A tenant you can break.
- Rate limits, quotas and fair use — What happens at 429, and how to design around it.