Skip to main content
GET
/
merchant
/
integration
/
quickbooks
/
disconnection
Disconnection Quickbooks
curl --request GET \
  --url https://api.unibee.dev/merchant/integration/quickbooks/disconnection \
  --header 'Authorization: Bearer <token>'
{
  "code": 123,
  "data": {},
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

​
Endpoint Overview

GET https://api.unibee.dev/merchant/integration/quickbooks/disconnection Disconnection Quickbooks

​
Authorization

All UniBee Merchant API requests require authentication via API key.
HeaderRequiredDescription
AuthorizationYesBearer <your_api_key>
Content-TypeYesapplication/json (for request body)

​
Parameters

Path, query, and request body parameters are defined in the schema below. Use the interactive Try it panel to see the full request structure. Path, query, and request body parameters are defined in the schema below. Use the interactive Try it panel to see the full request structure.

​
Request examples

​
cURL

curl -X GET "https://api.unibee.dev/merchant/integration/quickbooks/disconnection" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

​
Sandbox

curl -X GET "https://api-sandbox.unibee.top/merchant/integration/quickbooks/disconnection" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json"

​
Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success. The response schema for this endpoint is shown below.

​
Error handling

HTTP statusMeaning
400Bad request — invalid or missing parameters. Check message in the body.
401Unauthorized — missing or invalid API key.
404Not found — invalid path or resource.
500Server error — retry with backoff.
When code in the response body is non-zero, check message for details. Use requestId when contacting support.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Response

200 - application/json
​
code
integer<int>
​
data
object
​
merchantId
integer<int64>
​
message
string<string>
​
redirect
string<string>
​
requestId
string<string>