Endpoints¶
As of v1.0, these are the endpoints that have been fully implemented in bavapi:
audiencesaudience-groupsbrand-metricsbrand-metric-groupsbrandsbrandscape-datacategoriescitiescollectionscompaniescountriessectorsstudiesyears
"Implemented" in this case means that the endpoint has a corresponding function, Client method, and filters class associated with them. More info in each endpoint's respective section linked above.
If an existing endpoint does not appear in the list above, you can still perform queries to it using the raw_query function/method (see below), but bavapi won't validate filter parameters.
Examples for each endpoint are available in each of their individual sections, both for the top-level, synchronous functions, and the asynchronous methods in bavapi.Client.
For a summary of all existing Fount endpoints, as well as their parameters and supported filters, please see the Resources section of the Fount API documentation.
Other endpoints¶
While there are some commonly used endpoints with more extensive validation support, there are a lot of additional endpoints available for querying.
With the raw_query functions and methods, you can perform requests to any endpoint in the Fount, even if it's not supported with dedicated code.
| Endpoint | Function | Client method |
Filters class |
|---|---|---|---|
{any} |
raw_query |
Client.raw_query |
FountFilters |
Queries from raw_query functions and methods return a list of JSON dictionaries, instead of a pandas DataFrame.
Usage¶
Since the result of these queries will be a list of JSON dictionaries, you can use the parse_response function in the bavapi.parsing.responses module to parse the JSON response into a DataFrame: