...
To search for a list of inquiries belonging to the specific broker, consumers should send a HTTP POST GET request to endpoint /api/ipn/get/{:token}. The token parameter represents the security token acquired during the Authentication process on the API (see V1 Authentication)inquiries. As essential components of the JSON payload within the body of the request, consumers are required to include bToken (functioning as the broker identifier).
Action name | search inquiries |
---|---|
HTTP path | /api/ipn/get/{:token}
inquiries |
HTTP method | POSTGET |
Attributes of the HTTP request
HTTP Request Header |
---|
Authorization | string | required |
---|
An unique identifier of the broker.
A security token provided from Authentication endpoint. | |||
X-Broker-Token | string | optional1 | An unique identifier of the broker. |
---|---|---|---|
X-Account-Token | string | optional1 | An unique identifier |
of the account. | |||||||||
HTTP GET parameters | |||||||||
---|---|---|---|---|---|---|---|---|---|
inquiryId | int | optional | An unique identifier of the inquiry. | ||||||
lastDays | int | optional | If defined, only inquiries that were created or updated that last number of days, will be included in the result. Otherwise, inquiries created or updated in last three months will be included. | ||||||
Explanations:
1 at least one of bToken and aToken is required in the payload |
Attributes of the HTTP response
...
HTTP Request with simple payload | |||||
| |||||
HTTP Request with inquiry identifier | |||||
| |||||
HTTP Request with last days specified | |||||
| |||||
Successful HTTP Response | |||||
| |||||
Failed HTTP Response | |||||
|