/dice/companies

POST /api/dice/companies

Price: 1 credit

Get full details of a Dice company profile by its GUID or company-profile URL: name, profile URL, description, website, logo, banner, account type, founding year, employee count, office policy, industries, technologies, tech stack, office locations, social media links, benefits, awards, media, and last update.

How to use it

Fetch a single Dice company profile by its GUID (e.g. 3a49da6b-f646-4a86-a7fb-6800d711de1c) or a full company-profile URL. The company GUID is exposed on every Dice job get-by-id result as company_url. Returns one item with id, legacy_company_id, name, profile_url, description, overview_header, website, image, banner, account_type, founded, employee_count, office_policy, categories (industries), technologies, tech_stacks, locations, social_media, benefits, awards, images, videos and updated_at.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company profile GUID or a full Dice company-profile URL (examples: "3a49da6b-f646-4a86-a7fb-6800d711de1c", "https://www.dice.com/company-profile/3a49da6b-f646-4a86-a7fb-6800d711de1c"; minLength: 1)

Response

• @type string (default: "DiceCompany")
• id string required
• legacy_company_id string nullable
• name string nullable
• profile_url string nullable
• description string nullable
• overview_header string nullable
• website string nullable
• image string nullable
• banner string nullable
• account_type string nullable
• founded integer nullable
• employee_count string nullable
• office_policy string nullable
• categories array (default: [])
• technologies array (default: [])
• tech_stacks array (default: [])
  • @type string (default: "DiceTechStack")
  • name string nullable
  • image string nullable
• locations array (default: [])
  • @type string (default: "DiceCompanyLocation")
  • city string nullable
  • state string nullable
  • country string nullable
  • display_name string nullable
  • is_headquarters boolean nullable
• social_media object nullable
  • @type string (default: "DiceCompanySocialMedia")
  • facebook string nullable
  • instagram string nullable
  • twitter string nullable
• benefits object nullable
  • @type string (default: "DiceCompanyBenefits")
  • child_care_parental array (default: [])
  • diversity_equity_inclusion array (default: [])
  • financial_retirement array (default: [])
  • health_wellness array (default: [])
  • perks_discounts array (default: [])
  • professional_development array (default: [])
  • vacation_time_off array (default: [])
  • work_culture array (default: [])
• awards array (default: [])
  • @type string (default: "DiceCompanyAward")
  • name string nullable
  • year string nullable
  • image string nullable
• images array (default: [])
• videos array (default: [])
• updated_at 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 — Company profile 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.