Create shopping intent
- Print
- PDF
Create shopping intent
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
Create a profile of a shopping intent.
When a user requests the creation of shopping intent, the NCLUE system registers the request job and returns the profile ID. The creation process is as follows.
Creation process
| Order | Creation status | Description |
|---|---|---|
| Step 1 | Registered registered | Status where the creation job is registered in the system. It is the status before starting the job. You can cancel the job by deleting it at this point |
| Step 2 | Pending pending | Status where the creation job is queued in the system |
| Step 3 | Creating in_progress | Status where the job is being executed on the server. Creation time varies depending on the service's available resources |
| Step 4 | Creation complete
| Once creation is complete, it will be available for use when successful with the "Available" status. If an error occurs during the operation, it will be in the "Failed" status, and the error message can be used to troubleshoot the problem |
The creation of shopping intent varies in time depending on the service's available resources. To check the progress of the creation, call the Get shopping intent API and check the "status" field in the response body.
Request
This section describes the request format. The method and URI are as follows:
| Method | URI |
|---|---|
| POST | /api/v1/profile/shopping-intents |
Request headers
For information about the headers common to all NCLUE APIs, see Common NCLUE headers.
Request body
You can include the following data in the body of your request:
| Field | Type | Required | Description |
|---|---|---|---|
name | String | Required | Profile name (40-character limit) |
task_id | String | Required | ID of task to check the profile results |
Request example
The request example is as follows:
curl --location --request POST 'https://nclue.apigw.ntruss.com/api/v1/profile/shopping-intents' \
--header 'X-NCP-APIGW-TIMESTAMP: {Timestamp}' \
--header 'X-NCP-IAM-ACCESS-KEY: {Access Key}' \
--header 'X-NCP-APIGW-SIGNATURE-V2: {API Gateway Signature}'
--data '{
"name":"Pet food user profiling",
"task_id":"b5e742f1-0558-465a-8485-3b7808b0e125"
}'
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 of the shopping intent entered by the user |
task_id | String | - | ID of task to check the profile results |
task_name | String | - | Name of task to check the profile results |
created_at | String | - | Shopping intent creation request date (ISO 8601 format) |
Response example
The response example is as follows:
Succeeded
The following is a sample response upon a successful call.
{
"profile_id":"bce6d560-99ce-4a26-809d-03f750371d52",
"profile_name":"Pet food user profiling",
"task_id":"b5e742f1-0558-465a-8485-3b7808b0e125",
"task_name":"Prediction model for pet food purchase interest",
"created_at":"2024-11-04T11:02:34"
}
Failure
For examples of responses in the event of a failed call, see Response status codes.
Was this article helpful?