We're committed to keeping the AggKnowledge API stable so you can build on it with confidence.
Here's what that means in practice: any field that currently appears in an API response will continue to be there and populated. We won't remove fields or quietly stop returning values for them.
What we don't promise is a frozen response shape. We'll add new fields over time as we expand our data coverage and capabilities - so your integration should be written to accept and ignore unknown fields rather than treating them as errors. As long as you're only depending on fields that are documented in the API reference, you're on solid ground.
Last modified on
