To support requesting a large number of objects, the Endpoint supports pagination as defined in section . Clients can optionally provide their desired number of items per page and which page they want and servers will return that result set. Servers can also override client-provided pagination parameters, including requiring pagination when it isn't requested. As such, all clients should be aware that responses to this Endpoint may be paginated and be prepared to properly handle that. When requesting STIX 2.0 content, the content will always be delivered in a STIX bundle (even if there's only zero or one objects, in which case the bundle will be empty or only contain one object). Other content types can be requested by using a different Accept header, however the specific representation of other content types is not defined. Properties Supported Method GET URL /<api-root>/collections/<id>/objects/ <api-root> - the base URL of the API Root containing the Collection Parameters <id> - the identifier of the Collection from which objects are being requested Pagination Yes Filtering Yes - id, type, version Valid Request Type Accept: application/vnd.oasis.stix+json; version=2.0 200 (OK) Successful Response Status: Content-Type: application/vnd.oasis.stix+json; version=2.0 Body: bundle Requests for other content types are permitted and may result in other response bodies. Common Codes 404 - The Objects resource does not exist or the client does not have access to the Objects resource. - The client either needs to authenticate or does not have access 401, 403 to get objects in the Collection. Examples GET Request GET /api1/collections/91a7b528-80eb-42ed-a74d-c6fbd5a26116/objects/ HTTP/1.1 Host: example.com Accept: application/vnd.oasis.stix+json; version=2.0
To support requesting a large number of objects, the Endpoint supports pagination as defined in section . Clients can optionally provide their desired number of items per page and which page they want and servers will return that result set. Servers can also override client-provided pagination parameters, including requiring pagination when it isn't requested. As such, all clients should be aware that responses to this Endpoint may be paginated and be prepared to properly handle that. When requesting STIX 2.0 content, the content will always be delivered in a STIX bundle (even if there's only zero or one objects, in which case the bundle will be empty or only contain one object). Other content types can be requested by using a different Accept header, however the specific representation of other content types is not defined. Properties Supported Method GET URL /<api-root>/collections/<id>/objects/ Parameters <api-root> - the base URL of the API Root containing the Collection <id> - the identifier of the Collection from which objects are being requested Pagination Yes Filtering Yes - id, type, version Valid Request Type Accept: application/vnd.oasis.stix+json; version=2.0 Successful Response Status: 200 (OK) Content-Type: application/vnd.oasis.stix+json; version=2.0 Body: bundle Requests for other content types are permitted and may result in other response bodies. Common Codes 404 - The Objects resource does not exist or the client does not have access to the Objects resource. 401, 403 - The client either needs to authenticate or does not have access to get objects in the Collection. Examples GET Request GET /api1/collections/91a7b528-80eb-42ed-a74d-c6fbd5a26116/objects/ HTTP/1.1 Host: example.com Accept: application/vnd.oasis.stix+json; version=2.0