fbpx

< / >

Query obligation

Query obligation

URL:

https://{{wolkvox_server}}/server/API/v2/collections/queryObligation.php

Description:

This API provides the functionality to search for obligations in the collections module. It allows you to search and retrieve detailed information about obligations associated with records in your operation.

¿How it works?

This API operates through a ‘raw‘ type body and a GET request, which requires the following fields for its proper functioning:

The request headers require:

  • Wolkvox-Token

– In the request body, it is required

  • operation
  • obligation
  • wolkvox-id

 

How to determine the CRM server?

  • Access the CRM homepage using the link: https://crm.wolkvox.com/
  •  Log in using your CRM credentials.
  • Once you have logged in and are on the homepage of your CRM platform, observe the address bar of your web browser. The URL in this bar indicates the server where your operation is hosted.
  • Replace {{crm_server}} in the original URL with the specific URL of your CRM server to ensure that the API points correctly to your CRM instance.

Important Notice: Access Route Update

Starting September 1, 2024, new URLs will be implemented to access the wolkvox CRM platform. The current URLs will coexist with the new ones until November 30, 2024, after which they will be disabled.

New URLs:

From “https://sv0001.crmvox.com” to “https://crm0001.wolkvox.com

From “https://sv0000.crmvox.com” to “https://crm0000.wolkvox.com

Please ensure you update your integrations and automations before November 30, 2024, to avoid service interruptions.

REQUEST

KEY
DESCRIPTION
EXAMPLE
Wolkvox-Token
It is the token configured by the client on the CRM page.
A8K3J7F2
operation
It is the name of the CRM operation.
“operation”:”testmodule”
obligation
It is the obligation identifier.
“obligation”: “6669999 API”
wolkvox_id
It is the identifier of the records in collections.
“wolkvox_id”: “61fa3”

REQUEST

				
					$curl = curl_init();

curl_setopt_array($curl, array(
  CURLOPT_URL => 'https://{{wolkvox_server}}/server/API/v2/collections/queryObligation.php',
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => '',
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 0,
  CURLOPT_FOLLOWLOCATION => true,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => 'POST',
  CURLOPT_POSTFIELDS =>'{
    "operation": "",
    "obligation": "",
    "wolkvox_id": ""
}',
  CURLOPT_HTTPHEADER => array(
    'Wolkvox-Token: {{token}}',
    'Content-Type: application/json'
  ),
));

$response = curl_exec($curl);

curl_close($curl);
echo $response;

				
			

RESPONSE

KEY
DESCRIPTION
EXAMPLE
id
Identification code of the obligation in the indicated record.
“id”: “obl1”
name
Obligation name.
“name”: “Invoice 12345 – Pending Payment”
total_balance
It is the total balance.
“total_balance”: “10000”
portfolio_type
It is the associated portfolio type.
“portfolio_type”: “VIP Client”
last_pay
Indicates the amount of the last associated payment.
“last_pay”: “2000”
last_pay_date
Indicates the date of the last associated payment.
“last_pay_date”: “06-06-2023”
expiring_date
Indicates the due date.
“expiring_date”: “07-07-2023”
days_delay
Indicates the number of days overdue.
“days_delay”: “90”
form
It is a dataset representing additional fields (in the obligations) that were created as complementary to the default ones.
“form”: [ { “name”: “Titulation”, “value”: “titulation value” }, { “name”: “Frequency”, “value”: “Frequented” } ]
				
					{
    "code": "200",
    "error": "null",
    "msg": "x records were are found",
    "data": [
        {
            "id": "",
            "name": "",
            "total_balance": "",
            "portfolio_type": "",
            "last_pay": "",
            "last_pay_date": "",
            "expiring_date": "",
            "days_delay": "",
            "form": [
                {
                    "name": "",
                    "value": ""
                }
            ]
        }
    ]
}
				
			
Posibles códigos de error

Usamos cookies, se continuar a navegar assumimos que concorda. Pode ler mais sobre a utilização de cookies nas nossas políticas de privacidade e tratamento de dados pessoais

We use cookies, if you continue browsing we will assume that you agree. You can read more about the use of cookies in our privacy policies and treatment of personal data