How can I retrive the media url from the routes showing only the id in the media object

Community Packages Plugins
1

“media”: {

                "id": 1

            }

The above is the result that I got when I call the registrations route, I have uploaded the photos and integrate with S3. In the response, I got the media showing the id only. How can I try to achieve showing the url of related images.
Below is my media components,

image
image1211×561 47.6 KB

When calling the /api/v1/upload/files routes, I got all the files uploaded to S3. Is there a way to display the url in the response?

Any kind suggestions and tips are welcomed. Thanks.

2

I think you can api/upload/files/:id to get a single file.

3

Hi Eventyret,

I’m really appreciate for your comment. I’ve tried api/upload/files/:id before and I have only the file by the id which are not related to the resources here, GET api/registrations. This is my concern to know how I can retrieve the media by id from GET api/registrations. The id here 1 doesn’t represent the file in the api/upload/files route.

4

This is the response get from api/upload/files

image
image1206×374 36.9 KB

The response are all the files uploaded through strapi dashboard.

5

You can use “populate” attribute on query.

An example

Article: {
    title,
    content,
    media
}

add to endpoint of articles populate param, and you get all data of media object.
/api/articles?populate=*

6

Hi there i am also intrested about this
Here is a nice guide to population by strapi

I made some helper functions for the process itself but I am with the same tools qs query ect.
I ran into this @William_Kyaw when I escalated a media (image) as a resusable component
even populate: “*” gave back only id: number inside the media {}. There is no data {} to crawl further.
If i throw the image to the root (or anywhere) as a new element it be seen nicely.
I tried nested population ect.
If this is solved somehow would be great to know how.

7

Any solutions? I got same response @William_Kyaw

8

This error does not occur when using graphql :call_me_hand: