René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Event metadata validation is too strict","articleBody":"`CreateDataEventRequest` models (`CreateDataEventRequestWithId`, `CreateDataEventRequestWithUserId`, `CreateDataEventRequestWithEmail`) only accept string metadata, conflicting with Intercom’s documented metadata types (strings, numbers, Unix timestamps, rich links, monetary amounts).\n\n### Steps to reproduce\n\n1. Instantiate any variant with non-string metadata:\n\n```py\nfrom intercom.types import CreateDataEventRequestWithUserId\n\nCreateDataEventRequestWithUserId(\n    user_id=\"123\",\n    event_name=\"test-event\",\n    created_at=1671028894,\n    metadata={\"load\": 3.67},\n)\n```\n\n2. Observe `ValidationError` because metadata.load is not a string.\n\n### Expected behaviour\n\nAllow every metadata type listed at https://developers.intercom.com/docs/references/rest-api/api.intercom.io/data-events/createdataevent.\n\n### Actual behaviour\n\nValidation forces all metadata values to be plain strings.\n\n### Suggested Fix\n\nRelax the metadata value type in all `CreateDataEventRequest*` models (e.g., use `typing.Any` or a union covering the documented types) so the SDK aligns with Intercom’s API specification.","author":{"url":"https://github.com/jpvanhal","@type":"Person","name":"jpvanhal"},"datePublished":"2025-11-19T09:47:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/286/python-intercom/issues/286"}