Register source objects from a storage connection
Authorizations
Body
Response
Register source objects from a storage connection
- Option 1
- Option 2
- Option 3
RFC 3339 timestamp in UTC: the offset is Z or +00:00; any other offset is refused.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|[+-]00:00))$How this Source first arrived. api, cli, sdk-typescript and sdk-python are reported by the client in its Nitsor-Client header, and a request without a recognised one records api: they describe a cooperative caller and prove nothing. cli and sdk-typescript come from earlier clients that are no longer published; the Python SDK reports sdk-python. manual-upload, seed, demo and system are written by the server and no header can claim them. Later arrivals of the same bytes do not change it. unknown marks a Source registered before arrivals were recorded. Absent only from servers older than this field.
api, cli, sdk-typescript, sdk-python, manual-upload, seed, demo, system, unknown The kind of credential that authenticated the first arrival, established by the server: person (a signed-in session or a person token), agent (an Agent credential) or system (deployment access, which the seed and demo runs use). unknown marks a Source registered before it was recorded. Absent only from servers older than this field.
person, agent, system, unknown