mTLS Errors

Request Errors

The request failed client-certificate validation. These errors occur only for teams provisioned for mTLS. Unlike other request errors, these are returned before the request reaches Method’s core API. The response body is wrapped in { "error": { ... } } and has no top-level success or message field.

`UNAUTHORIZED`

No client certificate was presented, or the presented certificate failed verification. Returned with HTTP status 401.

{
  "error": {
    "type": "INVALID_REQUEST",
    "code": 401,
    "sub_type": "UNAUTHORIZED",
    "message": "A valid client certificate is required to access this resource. Contact your account administrator about mTLS provisioning."
  }
}

`FORBIDDEN`

The certificate is valid but its Subject DN is not authorized for the resolved team. Returned with HTTP status 403. Confirm the Subject DN registered with Method matches the one on your certificate.

{
  "error": {
    "type": "INVALID_REQUEST",
    "code": 403,
    "sub_type": "FORBIDDEN",
    "message": "The presented client certificate is not authorized for this team. Contact your account administrator."
  }
}

Resource Errors Entity Errors

⌘I

API Reference

Entities

Accounts

Wallet

Payments

Files

Opal

Elements

Events

Supporting Endpoints

Request Errors

`UNAUTHORIZED`

`FORBIDDEN`

​Request Errors

​UNAUTHORIZED

​FORBIDDEN

Request Errors

`UNAUTHORIZED`

`FORBIDDEN`