Filtering & Querying
Most API endpoints support query parameters for filtering, and all query result endpoints support pagination. This guide covers the common patterns.
Filtering Entities
Structure endpoints like nodes, members, and sections support query parameters to narrow down results.
Getting a Single Entity
Access any entity by its Id using the indexer (C#) or by_id
(Python):
Querying Analysis Results
After running an analysis, query endpoints return results in a flat, efficient format. All query endpoints support optional filters for load case and entity key.
Node Reactions
Filtering by Load Case and Node
Filter values use SG list format — a string of comma-separated Ids
and dash-separated ranges (e.g. "1,3-7,10"). Pass an empty string
or omit the parameter to return all results.
Member Intermediate Forces
Grouped results like member forces use a columnar layout — the parent object contains the case and member keys, with force values as parallel arrays indexed by station.
Buckling Load Factors
Natural Frequencies
Steel Design Check Summary
Pagination
All query endpoints support offset and limit for pagination. By
default all results are returned. Use pagination for large result sets.

