Verify Document Support

Verifies document support for a Recommand recipient.

GET

Query

Arguments

stringrequired

The document type to verify. You can use a full document type ID, or the simplified versions (e.g. "invoice", "creditNote", "selfBillingInvoice", "selfBillingCreditNote", ...).

stringrequired

The Peppol address of the recipient to verify.

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Try this request

Request

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/recommand/0.0.3/actions/verify-document-support" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --get \
  --data-urlencode 'connectionId=$CONNECTION_ID' \
  --data-urlencode 'documenttype=' \
  --data-urlencode 'peppoladdress='

{
  "success": true,
  "data": [
    {
      "certificateExpiry": "string",
      "isValid": true,
      "serviceEndpoint": "string",
      "serviceProvider": "string",
      "smpUrl": "https://example.com",
      "success": true,
      "technicalContact": "string"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.