Skip to main content
POST
/
api
/
image_fromurl
Classify an image from URL
curl --request POST \
  --url https://backend.identifai.net/api/image_fromurl \
  --header 'Content-Type: multipart/form-data' \
  --header 'X-Api-Key: <api-key>' \
  --form 'file_url=<string>' \
  --form 'ref_id=<string>' \
  --form with_morphing=true \
  --form with_tampering=true \
  --form with_heatmap=true \
  --form 'webhook_url=<string>'
{
  "identifier": "8d64370a87b820cc1cf620338f5c898bab37439c9a405f32d9eaffc50c4f27b0"
}

Authorizations

ā€‹
X-Api-Key
string
header
required

Your API key.

Body

multipart/form-data
ā€‹
file_url
string
required

The URL of the image to be classified.

ā€‹
ref_id
string

An optional reference ID to associate with the classification request.

ā€‹
with_morphing
boolean

Set it to true if you also want to analyze people's faces in the image using morphing.

ā€‹
with_tampering
boolean

Set it to true if you also want to analyze signs of tampering or manipulation without the aid of a Generative AI

ā€‹
with_heatmap
boolean

Set it to true if you also want to get an AI content heatmap.

ā€‹
webhook_url
string

If specified, the classification result will also be automatically sent to the entered URL. Otherwise, the result can be obtained by polling the relative endpoint. Please note that in order to use a webhook callback URL you need to request a specific enablement, otherwise the parameter is ignored. Moreover, the system may cache the analysis results of repeated submissions, i.e. submissions of the same file with the same options: in this case the webhook won't be called and the results would be accessible only by polling the relative endpoint.

Response

The classification identifier. The format depends on the Accept header.

ā€‹
identifier
string
Example:

"8d64370a87b820cc1cf620338f5c898bab37439c9a405f32d9eaffc50c4f27b0"