How the Targeton API Works¶

The API combines data from four Benchling endpoints into a single harmonised response. The processing steps are executed in order for every request.

Step 1 – Screen Pellet Lookup¶

The API first searches the Benchling Screen Pellet schema using the supplied name value.

If a matching Screen Pellet is found:

• library_type is set to screen
• replicate and pellet_day values are extracted from the record
• The associated Targeton information is retrieved

If no Screen Pellet is found, the API proceeds to Step 2.

Step 2 – HDR Vector Fallback¶

If Step 1 yields no result, the API searches the Benchling HDR Vector Lot schema using the same name value.

If a matching HDR Vector Lot is found:

• library_type is set to plasmid
• The associated Targeton information is retrieved
• replicate and pellet_day are not applicable and are returned as null

If neither schema contains a matching record, the API returns a 404 Not Found error.

Step 3 – Targeton Oligo Library Lookup¶

Using the Targeton API ID resolved in Step 1 or Step 2, the API queries the Targeton Oligo Library schema.

If multiple Targeton Oligo Library records are returned, the record with the highest Version value is selected.

The following fields are retrieved from the selected record:

• consequences_link
• valiant_output_link

Step 4 – LibAmp Primer Lookup¶

The API retrieves all LibAmp Primer records associated with the resolved Targeton and returns the primer sequences within a named object in the response.

Primers are returned as:

• LibAmp_F — forward primer sequence
• LibAmp_R — reverse primer sequence