Upload feed file data

POST

/v3/feeds/files

curl --request POST \
  --url https://us-gov.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" }'

• US Government Production API
• Staging API
• Demo API

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 Body^required

Media typeapplication/json

object

blob_metadata

object

entity_id

required

string format: uuid

Example

c3d4e5f6-a1b2-7890-1234-567890abcdef

feed_definition_id

required

string format: uuid

Example

f7a8b9c0-d1e2-3f4a-5b6c-7d8e9f0a1b2c

file_content_type

string

recorded_at

required

string

Example

2024-02-16T21:45:33Z

Responses

200

Successful response

Media typeapplication/json

object

blob_key

required

string

entity_id

required

string format: uuid

feed_definition_id

required

string format: uuid

file_content_type

string

file_size_bytes

required

number

file_storage_type

required

string

recorded_at

required

string

uploaded_at

required

string

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"
}

400

Bad Request

Media typeapplication/json

object

category

string

code

number

details

Array<object>

object

field

required

string

issue

required

string

message

string

status

string

timestamp

string

trace_id

string

Example

{
  "code": "400",
  "details": "sample_value",
  "message": "Request cannot be processed due to invalid input",
  "status": "error",
  "timestamp": "2025-01-15T14:32:45Z",
  "trace_id": "req_2J9K8L7M6N5P4Q3R"
}

401

Unauthorized

Media typeapplication/json

object

category

string

code

number

details

Array<object>

object

field

required

string

issue

required

string

message

string

status

string

timestamp

string

trace_id

string

Example

{
  "code": "401",
  "details": "sample_value",
  "message": "Authentication credentials are missing or invalid",
  "status": "error",
  "timestamp": "2025-01-15T14:32:45Z",
  "trace_id": "req_2J9K8L7M6N5P4Q3R"
}

403

Forbidden

Media typeapplication/json

object

category

string

code

number

details

Array<object>

object

field

required

string

issue

required

string

message

string

status

string

timestamp

string

trace_id

string

Example

{
  "code": "403",
  "details": "sample_value",
  "message": "Access denied: insufficient permissions for this resource",
  "status": "error",
  "timestamp": "2025-01-15T14:32:45Z",
  "trace_id": "req_2J9K8L7M6N5P4Q3R"
}

404

Not Found

Media typeapplication/json

object

category

string

code

number

details

Array<object>

object

field

required

string

issue

required

string

message

string

status

string

timestamp

string

trace_id

string

Example

{
  "code": "404",
  "details": "sample_value",
  "message": "The requested resource could not be found",
  "status": "error",
  "timestamp": "2025-01-15T14:32:45Z",
  "trace_id": "req_2J9K8L7M6N5P4Q3R"
}

500

Internal Server Error

Media typeapplication/json

object

category

required

The category of the error

string

code

required

The HTTP status code

number

details

required

Additional details about the error

Array<object>

object

field

The field that caused the error

string

issue

The specific issue with the field

string

message

required

A human-readable error message

string

status

required

The status of the response, always ‘error’ for error responses

string

timestamp

required

The timestamp when the error occurred

string format: date-time

trace_id

required

A unique identifier for tracing the error

string format: uuid

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"
}