Object Information
Changed onContains Flows that references the init/Media Object and other information.
The paging query parameters and headers are required for the list of Flow references in the Object. Service implementations should return a complete list of Flow references within reason and API clients should expect paging to happen in some rare cases where a Object is used in many Flows.
When making requests to provided get_urls that are not presigned, clients SHOULD include credentials if the provided URL is on the same origin as the Service itself, akin to the same-origin mode in the WhatWG Fetch Standard. Services MAY support the use of out-of-band credentials where the provided URL is on a different origin to the Service itself. Services SHOULD NOT solely require the use of out-of-band credentials.
Request
- Base URLhttp://localhost:4010
- URLhttp://localhost:4010/objects/{objectId}
- Auth
- HTTP bearer
- or API key in query parameter access_token
- or HTTP basic
Path parameters
The Object identifier. The Object ID may include special characters such as / which should be URL encoded.
Query parameters
Include storage metadata in get_urls. When verbose_storage is false only url, presigned, and label will be included in get_urls and init_object.get_urls.
A list of Object GET URL Labels, formatted for use in query string parameters
A comma separated list of labels of Object get_urls and init_object.get_urls to include in the response. Omitting accept_get_urls will result in no filtering of get_urls or init_object.get_urls. An empty accept_get_urls results in get_urls and init_object.get_urls being empty or omitted in the response. Object get_urls and init_object.get_urls with no label will only be returned if accept_get_urls is omitted. Without get_urls and init_object.get_urls, the response from the service could be substantially faster if it is not required to generate a large number of pre-signed URLs for example. Where multiple filter query parameters are provided, the returned get_urls and init_object.get_urls will match all filters.
A comma separated list of storage_ids of Object get_urls and init_object.get_urls to include in the response. Omitting accept_storage_ids, or providing an empty accept_storage_ids will result in no filtering of get_urls or init_object.get_urls. Object get_urls and init_object.get_urls with no storage ID will only be returned if accept_storage_ids is omitted or empty. A full list of available storage_ids may be found at the service/storage-backends endpoint. Where multiple filter query parameters are provided, the returned get_urls and init_object.get_urls will match all filters.
If set to true, only presigned URLs (i.e. those whos presigned property is true) will be returned in get_urls and init_object.get_urls. If set to false, only non-presigned URLs (i.e. those whos presigned property is false) will be returned in get_urls and init_object.get_urls. If omitted, both presigned and non-presigned URLs will be returned. If presigned is set to false, the response from the service could be substantially faster if it is not required to generate a large number of pre-signed URLs. Where multiple filter query parameters are provided, the returned get_urls and init_object.get_urls will match all filters.
Filter referenced_by_flows on tag values. This option is the same as the tag.{name} query parameter on the /flows/ API endpoint.
Filter referenced_by_flows on tag names. This option is the same as the tag_exists.{name} query parameter on the /flows/ API endpoint.
Filter get_urls and init_object.get_urls on tag values. This option is the same as the tag.{name} query parameter on the /service/storage-backends API endpoint.
Filter get_urls and init_object.get_urls on tag names. This option is the same as the tag_exists.{name} query parameter on the /service/storage-backends API endpoint.
Opaque string used by backend to access a specific page of results. Clients should read the next URL from the Link header returned with responses, or use value of the returned X-Paging-NextKey header. If not supplied, the first page is accessed. Service implementations should ensure a consistent sort order is applied to pages of results.
Restrict the response to the specified number of results. Service implementations may specify their own default and maximum for the limit
Response
Changes
- info
added the new optional
queryrequest parameterstorage_backend_tag.{name} - info
added the new optional
queryrequest parameterstorage_backend_tag_exists.{name} - info
added the optional property
//////to the response with the status - info
added the optional property
/////to the response with the status
- info
- breaking
the response property
/became optional for the status - info
added to the response body
allOflist for the response status - info
removed from the response body
allOflist for the response status - info
added the optional property
/to the response with the status
- breaking