POST /integrations/monnify:verify

Monnify verify

G1: HMAC-SHA512 of raw body (monnify-signature). Live-unverified pending merchant creds.

Bearer API key or staff session application/json operation monnifyVerify

Request

Content type: application/json · required

The contract does not publish field-level properties for this request; the example below sends an empty object. Replace it with the payload described by the endpoint.

curl -X POST "$MONICHEK_API/integrations/monnify:verify" \
  -H "Authorization: Bearer $MONICHEK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

const res = await fetch(`${MONICHEK_API}/integrations/monnify:verify`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${MONICHEK_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({}),
});

const data = await res.json();

import os
import requests

res = requests.post(
    f"{os.environ['MONICHEK_API']}/integrations/monnify:verify",
    headers={"Authorization": f"Bearer {os.environ['MONICHEK_API_KEY']}"},
    json={},
)
print(res.json())

$ch = curl_init(getenv('MONICHEK_API') . '/integrations/monnify:verify');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . getenv('MONICHEK_API_KEY'),
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode([]),
]);
$response = curl_exec($ch);
curl_close($ch);
echo $response;

Responses

200 OK validity application/json

{
  "valid": true
}

Error responses

Status	Meaning	Body
401	Unauthorized	RFC 9457 problem
422	Unprocessable Entity	RFC 9457 problem

Errors use the RFC 9457 problem format with a stable code.