/otta/companies/search

POST /api/otta/companies/search

Price: 5 credits

Search Otta tech companies. Filter by company name, employee-count band, business sectors / industries and job locations. Returns company cards with name, logo, short description, employee-count band, business sectors, total funding and the locations they hire in.

How to use it

Search Otta (Welcome to the Jungle) tech companies and discover startups by sector, size and location. Filter by keyword (company name), company_sizes, sectors and locations. Returns company cards; use otta/companies with an alias from a card to get the full enriched profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string — Company name to filter by (default: "")
• count integer required — Max number of companies to return (min: 1)
• company_sizes array — Filter by company employee-count band (default: []; one of: "1-20", "21-100", "101-200", "201-500", "501-1000", "1001+")
• sectors array — Filter by business sectors / industries (default: []; one of: "Accelerator", "Accessibility", "Accounting", "Advertising", "Aerospace", "Age-tech", "Agency", "Agriculture", "Analytics", "API", "Art", "Artificial Intelligence", "Augmented Reality", "Automation", "B2B", "B2C", "Banking", "Beauty", "Big data", "Biology", "Biotechnology", "Blockchain", "Bookkeeping", "Business Intelligence", "Capital Markets", "Cars", "Charity", "Childcare", "Cloud Computing", "Communication", "Community", "Compliance", "Computer Vision", "Construction", "Consulting", "Consumer Appliances", "Consumer Goods", "Content", "Credit cards", "Credit Scoring", "Crowdfunding", "Cryptocurrency", "Customer service", "Cyber Security", "D2C", "Data Analysis", "Data Integration", "Data Sharing", "Data storage", "Dating", "Deep Tech", "Delivery", "Dentistry", "Design", "DevOps", "Digital Media", "Discount", "Drones", "eCommerce", "Education", "Electric Vehicles", "Energy", "Enterprise", "Entertainment", "Environmental", "eSports", "Events", "Fashion", "Femtech", "Financial Services", "Fintech", "Fitness", "Flexible working", "Flights", "Flowers", "Food", "Foreign exchange", "Fraud", "Freight", "Fundraising", "Furniture", "Gambling", "Gaming", "Governments", "Hardware", "Healthcare", "Home improvement", "Hospitality", "HR", "Identity", "Incubator", "Insurance", "Interior design", "Internal tools", "Internet of Things", "Investing", "Kids", "Languages", "Lead generation", "Learning", "Legal", "Lending", "Lifestyle", "Location services", "Logistics", "Machine Learning", "Manufacturing", "Market research", "Marketing", "Marketplace", "Media", "MedTech", "Mencare", "Mental health", "Mobile", "Mobility", "Mortgages", "Music", "Nature", "Navigation", "Networking", "No-Code", "Nutrition", "Office", "Outsourcing", "Payments", "Personal finance", "Personal health", "Pets", "Printing", "Privacy", "Procurement", "Product", "Product Management", "Productivity", "Property", "Publishing", "Real Estate", "Recruitment", "Regtech", "Renting", "Retail", "Reviews", "Ridesharing", "Robotics", "SaaS", "Sales", "Science", "Security", "Sharing Economy", "Social", "Social Impact", "Social Media", "Sports", "Strategic Intelligence", "Subscription", "Supply Chain", "Sustainability", "Telecommunications", "Ticketing", "Toys", "Trading", "Training", "Transport", "Travel", "Tutoring", "Venture Capital", "Video", "Virtual Reality", "Visualisation", "Web 3.0", "Web Design", "Weddings", "Wellbeing")
• locations array — Filter by office or remote job locations (default: []; one of: "AMSTERDAM", "AUSTIN_US", "BARCELONA", "BERLIN", "BIRMINGHAM", "BOSTON_US", "BRISTOL", "CAMBRIDGE", "CARDIFF", "CHICAGO_US", "DENVER_US", "DUBLIN", "EDINBURGH", "GLASGOW", "LEEDS", "LONDON", "LOS_ANGELES_US", "MANCHESTER", "MIAMI_US", "NEW_YORK_US", "NOTTINGHAM", "OXFORD", "PARIS", "REMOTE_CANADA", "REMOTE_EUROPE", "REMOTE_FRANCE", "REMOTE_GERMANY", "REMOTE_IRELAND", "REMOTE_NETHERLANDS", "REMOTE_SPAIN", "REMOTE_UK", "REMOTE_US", "SAN_FRANCISCO_BAY_AREA_US", "TORONTO", "VANCOUVER")
• currency string — Currency for funding amounts (default: "GBP"; one of: "CAD", "EUR", "GBP", "USD")

Response

• @type string (default: "OttaCompanyCard")
• id string nullable
• alias string nullable
• name string nullable
• image string nullable
• favicon string nullable
• primary_colour string nullable
• short_description string nullable
• live_job_count integer nullable
• size string nullable
• sectors array (default: [])
  • @type string (default: "OttaSector")
  • id string nullable
  • value string nullable
• total_funding object nullable
  • @type string (default: "OttaMoney")
  • amount integer nullable
  • currency string nullable
• job_locations 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 — The entity was not found, or a precondition failed 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.