Skip to content

Align the 2.17 data attribute, data event, data export and visitor endpoints with what the API does - #760

Open
markdennis22 wants to merge 3 commits into
mainfrom
markdennis/2-17-data
Open

markdennis22 wants to merge 3 commits into
mainfrom
markdennis/2-17-data

Conversation

@markdennis22

Copy link
Copy Markdown
Contributor

Why?

The 2.17 spec for the data attribute, data event, data export and visitor endpoints didn't match the API. The export docs gave the wrong job limit, link expiry and download format. Event metadata was typed as strings only, the visitor request and response shapes were off, and most error responses were missing. Only the 2.17 spec changes, and the SDKs aren't generated from 2.17, so they are unaffected.

How?

Corrects these endpoints and their schemas to match the API's current behaviour, and adds the OAuth scopes each endpoint accepts to its description.

Generated with Claude Code

markdennis22 and others added 3 commits October 22, 2026 09:50
… reference with what the API does

Corrects the data type enums, event metadata and identifier rules, the export limits, expiry and download format, and the visitor request and response shapes, documents the error responses the API returns, and adds the accepted OAuth scopes to each operation.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…a details

convertVisitor listed visitor twice in required. The visitor avatar description no longer claims an object form its string schema can't hold, the data_type description now says only relationship attributes can't be created through the API, and the millisecond since and before parameters on the events list are int64.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A list attribute is stored and returned as a string attribute with its choices in options, so the response never carries data_type options.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant