juspay/hyperswitch · error · error_stack::Report<ApiErrorResponse>
Celero requires HeaderKey auth type
Error message
Celero requires HeaderKey auth type
What it means
Error "Celero requires HeaderKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:947
let calida_meta = metadata
.map(|m| {
serde_json::from_value::<CalidaMetadata>(m.clone())
.map_err(|_| err("Invalid Calida metadata format"))
})
.transpose()?;
Ok(Self::Calida {
api_key: api_key.clone(),
shop_name: calida_meta.as_ref().map(|m| m.shop_name.clone()),
})
}
_ => Err(err("Calida requires HeaderKey auth type")),
},
Connector::Celero => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Celero {
api_key: api_key.clone(),
}),
_ => Err(err("Celero requires HeaderKey auth type")),
},
Connector::Helcim => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Helcim {
api_key: api_key.clone(),
}),
_ => Err(err("Helcim requires HeaderKey auth type")),
},
Connector::Multisafepay => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Multisafepay {
api_key: api_key.clone(),
}),
_ => Err(err("Multisafepay requires HeaderKey auth type")),
},
Connector::Nexixpay => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Nexixpay {
api_key: api_key.clone(),
}),
_ => Err(err("Nexixpay requires HeaderKey auth type")),View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Celero with the HeaderKey connector_auth_type
- Recreate/update the connector account credentials to match the HeaderKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:892 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of juspay/hyperswitch@3093f22cc4 (2026-08-19).
Data as JSON: /api/errors/377edb78f3b833cf.
Report an issue: GitHub.