Hello fellow Karbonites!
I've been exploring the new tags feature in the API for our small accounting firm's integrations, and I wanted to share my understanding and assumptions. I'd appreciate any confirmations, corrections, or additional insights you might have.
From what I've gathered:
- The tags feature seems to function as key-value pairs, allowing us to add metadata to our API objects.
- Tags appear to be accessible via both GET and POST requests. I assume we can add tags when creating or updating objects and retrieve them when fetching object details.
- My guess is that these tags are primarily for backend use and won't be visible in the UI. This could make them perfect for storing integration-specific data without cluttering the user interface.
- I'm assuming there's no built-in limit on the number of tags we can use per object, but there might be practical limits due to request size restrictions.
- Regarding limitations, I'd expect:
- A maximum length for tag keys and values, possibly around 255 characters each.
- Restrictions on special characters in tag keys, likely limiting them to alphanumeric characters, hyphens, and underscores.
- A soft limit on the total number of tags per account to prevent abuse, maybe in the thousands.
- For data types, I'm guessing tags are limited to strings. It would be interesting if they supported other data types like numbers or booleans natively.
I'm particularly interested in using tags to store cross-system identifiers and metadata for our integrations. Has anyone else found innovative uses for this feature?
Looking forward to hearing your thoughts and experiences with the new tags feature!
cc:
