Threads 데이터 API

# Threads Data API

Read profiles, posts, replies, reposts, comments and search results through 12 authenticated Threads endpoints.

## Authentication

Send your API Hop API key in the Authorization header. Access depends on enabled gateways and API key permissions; documentation does not confirm production availability.

```http
Authorization: Bearer YOUR_API_KEY
```

## Requests

Use GET query parameters without a request body. Unknown, duplicate or invalid fields are rejected. Keep IDs as strings, including values beyond the JavaScript safe integer range. Requests time out after 60 seconds and are not automatically retried.

```bash
curl --get "https://api.apihop.ai/v1/threads/web/posts/detail" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "post_id=DPVUglOjOUu"
```

## Responses

The native JSON code/data envelope and numeric precision are preserved. Success requires code=200 and non-null data. An HTTP 200 business error is a failure. Response shapes vary by endpoint; this example is illustrative, not a live response.

```json
{"code":200,"data":{"post":{"code":"DPVUglOjOUu"},"replies":[]}}
```

## Billing

The default price is $0.002 (2000 credits) per successful request, including successful empty arrays or objects, not per item. Account-specific prices take precedence. Failed upstream requests release the reservation. Settlement errors return an error without repeating the upstream request.

## Pagination limits

User posts, reposts, replies, post comments, top search and recent search do not support pagination. Their end_cursor field is reserved and has no effect; do not use next_cursor or has_more to fetch further pages. User lists return only the available batch (about 25 items), not full history. No endpoint automatically retrieves more data.

## Errors

HTTP 400: invalid parameters; 401: authentication failure; 402: insufficient credit; 403: access denied; 405: unsupported method; 408: cancellation; 429: rate limit; 5xx: service or upstream failure, including 504 timeout. Keep X-Request-Id for diagnosis.

## Reference

[Full reference](https://apihop.ai/en/docs/api-reference/threads/reference)

## Sources

Checked against official OpenAPI V5.3.2 and endpoint prices on 2026-10-31. The price-only fetch_post_id_from_url operation is excluded because it is absent from OpenAPI.

[TikHub](https://docs.tikhub.io/4592766m0) · [OpenAPI](https://api.tikhub.io/openapi.json) · [Prices](https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info)

인증이 필요한 12개 Threads 엔드포인트로 프로필, 게시물, 답글, 재게시물, 댓글 및 검색 결과를 조회합니다.

인증

Authorization 헤더에 API Hop API 키를 보내세요. 접근은 활성 게이트웨이와 키 권한에 따라 달라지며, 문서는 운영 환경 제공 여부를 보장하지 않습니다.

http

Authorization: Bearer YOUR_API_KEY

요청

본문 없이 GET 쿼리 매개변수를 사용합니다. 알 수 없거나 중복되거나 잘못된 필드는 거부됩니다. JavaScript 안전 정수 범위를 넘는 값도 ID를 문자열로 유지하세요. 제한 시간은 60초이며 자동 재시도하지 않습니다.

bash

curl --get "https://api.apihop.ai/v1/threads/web/posts/detail" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "post_id=DPVUglOjOUu"

응답

원본 JSON code/data 구조와 숫자 정밀도를 보존합니다. 성공하려면 code=200이고 data가 null이 아니어야 합니다. HTTP 200 안의 업무 오류도 실패입니다. 구조는 작업마다 다르며 아래는 설명용 예시로, 실제 응답이 아닙니다.

json

{"code":200,"data":{"post":{"code":"DPVUglOjOUu"},"replies":[]}}

인증

요청

응답

과금

오류

참조

출처