Read customer-safe ingestion status under the original API key
Generated from the checked-in source. Do not edit this reference by hand.
GET /v1/media/image-ingestions/{id}
Operation: getImageIngestionConsent.
Authentication
Section titled “Authentication”Use the credential and permission scope described above. Each object below is an alternative; schemes within one object are required together.
[ { "bearerAuth": [] }, { "niuApiKeyAuth": [] }]HTTP request
Section titled “HTTP request”Set NIU_ORIGIN to your installation origin (without /v1). Replace path, query and header placeholders with the required values. Query examples use curl 7.87 or newer to encode values with --url-query. Use the credential scope described above; a bearer token must have the authority required by this operation.
Authentication alternative: bearerAuth.
curl --fail-with-body -X GET "$NIU_ORIGIN/v1/media/image-ingestions/{id}" \ -H "Authorization: Bearer $NIU_BEARER_TOKEN"Authentication alternative: niuApiKeyAuth.
curl --fail-with-body -X GET "$NIU_ORIGIN/v1/media/image-ingestions/{id}" \ -H "X-Niu-API-Key: $NIU_API_KEY"Parameters
Section titled “Parameters”Location: path. Required.
{ "type": "string", "format": "uuid"}Request body
Section titled “Request body”No request body is declared.
Responses
Section titled “Responses”HTTP 200
Section titled “HTTP 200”Consent status with nullable allowlisted reason, duration_ms and observed_at from its immutable outcome; no credentials, source tokens, upstream identifiers or procurement data
HTTP 401
Section titled “HTTP 401”Active API key required
HTTP 404
Section titled “HTTP 404”Consent unavailable under this API key