Requests and responses
Ids
The id formats each resource uses.
Id formats
Ids keep the shapes Klaviyo uses, so a system that stores them as text keeps working when it switches.
| Resources | Format | Example |
|---|---|---|
| Profiles, events, campaigns, campaign messages | 26-character ULID | 01JC7Z3K9V8Q2M5N4R6T1W0Y8X |
| Lists, segments, metrics, flows, flow messages, templates, forms | 6 letters and digits | R2kX9a |
| The account (also its public key) | 6 letters and digits | AbC123 |
| Flow actions | A number, as a string | "90183" |
Things to know
- Store ids as text. Do not parse them or rely on their length beyond the formats above.
- ULIDs sort by the time they were made, which is why event ids here are ULIDs where Klaviyo's event ids are 11 characters.
- An id from one account means nothing in another. Requests only ever see the account the key belongs to.