POST /api/qiita/organizations
Price: 10 credits
Get Qiita Organization
Get a Qiita organization by alias or page URL. Returns the company description, logo, office address, public email, social links, article, like, follower and member counts, the tags it publishes under with the members writing under each, its most active contributors, and its most popular and newest articles.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)organization string required — Organization alias or organization page URL (examples: "kddiagile", "https://qiita.com/organizations/kddiagile")@type string (default: "QiitaOrganization")alias string requiredname string nullableurl string nullabledescription string nullabledescription_html string nullableimage string nullablecover string nullableaddress string nullablepublic_email string nullablewebsite_url string nullableconnpass_url string nullablefacebook_url string nullablegithub_url string nullabletwitter_url string nullablehatena_blog_url string nullableanalytics_id string nullablearticle_count integer nullablelike_count integer nullablefollower_count integer nullablemember_count integer nullablefrequently_used_tags array (default: [])@type string (default: "QiitaOrganizationTagStat")name string requiredalias string requiredurl string nullableimage string nullablearticle_count integer nullablelike_count integer nullableusers array (default: [])@type string (default: "QiitaUserRef")alias string requiredname string nullableimage string nullableurl string nullabletop_contributors array (default: [])@type string (default: "QiitaUserRef")alias string requiredname string nullableimage string nullableurl string nullablepopular_articles array (default: [])@type string (default: "QiitaArticleBrief")id string requiredarticle_title string nullableurl string nullablesnippet string nullablecreated_at integer nullablelike_count integer nullableauthor object nullable@type string (default: "QiitaUserRef")alias string requiredname string nullableimage string nullableurl string nullableorganization object nullable@type string (default: "QiitaOrganizationRef")alias string requiredname string nullableimage string nullableurl string nullablecampaign object nullable@type string (default: "QiitaCampaignRef")id string nullablecampaign_title string nullableurl string nullabletags array (default: [])@type string (default: "QiitaTagRef")name string requiredalias string requiredurl string nullablenew_articles array (default: [])@type string (default: "QiitaArticleBrief")id string requiredarticle_title string nullableurl string nullablesnippet string nullablecreated_at integer nullablelike_count integer nullableauthor object nullable@type string (default: "QiitaUserRef")alias string requiredname string nullableimage string nullableurl string nullableorganization object nullable@type string (default: "QiitaOrganizationRef")alias string requiredname string nullableimage string nullableurl string nullablecampaign object nullable@type string (default: "QiitaCampaignRef")id string nullablecampaign_title string nullableurl string nullabletags array (default: [])@type string (default: "QiitaTagRef")name string requiredalias string requiredurl string nullable422 — 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 — Organization not found. Verify the alias. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.