All endpoints are documented here: https://c211.io/api/swagger-ui/#/crate/organizations

Header:

We develop and support HSDA endpoints on an "as-needed" basis for specific use-cases.

Return all resources from a source in bulk. Services and Locations will be efficiently nested under their parent Organizations, with all available data nested under those primary structures. Be sure to use the setting full = true for data replication.

To see the specifications please refer to the Open Referral site:

https://docs.openreferral.org/en/latest/hsds/api_reference.html#the-organizations-endpoint

As and extension, we have added fields to further clarify the data. For example, labeling phone numbers, organization schedules, contact emails, etc.

GitHub also has examples of the JSON payload you can expect:

https://github.com/openreferral/specification/blob/3.0/examples/organization_full.json

When viewing the JSON examples above, note that our payloads follow this spec rigorously, but also includes additional information designed to clarify intended use. For example, given a list of phone number related to a service, we will communicate in what order those numbers should be prioritized from the perspective of help seekers.

Return all details, or related data, for a specific service_at_location object. In the context of the Connect 211 resource directory, this is all possible information that would be displayed as "Details" for a "Search Record".

Our APIs return data that has been cleaned and augmented to some degree before being published. If you need raw data, please let us know ahead of time. This is not currently available, but is on our roadmap.