Getting Started
API Response Structure
Success Response
Sample of Sync Response
Code
Field description
| Field | Description |
|---|---|
| status | HTTP/HTTPS status code |
| message | Text message |
| job_id | Unique transaction_id, It will help to map Async response |
| source | It defines from where APIs request is coming, It can be either one from API, Widget, Dashabord, SDK or Portal. |
| entity | It defines which product the APIs request is coming from, It can be either one from Data, Insight, Verification, or Payments. |
| error | In case of success, error will be null |
Sample of Async Response
Code
Field description
| Field | Description |
|---|---|
| status | HTTP/HTTPS status code |
| message | Text message |
| data | Response data |
| source | It defines from where APIs request is coming, It can be either one from API, Widget, Dashabord, SDK or Portal. |
| entity | It defines which product the APIs request is coming from, It can be either one from Data, Insight, Verification, or Payments. |
| error | In case of success, error will be null |
Error Response
Sample of error response
Code
Field description
| Field | Description |
|---|---|
| status | HTTP/HTTPS status code |
| code | Brick customized status code |
| message | Text message |
| action | Further action to prevent this error |
| source | It defines from where APIs request is coming, It can be either one from API, Widget, Dashabord, SDK or Portal. |
| entity | It defines which product the APIs request is coming from, It can be either one from Data, Insight, Verification, or Payments. |
| error | In case of success, error will be null |
You can refer all possible error code in the error handling section.
Last modified on
