Skip to main content

Manager API: replan: and catchup: dedupe_key prefixes are reserved

POST /strategies/{strategyId}/signals now refuses a dedupe_key that starts with replan: or catchup: (any case). Those prefixes are reserved for signals the platform generates itself.

What changed​

  • A dedupe_key beginning with replan: or catchup:, in any letter case, is refused with 400 invalid_request and the message names the field. Every other key up to 200 characters is accepted as before.
  • Documented on the dedupe_key request field and in Managing a Strategy.

What to do​

Action: if any key you publish starts with replan: or catchup:, rename it. Keys that never used those prefixes need no change.