Declare file topics
Register the topic data one already-uploaded file carries, naming no session.
Answers 200 once the request has been processed, even when the platform registered only some of its
declarations: the response carries one element per declared topic, in request order, holding either the
topic that declaration registered against or the error that refused it. A file that is not Available,
or a listed representation naming a file that is not an Available file of the same org, answers 404;
a caller without edit access to the file or to a file a listed representation names, 401;
and a malformed request, 400. A request stating is_default_for_reads on a timeline source, true or false,
also answers 401 unless the caller has topic edit access in the org: which source a schema’s reads fall back to
is a property of the org’s topics, not of any one file. Each of these is settled before the first declaration
is prepared, so a refused request registers nothing.
Each declaration’s anchor_ns is an integer of nanoseconds since the Unix epoch, or any value
roboto.time.to_epoch_nanoseconds reads: a float or numeric string is seconds, and an ISO 8601
string is that instant.
Access control
- Restricted tokens need the API scope
api.everything_else
/v1/files/id/{fs_node_id}/topicsAuthorizationBearer token · headerrequiredfs_node_idstringrequiredX-Roboto-Org-IdstringX-Roboto-User-Idstringapplication/jsontopicsFileTopicDeclaration[]requiredShow propertiesHide properties
FileTopicDeclarationtopic_namestringrequiredtopic_schemaSchemarequiredThe structure of one topic's data: the columns it carries.
However a schema is produced, whether hand-written field by field or converted from a source format's own metadata, the registered result is the same: schemas are content-addressed server-side. Identity covers every attribute of every field (name, path, source data type, canonical type, and unit), so identical declarations collapse to a single stored schema no matter how many times they are repeated, while declarations differing in any field attribute are stored separately.
A column a timeline source reads is declared by typing it
:py:attr:~roboto.domain.topics.record.CanonicalDataType.Timestamp with a
:py:class:~roboto.time.TimeUnit unit; nothing else marks it. Which of a topic's timeline sources reads
fall back to is not part of the schema: it is stated on
:py:attr:~roboto.experimental.ingest.TopicDeclaration.timeline_sources and can be changed later, so the
same columns are one schema no matter which source is preferred.
This is what a caller declares, so it carries no checksum: the platform computes that from the fields.
:py:class:~roboto.domain.topics.record.TopicSchemaRecord is the stored schema the platform returns,
carrying that checksum and the identifiers it assigns.
Show propertiesHide properties
namestring | nullShow propertiesHide properties
stringnullfieldsField[]requiredShow propertiesHide properties
Fieldnamestringpathstring[]data_typestringrequiredcanonical_data_typeCanonicalDataTypeNormalized data types used across different robotics frameworks.
Well-known and simplified data types that provide a common vocabulary for describing message path data types across different frameworks and technologies. These canonical types are primarily used for UI rendering decisions and cross-platform compatibility.
The canonical types abstract away framework-specific details while preserving the essential characteristics needed for data processing and visualization.
References: - ROS 1 field types: http://wiki.ros.org/msg - ROS 2 field types: https://docs.ros.org/en/iron/Concepts/Basic/About-Interfaces.html#field-types - uORB: https://docs.px4.io/main/en/middleware/uorb.html#adding-a-new-topic
Example mappings:
- float32 -> CanonicalDataType.Number
- uint8[] -> CanonicalDataType.Array
- sensor_msgs/Image -> CanonicalDataType.Image
- geometry_msgs/Pose -> CanonicalDataType.Object
- std_msgs/Header -> CanonicalDataType.Object
- string -> CanonicalDataType.String
- char -> CanonicalDataType.String
- bool -> CanonicalDataType.Boolean
- byte -> CanonicalDataType.Byte
arraybooleanbytecategoricalimagenumbernumber_arrayobjectstringtimestampunknownlatdegfloatlondegfloatlatdegintlondegintunitstring | nullShow propertiesHide properties
stringnulltimeline_sourcesSchemaFieldSource | McapLogTimeSource | McapPublishTimeSource | Mp4PresentationTimeSource[]requiredShow propertiesHide properties
SchemaFieldSource | McapLogTimeSource | McapPublishTimeSource | Mp4PresentationTimeSourcemin_file_timestamp_nsintegerrequiredmax_file_timestamp_nsintegerrequiredis_default_for_readsboolean | nullShow propertiesHide properties
booleannullkindstringfield_pathstring[]requiredmin_file_timestamp_nsintegerrequiredmax_file_timestamp_nsintegerrequiredis_default_for_readsboolean | nullShow propertiesHide properties
booleannullkindstringmin_file_timestamp_nsintegerrequiredmax_file_timestamp_nsintegerrequiredis_default_for_readsboolean | nullShow propertiesHide properties
booleannullkindstringmin_file_timestamp_nsintegerrequiredmax_file_timestamp_nsintegerrequiredis_default_for_readsboolean | nullShow propertiesHide properties
booleannullkindstringdata_rangeany[] | nullShow propertiesHide properties
anynullrepresentationsRepresentationDeclaration[]Show propertiesHide properties
RepresentationDeclarationfile_idstringrequiredstorage_formatRepresentationStorageFormatrequiredSupported storage formats for topic data representations.
Defines the available formats for storing and accessing topic data within the Roboto platform. Each format has different characteristics and use cases.
mcapparquetcontent_formatstring | nullShow propertiesHide properties
stringnulltransformationsstring[]field_pathstring[] | nullShow propertiesHide properties
stringstringnullanchor_nsinteger | nullShow propertiesHide properties
integernullOK
dataobjectrequiredShow propertiesHide properties
responsesBatchResponseElement_TopicIdentityRecord_[]requiredShow propertiesHide properties
BatchResponseElement_TopicIdentityRecord_dataTopicIdentityRecord | nullShow propertiesHide properties
createdstring<date-time> | nullShow propertiesHide properties
string<date-time>nullcreated_bystringrequiredmodifiedstring<date-time> | nullShow propertiesHide properties
string<date-time>nullmodified_bystringrequirednamestringrequiredorg_idstringrequiredtopic_idstringrequirednullerroranyThrown when the conversation context (messages, system prompt, tool results) exceeds the model's context window limit.
The token estimate and the model's context limit are not carried on the exception, so a caller cannot read usage numbers off it.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when authentication fails
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if an operation would exceed a user or org level limit.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if a user is attempting to perform an action unrecognized by the Roboto platform.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if there is a conflict between a resource you're creating and another existing resource
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if a resource is missing or expired.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullAn error the platform reported that this SDK release cannot resolve to a specific exception class.
Reported for an element of a :py:class:~roboto.http.BatchResponse whose error names a code this release
defines no class for, or that arrived without a code, without a message, or as text that is not an
error envelope at all. It carries whatever code and message the platform sent, so a caller handling the
failure still learns what went wrong; when no message could be read, the message is the error's raw text.
The error envelope carries no status code, so http_status_code reports the 500 inherited from
:py:class:RobotoDomainException rather than the status the failure actually had.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown by shimmed out APIs which have not yet been implemented
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when a service is unavailable, such as when it's under heavy load and can't accept new requests. This is expected to be transient and ought to be retried.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when the service times out while processing a request. This is exepcted to be transient and ought to be retried.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when the server cannot complete the request because the response payload exceeds a storage or transport capacity limit (e.g., Lambda response size). This is NOT expected to be transient and should NOT be retried.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | null