@kardinal-ai/sdk. For changes to the API itself, see the API changelog.
Fix: vehicle profile options accepted
- The options of
vehicleProfile, such aswithTrafficorgrossWeight, are no longer refused as unknown fields bysubmit,update,parsePlanCreate, andkardinal routing plans validate. Each profile is checked against the options of its owntype, so a misspelled option is still reported. - If you named these options in
allowUnknownto work around the issue in 1.0.0, you can remove them.
First public release, targeting API 1.0.1
- Client for every endpoint of the Route Optimization API:
plans.submit,get,update,delete,list,iterAll,start,stop,getStatus, andsolutions.get,getObjectives,wait. - Types generated from the API specification, with the API’s field names and descriptions, and run-time validation of plans with
zodbefore sending. - Misspelled keys refused before sending (
UnknownFieldError), with the closest real field name;allowUnknownto send a field the SDK doesn’t know yet. solutions.wait, which follows a plan’s optimization and resolves with its solution once it’s over.- Typed errors for every API error, with
.errors,.details, and.retryable; any403thrown asKardinalLimitError. - Automatic retries of reads,
update,delete,start, andstop;submitis never retried. - Optional
kardinalcommand-line tool (installcommanderalongside the package), with local plan validation. - ES module, for Node.js 22 or later.

