-
Notifications
You must be signed in to change notification settings - Fork 105
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
Deprecate contributor_aggregate_ytd
sort option for Schedule A endpoint (reminder July 20)
#4381
Comments
contributor_aggregate_ytd
sort option for Scedule A endpointcontributor_aggregate_ytd
sort option for Schedule A endpoint
contributor_aggregate_ytd
sort option for Schedule A endpointcontributor_aggregate_ytd
sort option for Schedule A endpoint
Hello API user, This email provides information about changes to the Federal Election Commission’s (FEC) API, openFEC. We are contacting you because an API key associated with your email address used the ‘contributor_aggregate_ytd’ sort option for the ‘/schedules/schedule_a/’ endpoint sometime during the past three months. On August 18, 2020, the FEC will remove this sort option. The remaining sort options for ‘/schedules/schedule_a/’ will be ‘contribution_receipt_date’ and ‘contribution_receipt_amount’. Should you have any questions, please contact APIinfo@fec.gov. |
contributor_aggregate_ytd
sort option for Schedule A endpointcontributor_aggregate_ytd
sort option for Schedule A endpoint
contributor_aggregate_ytd
sort option for Schedule A endpointcontributor_aggregate_ytd
sort option for Schedule A endpoint (reminder July 20)
It looks like almost no one is sorting by
contributor_aggregate_ytd
(I see exactly one call in 3 months). We could consider deprecating that in the future to make Schedule A index management easier going forward.PI 12 Innovation sprint
: Send reminder email around July 19: Look for any new users of the soon-to-be deprecated functionalitySprint 13.1
: Remove the sort option (removed 8/11/2020)The text was updated successfully, but these errors were encountered: