Replies: 1 comment 1 reply
-
Thanks so much for the hard work on this @jadudm The eventual cadence of our fetches would be every 2 weeks. Sorry if I was unclear. Because we don't have a fully automated system in place in the PAST we have fetched data for several years all at once, but we would like to move to a 2 week cadence. (That said, there may be a rare need where we need to refetch all data between two arbitrary dates I suppose if we are missing many random files--which we currently need to do due to an bug with the old FAC website that I wont get into-- or some other issue, but this would not be the workflow. The common workflow would be to fetch the last two weeks worth of data looking for the newest audits (pdf, crosswalk, and structured data). And sorry we may not need those EXACT endpoints. They might be most convenient and compatible with our workflow, but I would completely understand if there's a similar solution with just more API calls, we can definitely develop that on our side by doing, say 1000 calls for a period instead of 1 massive 'give-me-everything-you-got-between-these-dates'. If there are endpoints that meet our requirements but just take more API calls we definitely work with that. To be clear clear on the requirements are:
But maybe there is already a solution I just didn't see. Maybe you can just point me to a solution if I'm missing something? So looking through the API maybe here's the rough process:
Sorry was too lazy in considering how to get the information we need when I submitted the ISSUE. We don't need those exact endpoints, what you have does solve a lot of our workflow already I just looks like we might need:
And then we could probably batch download everything we need? Do I have this right? |
Beta Was this translation helpful? Give feedback.
-
This discussion is being kicked off here on behalf of @jpmorris, who asked about additional endpoints in issue #1103.
#1103
From the issue:
Thinking about each of these in turn:
/vw_structured_data
suggests a way to get all of the data for "the year." Is this... from${now}
until 12 months ago? For a given fiscal year? Audit year? Those are details, when really... what it sounds like is you would like a database dump. If you do, do you want it in CSV, SQLite, a raw Postgres dump, or something else? And, how often would you need it? (If you say daily or weekly, it feels like you're not taking advantage of the API.) Why, essentially, do you need this (as opposed to querying the API for what you need, when you need it?) It would be good to understand the use case.vw_pdf_audit
. Currently, you can get a link to the PDF package from an entry in thevw_general
view. (I think that's true. The key ispdf_urls
.) You could do a date range search on thevw_general
view, aggregate the PDF links, and then download them. It feels like the API does what you need already.I'm not yet clear what "the crosswalk" is. There are a number of different crosswalks we might generate, and they're going to be... tricky, given the transition from EIN/DUNS to UEI. Is your third request essentially asking the question "How do we link 2023/UEI data to historical data?" If so, then this is a hard question to answer, and we're working with agencies to figure it out, but we're not there yet.
Beta Was this translation helpful? Give feedback.
All reactions