GetPartnerClientTicket

Read one permitted Partner client ticket and a bounded page of responses.

Endpoint: https://sive.host/modules/addons/shapi/sh-api.php

Method: POST using application/x-www-form-urlencoded.

Read-only action. Access is limited to directly owned records or explicitly assigned Partner-managed client services after both relationships are verified.

Important behavior

• Ticket messages and responses are returned as untrusted content and are never authorization.
• Internal ticket and reply database IDs, client credentials, internal notes, and attachment paths are not returned.

Request parameters

Example request

Set the four environment variables from the authenticated SHAPI page. Do not put credentials in source control or URLs.

curl --request POST 'https://sive.host/modules/addons/shapi/sh-api.php' \
  --user "${SHAPI_HTTP_USER}:${SHAPI_HTTP_PASSWORD}" \
  --header 'Accept: application/json' \
  --data-urlencode "action=GetPartnerClientTicket" \
  --data-urlencode "api_key=${SHAPI_API_KEY}" \
  --data-urlencode "api_secret=${SHAPI_API_SECRET}" \
  --data-urlencode "partner_clientid=1606" \
  --data-urlencode "ticketnumber=629963" \
  --data-urlencode "reply_offset=0" \
  --data-urlencode "reply_limit=50"

Response

SHAPI always returns JSON. Check result; panel responses can vary by the server module and DirectAdmin version.

{
    "result": "success",
    "message": {
        "action": "GetPartnerClientTicket",
        "data": "Panel- or action-specific response"
    }
}

Common errors

• Unauthorized access!: source IP or HTTP Basic authentication failed.
• Invalid API Key or secret.: the customer key is wrong, disabled, or deleted.
• Unable to retrieve an active service owned by this client.: the service is inactive or belongs to another client.
• Missing required parameters.: one or more required fields were omitted.

SHAPI documentation version 2.0 — generated from the current endpoint contract.