Skip to content

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.

Sign up for GitHub

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

49 Open 51 Closed
49 Open 51 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Clarify expected behaviour on invalid input
#171 opened Apr 12, 2024 by wetneb
Inconsistent field naming in data extension property settings
#164 opened Apr 6, 2024 by wetneb
1
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
1
@thadguidry
Clarify default value of 'required' and 'match_quantifier' field on matching conditions
#155 opened Feb 26, 2024 by wetneb
Minor inconsistency with Reconciliation Query's type field
#152 opened Jan 11, 2024 by derenrich
2
Move <dl> elements out of <p> elements
#151 opened Jan 10, 2024 by wetneb
2
Schema mixes snake and camel case?
#150 opened Jan 10, 2024 by derenrich
1
2
Suggestion: add more easy-to-understand explanation of examples
#146 opened Nov 27, 2023 by GO5IT
2
Reformulate the 'type' parameter as another property
#145 opened Nov 21, 2023 by wetneb
1
Remove notion of "notable" types
#143 opened Oct 8, 2023 by wetneb
1
Support for multi-lingual candidate names
#138 opened Sep 14, 2023 by saumier
18
use semantic versioning for protocol versions (?)
#135 opened Sep 7, 2023 by awagner-mainz
2
Add an additional property match context to the features API design Where we discuss any changes we want to introduce in the API enhancement New feature or request
#128 opened May 11, 2023 by thadguidry
7
I18n checklist: text direction
#126 opened May 9, 2023 by fsteeg
13 of 19 tasks
I18n checklist: language
#125 opened May 9, 2023 by fsteeg
17 of 22 tasks
Normalize field descriptions in JSON schemas
#120 opened Mar 27, 2023 by wetneb
Add type parameter to suggest property queries
#104 opened Dec 16, 2022 by wetneb
6
Simplifying authentication API design Where we discuss any changes we want to introduce in the API
#102 opened Dec 2, 2022 by Abbe98
Support HTTP QUERY method
#98 opened Aug 29, 2022 by acka47
Property proposal responses do not have a corresponding JSON schema
#96 opened Aug 12, 2022 by wetneb
Normalize naming conventions across the API
#95 opened Jul 28, 2022 by wetneb
2
Unify the syntax for property values in reconciliation queries and data extension responses
#94 opened Jul 27, 2022 by wetneb
1
Add "description" field to type and property classes
#93 opened Jul 27, 2022 by wetneb
3
Make the API more REST-y
#84 opened May 19, 2022 by wetneb
5 tasks done
@wetneb
6
Specify behaviour on invalid user input
#83 opened May 17, 2022 by wetneb
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.