/seedrs/businesses

POST /api/seedrs/businesses

Price: 1 credit

Get Seedrs (Republic Europe) funded company (secondary market) profile by slug or URL

How to use it

Get a Seedrs (europe.republic.com) funded company's secondary-market profile by slug or URL. Returns indicative current_valuation, total_raised_amount, performance (share-price change %), investor_count, available_shares, the full historical share_prices series, sector, incorporation date and Companies House number, registered address, and social links.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• business string required — Business slug ('revolut') or business URL ('https://europe.republic.com/revolut') (examples: "revolut", "https://europe.republic.com/revolut"; minLength: 1)

Response

• @type string (default: "SeedrsBusiness")
• id integer required
• alias string required
• name string required
• description string nullable
• url string required
• image string nullable
• cover_image string nullable
• country string nullable
• currency string nullable
• funded_through_cohort boolean nullable
• current_valuation number nullable
• total_raised_amount number nullable
• performance number nullable
• investor_count integer nullable
• available_shares number nullable
• state string nullable
• is_raising boolean nullable
• sector object nullable
  • @type string (default: "SeedrsCategory")
  • id integer nullable
  • name string required
  • alias string nullable
• customer_type object nullable
  • @type string (default: "SeedrsCategory")
  • id integer nullable
  • name string required
  • alias string nullable
• digitisation object nullable
  • @type string (default: "SeedrsCategory")
  • id integer nullable
  • name string required
  • alias string nullable
• eligible boolean nullable
• last_trading_cycle_amount_sold number nullable
• next_business_update_due_at string nullable
• last_business_update_published_at string nullable
• last_business_update_requested_at string nullable
• funding_rounds_count integer nullable
• raising_now_campaign_slug string nullable
• percentage_raising number nullable
• secondary_market object nullable
  • @type string (default: "SeedrsSecondaryMarket")
  • eligible boolean nullable
  • available_shares number nullable
  • last_trading_cycle_amount_sold number nullable
• share_prices array (default: [])
  • @type string (default: "SeedrsSharePrice")
  • price number nullable
  • price_exchanged number nullable
  • currency string nullable
  • date string nullable
• health_message string nullable
• transfer_rights string nullable
• nominee_investment boolean nullable
• shareholder boolean nullable
• has_active_buy_offer boolean nullable
• requested_shares number nullable
• incorporation_date string nullable
• companies_house_number string nullable
• address object nullable
  • @type string (default: "SeedrsAddress")
  • line_1 string nullable
  • line_2 string nullable
  • city string nullable
  • country string nullable
  • postcode string nullable
• website_url string nullable
• twitter_url string nullable
• linkedin_url string nullable
• facebook_url string nullable
• instagram_url 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 — Business 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.