What you need to do Endpoint Know before you build
Create or change one user profile POST /api/users/update (500 requests a second) Fields you send are merged in. Fields you leave out stay as they were, so this is safe for partial updates.
Load or refresh many profiles at once POST /api/users/bulkUpdate (5 requests a second) Top-level fields you send overwrite what's there. Set mergeNestedObjects to true if nested objects should be merged rather than replaced.
Record something a user did POST /api/events/track (2,000 a second) or /api/events/trackBulk (10 a second) Bulk and single events are processed separately. Pick one endpoint per event stream or the order isn't guaranteed.
Purchases and abandoned carts POST /api/commerce/trackPurchase and /api/commerce/updateCart A tracked purchase clears the user's shoppingCartItems, which is what ends an abandoned-cart journey for them.
Product or content data for personalisation POST /api/catalogs/{catalogName}/items (100 a second, per key) Up to 1,000 items per request. An item with an existing ID is overwritten in full unless you set replaceUploadedFieldsOnly.
Start a journey or send one email from code POST /api/workflows/triggerWorkflow or /api/email/target Iterable advises leaving at least 60 seconds between updating a user and a send that depends on that update.
Pull campaign results out GET /api/export/data.csv (4 requests a minute) Slow by design. For anything near real time, have Iterable push events to you with a webhook instead.