Config API

The Config API provides basic catalog management operations. Similarly to the API Lookup, the Config API responses are cacheable. HERE recommends requesting catalog configuration only once per instance / Spark or Flink worker node and to keep reusing cached catalog configuration objects as needed.

The API Lookup and Config API services do not require any special performance considerations due to the nature of their low request rates and small response sizes.


The /config/v1/status/{status_token} endpoint is used to determine if the request succeeded, failed, or is still being processed (pending). While in the pending state, the request should not be retried.

For consecutive delete and create requests, the recommendation is to wait 60 seconds due to the nature of the system.

results matching ""

    No results matching ""