Get Metadata
Authorizations
AuthorizationstringRequired
The File Management API uses JWT (JSON Web Tokens) for authentication.
Obtaining a Token
To retrieve a valid token, you must call the login/idm/tokens endpoint.
- Requirements: Use a Service Account that has been assigned the Content Export Reader role.
- Response: The JWT will be returned in the
access_tokenfield of the JSON response. - Reference: For detailed steps on the handshake, see the OAuth2 Authenticate documentation.
Using the Token
Once obtained, include the token in the Authorization header for all API requests:
Authorization: Bearer <access_token>
Path parameters
fileIdstringRequiredExample:
The unique ID of the file.
internal_file_id_1Query parameters
typestring · enumRequiredPossible values:
The type of file being managed.
Responses
200
File metadata retrieved successfully.
application/json
idstringRequiredExample:
Unique file identifier.
internal_file_id_1namestringRequiredExample:
File name.
s_POD_ID_SD-2025-01-01-00_ED-2025-05-12-09_GD-2025-05-12_1747050746368.zip.pgpsizeinteger · int64OptionalExample:
File size in bytes.
1234567uploadTimestring · date-timeOptionalExample:
Timestamp of when the file was uploaded (ISO 8601 format).
2024-05-15T10:00:00ZcontentTypestringOptionalExample:
MIME type of the file.
application/pgp-encryptedintegrityHashstringOptionalExample:
A cryptographic hash of the file content.
e79e8e823f2df5091d1e4e1583816c07977d3f11b676f91c9f8dcc53c26e271dtypestringRequiredExample:
The type of file.
ContentExport401
Unauthorized - Authentication failed.
application/json
403
Forbidden - Invalid entitlements.
application/json
404
Not Found - File not found.
application/json
500
Internal Server Error.
application/json
get
/files/v1/{fileId}/metadataLast updated
Was this helpful?