Sephora Reviews API
API 한 번의 호출로 Sephora Reviews 데이터를 받아 가세요. Returns written customer reviews for a Sephora product, 10 per page by default, each with the full review text, star rating, title, reviewer nickname, submission date, and helpful-vote count. The review total is exact. Pass the returned cursor back until has_more is false. Optional sort_by: most_helpful, highest_rating, lowest_rating, oldest, newest. Optional rating keeps only that star value.
2026년 10월 업데이트SocialCrawl 팀이 직접 관리해요
Sephora 상품의 고객 리뷰를 페이지당 10건씩 본문, 별점, 제목, 작성자 닉네임, 작성일과 함께 반환합니다.
상품 아이디가 있고 리뷰 본문이 필요할 때 사용합니다. 별점 평균은 GET /v1/sephora/product에 있습니다.
68개 플랫폼을 병렬로 검색합니다
Reviews API로 무엇을 할 수 있을까요
Reviews 엔드포인트가 통합 스키마와 계산 필드를 담은 Sephora 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/sephora/reviews?product_id=P427414&label=issue"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/sephora/reviews",
params={
'product_id': 'P427414',
'label': 'issue',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/sephora/reviews?product_id=P427414&label=issue",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();함께 보내면 좋은 파라미터
label=issue리뷰마다 어떤 제품 문제를 지적하는지 표시합니다. 추가 크레딧은 들지 않으며 감정 판정도 무료입니다.
파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| product_id | 아니오 | Sephora product id, the P-number at the end of a product URL: sephora.com/product/the-ordinary-deciem-natural-moisturizing-factors-ha-P427414 is product id P427414. Product ids also come back on every row of GET /v1/sephora/search and GET /v1/sephora/category. |
| url | 아니오 | Full Sephora product URL, for example https://www.sephora.com/product/the-ordinary-deciem-natural-moisturizing-factors-ha-P427414. The product id is extracted from the path. |
| page | 아니오 | Page number, starting at 1. Prefer the universal cursor parameter. |
| limit | 아니오 | Reviews per page, 1 to 100. Default 10. |
| sort_by | 아니오 | Review ordering: most_helpful, highest_rating, lowest_rating, oldest, newest. (most_helpful | highest_rating | lowest_rating | oldest | newest) |
| rating | 아니오 | Keep only reviews with this star value, 1 to 5. |
| label | 아니오 | Optional CSV of SocialCrawl labels to add to every review. Without this param every page already carries sentiment and issue, free; label= adds the labels you name to them (the defaults keep running). sentiment and issue are free when asked for too; reports, incentivized and injection add 1 credit per started 25 newly judged reviews. judgments=off (or label=none) turns the default labels off. They read the review's title and text, never its stars. sentiment: how the reviewer feels, on five levels (level 0 to 4, score_0_1, confidence), plus rating_mismatch, true when the words clearly contradict the star rating (a glowing text under 1 star, a furious one under 5), null when the review has no rating. issue: the main problem the review reports (label: product_defect, sizing_or_fit, shipping_or_delivery, customer_service, price_or_value, missing_feature, other, or none, with confidence; label is null when unsure). reports (needs reports=): does this review say that the thing you describe happened (p, 0 to 1). incentivized: does the reviewer say they got the product free, discounted or rewarded for the review (p), and did the text carry a disclosure such as 'in exchange for my honest review', Vine or 체험단 (disclosed). injection flags text that addresses an AI system and tries to direct it (flagged, p); it never drops or rewrites a row. These are signals to read, never a verdict on a review or a reviewer. A review that could not be judged carries labels: null. Reviews already labelled for anyone are free, and so is a cached page. data.labels reports what was judged and billed. |
| reports | 아니오 | Required by label=reports, ignored otherwise. What to look for, in plain words, up to 300 characters, for example reports=the battery drains quickly or reports=배송이 늦음. Every review gains labels.reports.p, the probability that it says so, in any wording or language. Without it label=reports is skipped with the warning label_reports_needs_reports and is not billed. |
| judgments | 아니오 | Optional, on (the default) or off. By default every row gains free SocialCrawl judgments (computed.labels, and computed.relevance on search endpoints), reported in data.labels (mode default) and data.relevance (origin default), each with a status (complete, partial or skipped) and pending: the rows still being judged when the page was sent, which carry null now and are filled on your next call or cached read. Default judgments never add credits, never change an existing field, and never drop or reorder a row. off returns the page exactly as before, with none of those keys. label=none does the same. (on | off) |
| dry_run | 아니오 | Optional. When 1, return a cost preview for this labelled or relevance-filtered request without fetching the page or judging any row. data.estimate reports rows_expected, rows_cached, label_credits_min, label_credits_max and base_credits. 0 credits charged. (1) |
| label_evidence | 아니오 | Optional, only with label=. When 1, every labelled row also carries computed.labels_evidence.<preset> = { quote, sentence_index }: the sentence in the row that most clearly shows the label, copied verbatim. Absent or null when no single sentence shows it. (1) |
| fit | 아니오 | Optional. When goal, keep the rows and fields needed for the goal you pass in goal= (plus any that are uncertain, and the first and last), and replace the rest with a stub. data.held_back lists the held ids and a recall id that re-reads the full page from cache at no extra charge. Without this param the page is unchanged. (goal) |
| goal | 아니오 | Required by fit=goal. What you are trying to do, in your own words, up to 300 characters. |
| fit_tokens | 아니오 | Optional, only with fit=goal. Soft cap on how much of the page to keep, in tokens. Uncertain blocks and the first and last block are kept even if they exceed it. |
| since | 아니오 | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| until | 아니오 | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
Sephora Reviews API는 무엇을 돌려주나요
모든 응답은 하나의 통합 스키마를 따라요. 크레딧을 쓰기 전에 어떤 필드가 돌아오는지, 실제 응답 본문 그대로 확인해 보세요.
응답 예시 보기
{
"success": true,
"platform": "sephora",
"endpoint": "/v1/sephora/reviews",
"data": {
"items": [
{
"review": {
"id": "403166879",
"entity_id": "P427414",
"url": null,
"title": "Sample comment text (redacted).",
"text": "Sample comment text (redacted).",
"rating": {
"value": 5,
"max": 5
},
"author": {
"name": "user_32605d",
"avatar_url": null,
"url": null,
"location": null,
"reviews_count": null
},
"helpful_votes": 0,
"verified": true,
"source": null,
"language": null,
"original_language": null,
"translated": null,
"images": null,
"responses": null,
"published_at": "2026-09-15T01:34:42.000Z"
}
},
{
"review": {
"id": "403091985",
"entity_id": "P427414",
"url": null,
"title": "Sample comment text (redacted).",
"text": "Sample comment text (redacted). Sample comment text (redacted). Sample comment text (redacted). Sample comment text (redacted).",
"rating": {
"value": 2,
"max": 5
},
"author": {
"name": "user_bf9db4",
"avatar_url": null,
"url": null,
"location": null,
"reviews_count": null
},
"helpful_votes": 0,
"verified": null,
"source": null,
"language": null,
"original_language": null,
"translated": null,
"images": null,
"responses": null,
"published_at": "2026-09-14T04:37:03.000Z"
}
}
],
"next_cursor": "2",
"total": 2847,
"dropped": 0
},
"credits_used": 5,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsImUiOiJzZXBob3JhL3Jldmlld3MiLCJwIjoicGFnZSJ9",
"has_more": true,
"page_size": 10
},
"credits_remaining": 9999,
"redacted": true
}통합 응답 구조를 보여 주는 실제 샘플이에요. 필드 값은 조회한 대상에 따라 달라져요.
Sephora Reviews API는 어떻게 동작하나요
API 키와 함께 GET 요청을 보내면, 통합 스키마와 계산 필드를 담은 깔끔한 JSON이 돌아와요.
메서드
GET
응답 형식
JSON
소셜 미디어 데이터를 몇 초 만에 수집하는 방법
개발자를 위한 가장 빠른 소셜 미디어 스크래핑 API. 월간 활성 사용자 100억 명 이상을 포괄하는 68개 플랫폼에서 프로필, 게시물, 댓글, 분석 데이터를 수집하세요.
모든 플랫폼을 하나의 스키마로
동일한 응답 구조로 68개 플랫폼을 조회하세요. 연동은 한 번이면 충분합니다.
단순 수집을 넘어 계산된 필드 제공
엔드포인트가 해당 지표를 지원하고 계산에 필요한 원본 값이 있을 때, 정규화된 레코드에 engagement_rate, estimated_reach, content_category, language를 함께 담아 바로 활용할 수 있습니다.
코드 한 줄 쓰기 전에, 데이터부터
Visual Data Explorer에 URL만 붙여넣으면 결과 카드와 정형화된 테이블, CSV 내보내기를 바로 사용할 수 있습니다.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Sephora Reviews 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 Sephora 데이터를 받아 가세요.
