Submit a SAR/RF collection request
POST/collection-requests
Asks for a SAR or RF collection over an area of interest, once or on a recurring schedule. A request states what is wanted – the product type, where, and when – never how it is collected, so sensor, beamMode, and provider are rejected rather than ignored.
Submitting a request notifies Vantor operations, who work it with the collection provider. It is not yet a confirmed collection: every occurrence starts as Requested, moves to Accepted once the collection is confirmed with the provider, and becomes Fulfilled when the expected scene that satisfies it is delivered. All occurrences of a recurring series are created at submission.
Required permissions: CROWS_NEST_BASE_USER
Request
Responses
- 201
- 400
- 401
- 403
- 500
Collection request created, with its occurrences.
Invalid payload. For example: a missing required field, sensor, beamMode, or provider supplied, a collectionMode on an RF request, an invalid geometry or one over the vertex limit, a window that ends before it starts, an incomplete recurrence rule or one that runs past the maximum series length, customer omitted when the token can manage more than one customer, or a customer outside the caller's scope.
Unauthorized – missing or invalid JWT.
Forbidden – token lacks required role or customer scope.
Internal server error.