Batch search chemical details by cichem ids
Request Body
application/json
Batch lookup request by cichem_id with optional projection
Batch lookup request by cichem_id
List of cichem_id values (required, non-empty, max 2000)
Response projection
"standard"Value in
- "standard"
- "full"
Response Body
application/json
application/json
curl -X POST "https://example.com/chemical/details/search/by-cichem-id" \ -H "Content-Type: application/json" \ -d '{ "cichemIds": [ "string" ] }'{ "data": [ { "pubchemCid": 0, "cichemId": "string", "cicompId": "string", "casrn": "string", "dtxcid": "string", "dtxsid": "string", "chemblId": "string", "primaryName": "string", "systematicName": "string", "molFormula": "string", "monoisotopicMass": 0 } ], "total": 0, "suggestions": [ "string" ]}Search chemicals by identifier, name or value prefix GET
Multi-step chemical search. 1. Pre-processing: trim + uppercase; EC numbers (NNN-NNN-N), CASRN (leading zeros stripped), InChIKeys and numeric values (e.g. partial CASRN `1912-24`) keep their dashes; unicode dashes are normalized; otherwise `-` is replaced by a space. 2. Exact step: rows whose modified value equals the word (or the word without spaces) for the configured identifier/name types. 3. Prefix step (skipped for CASRN, CI chemical/compound ids, DTXSID/DTXCID, or when the first exact hit is a CASRN): rows whose modified value starts with the word, limited to `top`. InChIKey values are included only when the word is at least 14 characters long. 4. Post-processing: exact rows first, de-duplicated by chemical (first row wins), limited to `top`. No match returns `200` with empty `data`, explanatory `messages` and optional `suggestions` (e.g. a formatted CASRN for digits-only input, or related InChIKeys).
Search chemical details by cichem id GET
Next Page