-
Notifications
You must be signed in to change notification settings - Fork 11
Issues: reconciliation-api/specs
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Do we need JSON-LD support? If yes, what for?
question
Further information is requested
#183
opened Nov 11, 2024 by
acka47
Add missing fields to the JSON Schema for manifest
documentation
Improvements or additions to documentation
#180
opened Sep 13, 2024 by
thadguidry
Use some better HTML/Markdown format structure to show which query response fields are optional
documentation
Improvements or additions to documentation
#157
opened Mar 14, 2024 by
thadguidry
Simplifying authentication
API design
Where we discuss any changes we want to introduce in the API
#102
opened Dec 2, 2022 by
Abbe98
Property proposal responses do not have a corresponding JSON schema
#96
opened Aug 12, 2022 by
wetneb
Unify the syntax for property values in reconciliation queries and data extension responses
#94
opened Jul 27, 2022 by
wetneb
richer responses in the reconciliation API for more NER-like queries
#61
opened Dec 14, 2020 by
epaulson
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.