Entity upsert endpoints promoted to stable
A number of upsert endpoints are being promoted from v2-beta to the v2 stable API. The new v2 stable endpoints are now live; the corresponding v2-beta endpoints are now deprecated, and will be fully sunset at a later date.
What’s changing?
A collection of endpoints that support an upsert operation are being promoted to the v2 stable API. When provided with a list of objects that includes a Registry ID, these upsert endpoints either update an existing entity (if an entity with that Registry ID already exists) or create a new entity (if an entity with that Registry ID not does already exist). You can also use Registry IDs in schema field values to link to entities being created in the same upsert request.
The following endpoints have been promoted to v2 stable and marked deprecated in v2-beta.
PATCH /dna-sequences/{entity_registry_id}:upsertPATCH /dna-oligos/{entity_registry_id}:upsertPATCH /rna-sequences/{entity_registry_id}:upsertPATCH /rna-oligos/{entity_registry_id}:upsertPATCH /aa-sequences/{entity_registry_id}:upsertPATCH /custom-entities/{entity_registry_id}:upsertPATCH /molecules/{entity_registry_id}:upsertPOST /entities:bulk-upsertPOST /dna-sequences:bulk-upsertPOST /dna-oligos:bulk-upsertPOST /rna-sequences:bulk-upsertPOST /rna-oligos:bulk-upsertPOST /aa-sequences:bulk-upsertPOST /custom-entities:bulk-upsertPOST /molecules:bulk-upsert
When is this happening?
The new v2 stable upsert endpoints are now live! The corresponding v2-beta endpoints are now deprecated, and will be fully sunset at a later date. If you are currently using any v2-beta upsert endpoints, please migrate to the corresponding v2 stable versions.