Developers
REST API
GuidesErrorsLogin
Get API Keys
API Navigation
  • Overview
  • Quick start
  • Authentication
  • Collect a payment
  • Payment status
  • Refunds
  • Testing
  • Production
  • Security
API reference
  • Create API keys POST
  • List API keys GET
  • Get API key GET
  • Delete API key DEL
  • Collect with MTN POST
  • MTN payment status GET
  • Collect with Airtel POST
    Create and pay
  • Create order POST
  • Order fee POST
  • Pay order with card POST
  • Pay order with bank POST
    • Status and verify
  • Order status POST
  • Verify order POST
    • Cards and tokens
  • Save card POST
  • Tokenize charge GET
    • Refunds
  • Refund order POST
    • Lists and stats
  • List orders GET
  • Get order GET
  • List banks GET
  • Order stats GET
  • List transactions GET
  • Get transaction GET
  • Transaction statuses GET
Errors and limits
  1. Docs
  3. API reference
  5. Delete API key

Delete API key

Delete an API key config owned by the signed-in merchant.

OpenAPI SpecRun in Postman
DEL/developer/delete/:idAPI
Authentication:Bearer token•Authorization: Bearer <token>(Bearer token for server-to-server API calls)
Security requirement: 403 CSRF Protection
Auth guide →

Direct server-to-server calls authenticated via Bearer tokens do not require CSRF headers. If you instead invoke mutation endpoints from a web browser using cookie-based sessions, you must include the following header:

X-Requested-With: XMLHttpRequest

Path params

FieldTypeRequiredDescription
idstringRequiredAPI key config ID (id) from create or list.
import axios from "axios";

const url = "https://payment-service-mh2d.onrender.com/api/developer/delete/:id";

const headers = {
    Authorization: `Bearer ${process.env.ZIBA_TOKEN}`,
};

try {
  const response = await axios.delete(url, {
    headers,
    timeout: 15000,
  });
  console.log("Success:", response.status, response.data);
} catch (error) {
  console.error("Request failed:", error.response?.data || error.message);
}
Auth guide

Response fields

FieldTypePresenceDescription
idstringAlways returnedID of the deleted gateway configuration.
apiKeystringAlways returnedAPI key that was revoked.
namestringAlways returnedLabel of the revoked key.
messagestringOptionalConfirmation message.

Status codes

HTTP StatusMeaning
200API key config deleted and revoked.
401No merchant session. Missing or expired Bearer token.
404API key config not found or belongs to another merchant.

Notes

  • Immediate Effect: Revocation takes effect across nodes. Any server calling POST /payment/gateway-momo-pay with this key will receive HTTP 401 Unauthorized.

Related

List API keysCreate API keys
Was this page helpful?

Let us know how we can make our API documentation better.

PreviousGet API key
NextCollect with MTN