POST /api/siemens/search/partners/digital
Price: 1 credit
Search Digital Industries Software partner.
Search Siemens Digital Industries Software partners by country, needs, product category, and industry.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)partner_name string — Partner name search text (default: ""; examples: "Siemens")country string required — Country code (AU, TR, US, etc.) (examples: "US")location string — Location text (default: ""; examples: "New York")your_needs string — Your Needs filter. Options: All, Purchase products or solutions (Solution Providers (VAR/Resellers)), Explore technology and apps (Software & Technology Partner), Find professional services (Consulting & System Integrator) (default: "All"; one of: "All", "Solution Providers (VAR/Resellers)", "Software & Technology Partner", "Consulting & System Integrator"; examples: "All")product_category string — Product Category filter (default: "All"; one of: "All", "ADDITIVE MANUFACTURING", "ASSEMBLY", "CLOUD SOLUTIONS", "COMOS", "DI HOSTED BUSINESS", "FEMAP", "HEEDS", "INSIGHTS HUB", "INTEGRATED ELECTRICAL SYSTEMS", "LEARNING SERVICES", "LOGISTICS SCHEDULING", "MANUFACTURING EXECUTION", "MENDIX", "MOTION CONTROL", "NX FOR DESIGN", "NX FOR MANUFACTURING", "OPCENTER-APS", "OPEN TOOLS", "PADS", "PERFORMANCE TESTING", "PLM-MULTI", "POLARION", "PRODUCT COSTING", "QUALITY MANAGEMENT", "RESEARCH DEVELOPMENT &LABORATORY", "RULESTREAM", "SERVICES", "SIMCENTER 3D SOLUTIONS", "SIMCENTER-AMESIM", "SIMCENTER-FloEFD", "SIMCENTER-FLOTHERM", "SIMCENTER-STAR-CCM+", "SIMULATION AND TEST SOLUTIONS", "SOLID EDGE", "SUPPLYFRAME", "TC CONTENT AND DOCUMENT MANAGEMENT", "TC PRODUCT CONFIGURATOR", "TEAMCENTER", "VALOR"; examples: "All")industry_focus string — Partner Industry Focus filter (default: "All"; one of: "All", "Aerospace and Defense", "Automotive and Transportation", "Banking, Financial &Credit Institution", "Battery", "Business Services", "Clearing House Review", "Consumer Products And Retail", "Education", "Electronics and Semiconductor", "Energy and Utilities", "Government", "Healthcare", "Heavy Equipment", "Industrial Machinery", "Infrastructure &Construction", "Insurance", "Marine", "Medical Device and Pharmaceutical", "Other Industries", "Process Industries", "Real Estate", "Service Industries", "Software &IT"; examples: "All")count integer required — Max result count (>: 0)@type string (default: "SiemensPartnerFinderResult")name string requiredpartner_type string (default: "")location_count integer (default: 0)location_name string (default: "")mailing_address string (default: "")contact string (default: "")email string (default: "")phone string (default: "")website string (default: "")product_specialization string (default: "")image string (default: "")latitude number (default: 0)longitude number (default: 0)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.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.