PSA API endpoint
Use Crawlora's PSA TicketFacts Profile API to extract supported public PSA data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/psa/ticketfacts/subjectOne event's full public ticket reference page: PSA's own historical writeup of the event and the ticket(s) involved. Unlike psa-autographfacts-subject, this carries no price guide. subject_id is the numeric id from a psa-ticketfacts-subjects result. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| subject_id | string | Yes | Numeric subject id, from a psa-ticketfacts-subjects result | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/psa/ticketfacts/subject" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- `ticket_profile` is PSA's own free-text historical writeup of the event. - A `subject_id` PSA cannot resolve returns `404`. Example response: ```json { "code": 200, "msg": "OK", "data": { "subject_id": "1147", "name": "Super Bowl I", "ticket_profile": "The nearly decade-long battle that raged between the National Football League and the American Football League ... culminated in the establishment of a single title game between the two league champions, known as the AFL-NFL World Championship.", "source_url": "https://www.psacard.com/ticketfacts/subject/profile/1147" } } ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"subject_id": "1147",
"name": "Super Bowl I",
"ticket_profile": "The nearly decade-long battle that raged between the National Football League and the American Football League ... culminated in the establishment of a single title game between the two league champions, known as the AFL-NFL World Championship.",
"source_url": "https://www.psacard.com/ticketfacts/subject/profile/1147"
}
}Request schema
No body schema
Response schema
#/definitions/psa.ticketFactsSubjectResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | psa.TicketFactsSubjectResult | No | ||||
| data.name | string | No | Name is the event's display name, e.g. "Super Bowl I". | |||
| data.source_url | string | No | ||||
| data.subject_id | string | No | ||||
| data.ticket_profile | string | No | TicketProfile is PSA's own free-text historical writeup for this event. | |||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/psa/ticketfacts/subject" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms