Authentication and compatibility

Named credentials, explicit scopes, and versioned response contracts.

Vectorlane issues credentials to a named integration owner. Each key pair is tied to an environment, a scope set, and a regional ingress profile so validation and delivery behavior remain predictable.

Credential model

  • One key pair per environment and workload category
  • Separate webhook secret for callback verification
  • Idle credentials rotate on a scheduled policy

Versioning

  • URI versioning for breaking response changes
  • Field additions remain backward compatible within a major line
  • Deprecation notices are published before removal windows

Webhook signature example

Callbacks are signed and timestamped.

X-Vectorlane-Timestamp: 1728642000
X-Vectorlane-Signature: sha256=3cb3d4f6c1a4...

signing_payload = timestamp + "." + raw_body