/wikidata/properties

POST /api/wikidata/properties

Price: 5 credits

Get a Wikidata property (P-id) with its data type, labels, descriptions, aliases and statements

How to use it

Get a Wikidata property by its P-id (e.g. 'P69'), or entity URL. A property is a predicate used in item statements (e.g. 'educated at', 'instance of'). Returns the property's value data type (wikibase-item, time, quantity, external-id, etc.), its multilingual labels, descriptions and aliases, and its own statements. Use it to interpret what a property id means inside an item's statements.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Property identifier — a Wikidata P-id or an entity URL (examples: "P69", "https://www.wikidata.org/wiki/Property:P31", "http://www.wikidata.org/entity/P106"; minLength: 1)

Response

• @type string (default: "WikidataProperty")
• id string required
• data_type string nullable
• labels object (default: {})
  • * string
• descriptions object (default: {})
  • * string
• aliases object (default: {})
  • * array
• statements array (default: [])
  • @type string (default: "WikidataStatement")
  • id string nullable
  • property_id string required
  • data_type string nullable
  • rank string nullable
  • value object nullable
    • @type string (default: "WikidataStatementValue")
    • type string nullable
    • content any
  • qualifiers array (default: [])
    • @type string (default: "WikidataQualifier")
    • property_id string required
    • data_type string nullable
    • value object nullable (see schema WikidataStatementValue)
  • references array (default: [])
    • @type string (default: "WikidataReference")
    • parts array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Property not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.