juspay/hyperswitch · error · ApiErrorResponse::InternalServerError
Nmi requires HeaderKey or BodyKey auth type
Error message
Nmi requires HeaderKey or BodyKey auth type
What it means
Error "Nmi requires HeaderKey or BodyKey auth type" thrown in juspay/hyperswitch.
Source
Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1177
api_key: api_key.clone(),
profile_token: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Mollie {
api_key: api_key.clone(),
profile_token: Some(key1.clone()),
}),
_ => Err(err("Mollie requires HeaderKey or BodyKey auth type")),
},
Connector::Nmi => match auth {
ConnectorAuthType::HeaderKey { api_key } => Ok(Self::Nmi {
api_key: api_key.clone(),
public_key: None,
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Nmi {
api_key: api_key.clone(),
public_key: Some(key1.clone()),
}),
_ => Err(err("Nmi requires HeaderKey or BodyKey auth type")),
},
Connector::Authipay => match auth {
ConnectorAuthType::SignatureKey {
api_key,
key1: _,
api_secret,
} => Ok(Self::Authipay {
api_key: api_key.clone(),
api_secret: api_secret.clone(),
}),
ConnectorAuthType::BodyKey { api_key, key1 } => Ok(Self::Authipay {
api_key: api_key.clone(),
api_secret: key1.clone(),
}),
_ => Err(err("Authipay requires SignatureKey or BodyKey auth type")),
},
Connector::Bankofamerica => match auth {
ConnectorAuthType::SignatureKey {View on GitHub (pinned to 3093f22cc4)
Solutions
- Configure the merchant connector account for Nmi with the HeaderKey or BodyKey connector_auth_type
- Recreate/update the connector account credentials to match the HeaderKey or BodyKey schema
When it happens
Trigger: Thrown at crates/router/src/core/unified_connector_service/connector_config.rs:1122 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/54f16e077b991a76.
Report an issue: GitHub.