Forge Object Store is now in Preview, and therefore fully supported. However, it remains under active development and may be subject to shorter deprecation windows. Preview features are suitable for early adopters in production environments.

We release preview features so partners and developers can study, test, and integrate them prior to General Availability (GA). For more details, see Forge EAP, Preview, and GA.

When a request fails, the Forge Object Store returns a structured error response:

1
2
3
4
5
6
interface ForgeError {
  code: string;
  message: string;
  suggestion: string;
}

In this response:

code: A machine-readable error code.
message: A human-readable description of the error.
suggestion: A recommended action to resolve the error.

Status codes

Common HTTP status codes returned by the Object Store:

Status code	Description
`400`	Invalid request body or parameters.
`404`	The requested object was not found.
`429`	Rate limit exceeded. See Object Store limits.
`500`	Internal server error.

Unsupported upload checksum type

Starting December 10, 2026, upload requests using SHA1, CRC32, or CRC32C will return HTTP 400 with the error code CHECKSUM_TYPE_UNSUPPORTED. To resolve this error, calculate a SHA-256 hash of the file content, encode the digest as base64, and set checksumType to 'SHA256'.

See Upload checksums and the deprecation notice for details.