RCSB PDB Sequence Coordinates Service API Migration Guide

RCSB PDB Sequence Coordinates API changes

Migrating from the 1D Coordinates Service to the Sequence Coordinate Service involves updating your endpoint URLs to call the new service and modifying your applications to account for breaking changes introduced in the new API.

HTTP Request

The Sequence Coordinates Service API only support HTTP POST requests.

End Points

Endpoint alignment has been renamed to alignments.

1D Coordinates Service Sequence Coordinates Service

Endpoint group_alignment has been renamed to group_alignments.

1D Coordinates Service Sequence Coordinates Service

End Points Arguments

Endpoint group_annotations boolean argument histogram has been removed. Its functionality has been replaced by a new endpoint group_annotations_summary with the same signature.

1D Coordinates Service Sequence Coordinates Service

Enumerated values of GroupReference are now screaming snake case

>
1D Coordinates Service Sequence Coordinates Service

Query Fields

Field target_alignment has been renamed to target_alignments.

1D Coordinates Service Sequence Coordinates Service

Field target_alignment_subset has been removed. The motivation of this field was to request a subset of alignment based on offset and length arguments. This functionality has been moved to target_alignments field that accepts optional arguments as the removed field.

1D Coordinates Service Sequence Coordinates Service

Type Names

GraphQL type name changes. This only affects programmatic users that build types from GraphQL schema

Contact Us

Contact info@rcsb.org with questions or feedback about this service.