/dbpedia/resources/properties

POST /api/dbpedia/resources/properties

Price: 5 credits

Get a DBpedia resource's RDF properties as a flat list, optionally filtered by predicate

How to use it

Get the RDF properties (facts) of a DBpedia resource as a flat predicate-to-values list, without the label, types and image envelope of the full resource. Each entry carries the predicate URI and all of its values (value, value type, language and datatype). Pass a predicate URI to fetch only the values of that property (e.g. all 'birthPlace' facts). Use it to read specific facts about a resource.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• resource string required — Resource identifier — a DBpedia resource name, resource URL or Wikipedia article URL (examples: "Berlin", "http://dbpedia.org/resource/Berlin", "https://en.wikipedia.org/wiki/Berlin"; minLength: 1)
• predicate string nullable — Restrict the result to a single predicate URI (examples: "http://dbpedia.org/ontology/birthPlace", "http://purl.org/dc/terms/subject")

Response

• @type string (default: "DbpediaProperty")
• predicate string required
• values array (default: [])
  • @type string (default: "DbpediaValue")
  • value any
  • type string nullable
  • lang string nullable
  • datatype string nullable

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 — Resource 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.