Uploading an image as an asset from a URL and using createIfNotExists and createOrReplace in the Sanity API.

I'm using this command to upload an image from the airtable code block as an asset:
but I'm getting this error:


Can anyone help how to upload an image as an asset from a url string?

Hi Aldrin - this seems like an issue with not having a readable stream for the image. Could it be an issue with access to the Airtable image, e.g. needing a token? Does the issue persist if you try with a publicly available image?

hey dude thanks for replying. the image in the url is publicly available, i just tried in incognito

Thanks Aldrin - looks like the issue is different.

curl

here relies on using a local file as shown by the

@/Users/mike/images/bicycle.jpg

portion of the example. When inserting a remote URL instead,

curl

doesn't fetch and upload, so we're essentially sending a URL as image content. To create a readable stream, an extra step is necessary before including it in the POST request. For example:

Hope that helps!

thanks , i'll try this one

hi peter, thank you for your suggestion. its working now. cheers!

Awesome, Aldrin! Glad to hear 🙂

i do have another question. in the mutations api (https://www.sanity.io/docs/http-mutations ), i'm trying to use

createIfNotExists

, what does the api check if the record exists? the

_id

?

is it also the same case if i try to use

createOrReplace

? i need to pass the sanity id?

That's correct, it checks if any document with the provided

_id

exists. If you use

createIfNotExists

, a new document will only be created if a document with a given

_id

does not exist yet.

createOrReplace

, on the other hand, creates (or sets) the document even if a document with the same

_id

already exists, thereby replacing it.
Specifically,

createOrReplace

checks if the

_id

and the

_type

exist. If both are the same, it acts as a

set

patch to replace the document's entire contents. If the

_id

is the same but the

_type

is different, it deletes the old doc and then creates the new one. The result of both is the same but the procedure behind the scenes is slightly different.
Hope that clarifies things
🙂

if i pass

null

as an id for

createIfNotExists

, it should be an automatic create, right?

also, on succesful api call, is the

transactionId

the sanity id of the document?

hey ! any ideas for this? the transactionid mentioned seems to be the

_rev

revision id instead of the document id. How can we get the

_id

to postback to Airtable?

If no ID is provided, it should generate a new, unique ID for you - but only if you use

create

and not

createIfNotExists

in this case. The latter requires an explicit

_id

.
As Micaela suggested,

transactionId

is the

_rev

(revision) and not the document

_id

.
If you need to return the document

_id

to Airtable, you could consider fetching the document after creation, using a query like: