Trying to design an API where the content when referenced has multiple parts that make up its ID instead of just one singular ID due to it possible being in different areas that are segmented. Any feedback or references to similar examples would be great. Looking for any pitfalls that I might not be able to foresee for now.

Example

Normal APIs: /v1/files/{fileId}

Mine: /v1/files/{region}/{parentFolder}/{fileId}

Possible Options

Keeping the multiple parts as is

/v1/files/{region}/{parentFolder}/{fileId}

Using base64 on {region}/{parentFolder}/{fileId} to send it as one ID

I’m wary of working my way into some sort of anti-pattern with this.

/v1/files/{encodedParts}

Sticking with /v1/files/{fileId} and putting region and parent folder in query params (can’t have a body in GET requests of course)

/v1/files/{fileId}?region=US&parentFolder=parentFolderId