- Legion API
- Feed Data
- Upload feed file data
Upload feed file data
const url = 'https://api.hopper.west.prod.govcloud.legion.picogrid.com/v3/feeds/files';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"blob_metadata":{},"entity_id":"c3d4e5f6-a1b2-7890-1234-567890abcdef","feed_definition_id":"f7a8b9c0-d1e2-3f4a-5b6c-7d8e9f0a1b2c","file_content_type":"example","recorded_at":"2024-02-16T21:45:33Z"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.hopper.west.prod.govcloud.legion.picogrid.com/v3/feeds/files \ --header 'Content-Type: application/json' \ --data '{ "blob_metadata": {}, "entity_id": "c3d4e5f6-a1b2-7890-1234-567890abcdef", "feed_definition_id": "f7a8b9c0-d1e2-3f4a-5b6c-7d8e9f0a1b2c", "file_content_type": "example", "recorded_at": "2024-02-16T21:45:33Z" }'Upload file-based feed data using multipart/form-data. The request should contain a ‘metadata_json_payload’ field with JSON metadata matching the IngestFeedFileDataRequest schema, and a ‘file’ field with the binary file content. Note: This endpoint uses multipart/form-data, not application/json as shown in the schema below.
Request Bodyrequired
Section titled “Request Bodyrequired”object
object
Example
c3d4e5f6-a1b2-7890-1234-567890abcdefExample
f7a8b9c0-d1e2-3f4a-5b6c-7d8e9f0a1b2cExample
2024-02-16T21:45:33ZResponses
Section titled “Responses”Successful response
object
Example
{ "entity_id": "c3d4e5f6-a1b2-7890-1234-567890abcdef", "feed_definition_id": "f7a8b9c0-d1e2-3f4a-5b6c-7d8e9f0a1b2c", "file_storage_type": "S3", "recorded_at": "2024-02-16T21:45:33Z", "uploaded_at": "2024-02-16T21:45:40Z"}Bad Request
object
object
Example
{ "code": 400, "details": [ { "Field": "organization_id", "Issue": "must be a valid UUID format" } ], "message": "Request cannot be processed due to invalid input", "status": "error", "timestamp": "2026-01-15T14:32:45Z", "trace_id": "req_2J9K8L7M6N5P4Q3R"}Unauthorized
object
object
Example
{ "code": 401, "details": [ { "Field": "authorization_header", "Issue": "Bearer token is expired or malformed" } ], "message": "Authentication credentials are missing or invalid", "status": "error", "timestamp": "2026-01-15T14:32:45Z", "trace_id": "req_2J9K8L7M6N5P4Q3R"}Forbidden
object
object
Example
{ "code": 403, "details": [ { "Field": "required_scope", "Issue": "requires 'orion:settings:write' scope, but token only has 'orion:settings:read'" } ], "message": "Access denied: insufficient permissions for this resource", "status": "error", "timestamp": "2026-01-15T14:32:45Z", "trace_id": "req_2J9K8L7M6N5P4Q3R"}Not Found
object
object
Example
{ "code": 404, "details": [ { "Field": "organization_id", "Issue": "organization with ID 'a1b2c3d4-e5f6-7890-abcd-ef1234567890' not found" } ], "message": "The requested resource could not be found", "status": "error", "timestamp": "2026-01-15T14:32:45Z", "trace_id": "req_2J9K8L7M6N5P4Q3R"}Internal Server Error
object
The category of the error
The HTTP status code
Additional details about the error
object
The field that caused the error
The specific issue with the field
A human-readable error message
The status of the response, always ‘error’ for error responses
The timestamp when the error occurred
A unique identifier for tracing the error
Example
{ "category": "server_error", "code": 500, "details": [ { "field": "field_name", "issue": "Field validation issue" } ], "message": "Internal Server Error", "status": "error", "timestamp": "2024-03-15T10:30:00Z", "trace_id": "b7c5e4d3-a2b1-4f0e-8d9c-1a2b3c4d5e6f"}Version 3.14.0 · commit 0771262
