How do I point the terra-api npm client at the new endpoint?
You can route to the new direct endpoint today, without waiting for a package release, by passing a custom baseUrl to the SDK client constructor (set it to the…
You can route to the new direct endpoint today, without waiting for a package release, by passing a custom baseUrl to the SDK client constructor (set it to the new access endpoint).
The npm client has not been updated recently, so its default base URL will not flip automatically, which makes the baseUrl override the practical path.
The old endpoint is not currently deprecated.
PreviousWhy does the duplicate-workout-name error differ by provider?
NextHistorical data and backfill
Last updated
Was this helpful?