To use this endpoint, provide the URL of a file to extract and parse the hidden exif metadata.
File Exif Extractor - Endpoint Features
| Object | Description |
|---|---|
url |
[Required] |
{"File": {"Url": "https://conasems-ava-prod.s3.sa-east-1.amazonaws.com/aulas/ava/dummy-1641923583.pdf", "FileName": "dummy-1641923583.pdf", "FileSize": 13264, "FileModifyDate": "2026:01:13 21:09:31+00:00", "FileAccessDate": "2026:01:13 21:08:51+00:00", "FileInodeChangeDate": "2026:01:13 21:09:31+00:00", "FileType": "PDF", "FileTypeExtension": "PDF", "MIMEType": "application/pdf"}, "PDF": {"PDFVersion": 1.4, "Linearized": false, "PageCount": 1, "Author": "Evangelos Vlachogiannis", "Creator": "Writer", "Producer": "OpenOffice.org 2.1", "CreateDate": "2007:02:23 17:56:37+02:00"}}
curl --location --request GET 'https://zylalabs.com/api/5259/exif+extractor+api/6774/file+exif+extractor?url=https://conasems-ava-prod.s3.sa-east-1.amazonaws.com/aulas/ava/dummy-1641923583.pdf' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Send a file URL, and the API extracts hidden metadata for analysis and insights.
The Exif Extractor API is a metadata extraction tool that reveals hidden file details such as creation date, location and device information.
Receives file URLs as input, provides extracted exif metadata like dates, locations, and device info.
Investigating the origin and details of images or documents. Forensic analysis of digital files. Verifying authenticity and creation details of online content.
Beside the number of API calls per month allowed, there are no other limitations.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
The API returns detailed metadata from files, including technical information like file size, modification dates, and MIME type, as well as contextual data such as title, keywords, and descriptions.
Key fields include "FileName," "FileSize," "FileModifyDate," "FileType," and "HTML" elements like "Title" and "Description," which provide insights into the file's content and properties.
The response is structured in a JSON format, with a "File" object containing file-specific details and an "HTML" object providing metadata related to the file's content, making it easy to parse.
The API provides information such as file metadata (size, type, modification dates) and embedded HTML metadata (title, keywords, description), useful for content analysis and verification.
Users can customize requests by providing different file URLs to extract metadata from various files, allowing for tailored analysis based on specific content needs.
The data is extracted directly from the files' embedded metadata, ensuring that the information is sourced from the files themselves, which helps maintain accuracy and reliability.
Users can analyze the returned metadata to verify file authenticity, trace origins, or conduct audits, leveraging details like geographic coordinates and device models for informed decision-making.
Typical use cases include forensic investigations, validating the authenticity of digital content, and conducting audits of multimedia files to ensure compliance and accuracy.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
1,075ms
Service Level:
100%
Response Time:
462ms
Service Level:
100%
Response Time:
1,007ms
Service Level:
100%
Response Time:
343ms
Service Level:
100%
Response Time:
1,812ms
Service Level:
95%
Response Time:
3,625ms
Service Level:
100%
Response Time:
3,168ms
Service Level:
100%
Response Time:
1,945ms
Service Level:
100%
Response Time:
679ms
Service Level:
100%
Response Time:
3,435ms
Service Level:
100%
Response Time:
874ms
Service Level:
100%
Response Time:
671ms
Service Level:
100%
Response Time:
4,635ms
Service Level:
100%
Response Time:
1,249ms
Service Level:
100%
Response Time:
2,559ms
Service Level:
100%
Response Time:
3,957ms
Service Level:
100%
Response Time:
2,643ms
Service Level:
100%
Response Time:
1,273ms
Service Level:
100%
Response Time:
751ms
Service Level:
100%
Response Time:
2,602ms