Get shopping intent
- Print
- PDF
Get shopping intent
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in VPC
Get the profile details of created shopping intent. You can check the progress of the profile you requested to create and the task model used when creating the profile. If the creation fails, you can see the error message.
Request
This section describes the request format. The method and URI are as follows:
Method | URI |
---|---|
GET | /profile/shopping-intents/{profile_id} |
Request headers
For information about the headers common to all NCLUE APIs, see NCLUE request headers.
Request path parameters
You can use the following path parameters with your request:
Field | Type | Required | Description |
---|---|---|---|
profile_id | String | Required | Profile ID
|
Request example
The request example is as follows:
Response
This section describes the response format.
Response body
The response body includes the following data:
Field | Type | Required | Description |
---|---|---|---|
profile_id | String | - | Profile ID |
profile_name | String | - | Profile name |
task_id | String | - | Task ID to apply for profiling |
task_name | String | - | Task name to apply for profiling |
status | String | - | Profile status
|
created_at | String | - | Profile creation request date and time (ISO 8601 format) |
completed_at | String | - | Profile creation completion date and time (ISO 8601 format) |
line_count | Integer | - | Number of lines of the feature applied to the task |
disk_usage | Integer | - | Capacity (byte) of the profile |
fail_message | String | - | Creation failure message
|
Response status codes
For response status codes common to NCLUE, see NCLUE response status codes.
Response example
The response example is as follows:
Was this article helpful?