API & Developer Terms
AntiqList – API & Developer Terms
Last Updated: 07 September 2026
Version: 1
Legal Name: AntiqList
Address: Yenişafak Mah. Merkezefendi Denizli / Türkiye
Email: [email protected]
Website: https://www.antiqlist.com/
1. Purpose
These API & Developer Terms govern access to and use of application programming interfaces ("APIs"), developer tools, feeds, integrations, software development resources, and other technical interfaces made available by AntiqList.
These Terms are intended to establish rules for responsible, secure, lawful, and reliable use of AntiqList's technical infrastructure.
2. Scope
These Terms apply to any person, business, organization, developer, application, service, script, integration, or other technical system that accesses or interacts with an AntiqList API or developer service.
3. Acceptance of These Terms
By accessing or using an AntiqList API or developer service, you agree to comply with these Terms and all other applicable AntiqList policies.
If you do not agree with these Terms, you must not access or use the applicable API or developer service.
4. Definitions
For purposes of these Terms:
"API" means an application programming interface made available by AntiqList.
"Developer" means a person or entity accessing or using an AntiqList API or developer service.
"Application" means software, websites, mobile applications, scripts, bots, services, or other systems using an AntiqList API.
"API Credentials" means API keys, tokens, secrets, client identifiers, access credentials, or similar authentication mechanisms.
"API Data" means information returned, transmitted, or made accessible through an AntiqList API.
5. AntiqList's Role
AntiqList may provide APIs and developer services to enable approved technical integrations with portions of the AntiqList platform.
Access to an API does not create a partnership, agency relationship, employment relationship, franchise, or other business relationship unless expressly agreed in writing.
6. API Availability
AntiqList may make APIs available on a permanent, temporary, limited, experimental, beta, or invitation-only basis.
AntiqList does not guarantee that any particular API will remain available indefinitely.
7. API Documentation
Where documentation is provided, developers must follow the applicable technical documentation, authentication requirements, endpoint rules, parameter requirements, data formats, and usage limitations.
Documentation may be updated from time to time.
8. Developer Account
Certain APIs may require a registered AntiqList account or separate developer account.
Developers are responsible for maintaining accurate account information and keeping their accounts secure.
9. API Credentials
API credentials must be treated as confidential.
Developers must not:
publicly expose API keys;
publish credentials in source-code repositories;
share private credentials with unauthorized persons;
embed confidential credentials in publicly accessible client-side applications where doing so creates a security risk; or
use another person's credentials without authorization.
10. Credential Security
Developers are responsible for implementing reasonable security controls for API credentials.
If credentials are compromised, lost, exposed, or suspected of unauthorized use, the developer should promptly notify AntiqList and rotate or revoke the affected credentials where possible.
11. Authentication
Developers must use the authentication methods specified by AntiqList.
Attempts to bypass, disable, manipulate, or circumvent authentication mechanisms are prohibited.
12. Authorization
API access is limited to the permissions expressly granted to the relevant application, account, credential, or developer.
A developer must not attempt to access information or functionality outside its authorized scope.
13. Rate Limits
AntiqList may impose rate limits, quotas, concurrency limits, request limits, bandwidth limits, or other technical restrictions.
Developers must design applications to operate within applicable limits.
14. Rate Limit Circumvention
Developers must not circumvent rate limits by using:
unauthorized API keys;
multiple accounts;
distributed requests;
rotating identities;
proxy networks;
automated credential generation; or
other mechanisms intended to avoid technical restrictions.
15. Excessive Requests
Requests that place unreasonable or harmful loads on AntiqList infrastructure may be restricted or blocked.
AntiqList may take immediate technical measures where necessary to protect platform stability and security.
16. Automated Access
Automated access is permitted only through APIs or other interfaces expressly authorized by AntiqList.
Developers must not use unauthorized scraping, crawling, reverse engineering, browser automation, or similar techniques to bypass API restrictions.
17. Web Scraping
Unless expressly authorized in writing, developers must not use automated systems to scrape, harvest, copy, systematically collect, or reproduce AntiqList data through website interfaces as a substitute for an available API.
18. Data Access
API access may provide only the data necessary for the approved functionality.
AntiqList may restrict or modify the categories of information available through an API.
19. Personal Information
Developers must handle personal information obtained through an AntiqList API in accordance with applicable privacy and data protection laws.
Developers must not collect, use, retain, disclose, sell, or otherwise process personal information for purposes that are not authorized or legally permitted.
20. Data Minimization
Developers should access and retain only the information reasonably necessary for the approved purpose of their application.
Unnecessary personal information should not be collected or retained.
21. User Consent
Where applicable law requires user consent for data access, communications, marketing, tracking, profiling, or other processing, developers are responsible for obtaining and maintaining appropriate consent.
22. User Privacy
Developers must provide appropriate privacy information to their users where required by applicable law.
A developer must not represent that AntiqList has approved its privacy practices unless AntiqList has expressly provided such approval.
23. API Data Ownership
Access to API Data does not automatically transfer ownership or intellectual property rights in that data to the developer.
The rights applicable to API Data depend on the nature of the information, applicable law, and the rights of AntiqList, users, sellers, buyers, and other third parties.
24. User-Generated Content
API Data may include user-generated content such as:
listing descriptions;
photographs;
reviews;
seller information;
comments;
marketplace information; and
other user-submitted materials.
Developers must respect applicable rights in such content.
25. Copyright
Developers must not reproduce, distribute, modify, publicly display, or commercially exploit copyrighted materials obtained through an API except where authorized by AntiqList, the relevant rights holder, or applicable law.
26. Trademarks
The AntiqList name, logo, trademarks, service marks, branding, and related materials may not be used in a manner that falsely suggests sponsorship, endorsement, affiliation, or ownership.
27. API Data Accuracy
API data may change, become unavailable, or contain inaccuracies.
Developers are responsible for appropriately handling incomplete, outdated, or changed API data.
28. Listing Information
Where APIs provide marketplace listing information, developers must not alter or present that information in a misleading manner.
Developers should preserve material context relating to listings where necessary to avoid misleading users.
29. Authenticity and Provenance Information
API access does not constitute authentication or verification of antiques, collectibles, artworks, provenance, ownership, historical claims, certificates, or other listing information.
Developers must not represent API data as an independent authenticity certification unless such certification has been expressly provided by an authorized party.
30. Pricing Information
Prices obtained through an API may change.
Developers should not represent API-provided pricing as guaranteed unless expressly indicated by AntiqList.
31. Search and Ranking Data
API results may be affected by search algorithms, ranking systems, availability, location, personalization, moderation, and other factors.
Developers must not represent API results as permanent rankings or endorsements unless expressly authorized.
32. Attribution
Where AntiqList requires attribution for particular API data or services, developers must display the required attribution accurately and in the specified manner.
33. AntiqList Branding
Developers may be required to comply with AntiqList branding guidelines when displaying AntiqList content or identifying AntiqList as a data or service provider.
34. No False Endorsement
Developers must not claim or imply that:
AntiqList endorses their application;
AntiqList certifies their services;
AntiqList guarantees their transactions;
AntiqList recommends their business; or
their application is officially affiliated with AntiqList,
unless expressly authorized.
35. Third-Party Applications
Applications using AntiqList APIs may integrate with third-party services.
Developers are responsible for ensuring that their third-party integrations comply with applicable laws and contractual obligations.
36. Third-Party API Use
Developers must not use AntiqList APIs to facilitate unauthorized access to third-party services, violate third-party terms, or circumvent third-party security controls.
37. Prohibited Uses
Developers must not use AntiqList APIs for:
fraud;
scams;
phishing;
malware;
unauthorized surveillance;
credential theft;
spam;
harassment;
illegal transactions;
prohibited goods;
counterfeit goods;
stolen property;
unauthorized scraping;
security attacks;
circumvention of platform restrictions; or
other unlawful or abusive activities.
38. High-Risk Applications
AntiqList may restrict API access for applications involving particularly sensitive, high-risk, high-volume, financial, identity-related, or security-sensitive activities.
Additional review or requirements may apply.
39. Payments
API access does not automatically authorize developers to process payments on behalf of AntiqList.
Any payment-related integration must comply with applicable payment requirements and any specific authorization provided by AntiqList.
40. Financial Services
Developers must not represent AntiqList API access as authorization to provide financial, investment, escrow, lending, payment, or other regulated financial services.
41. Marketplace Transactions
Unless expressly authorized, developers must not represent themselves as AntiqList or as an authorized transaction intermediary.
The use of API data does not alter the contractual relationship between buyers and sellers.
42. Off-Platform Transactions
Developers must not use AntiqList API access primarily to facilitate prohibited off-platform transactions, circumvent marketplace fees, bypass safety measures, or avoid applicable AntiqList policies.
43. Circumvention
Developers must not use API access to circumvent:
account restrictions;
listing restrictions;
moderation decisions;
payment controls;
verification requirements;
rate limits;
geographic restrictions;
security measures; or
other platform controls.
44. Security Testing
Security testing against AntiqList systems is prohibited unless expressly authorized.
Developers must not conduct unauthorized:
penetration testing;
vulnerability scanning;
denial-of-service testing;
credential testing;
exploitation attempts; or
other security assessments.
45. Vulnerability Reporting
Security vulnerabilities discovered in connection with an authorized integration should be reported responsibly to AntiqList at:
[email protected]
Developers should avoid unnecessary access, disclosure, modification, or destruction of data while investigating a potential vulnerability.
46. Malicious Code
Applications must not introduce malware, ransomware, spyware, viruses, destructive code, unauthorized tracking mechanisms, or other malicious functionality through an AntiqList integration.
47. Bots and Automated Agents
Bots may be used only where expressly permitted by the applicable API or developer documentation.
Automated agents must comply with rate limits, security requirements, privacy obligations, and all applicable AntiqList policies.
48. Artificial Engagement
Developers must not use APIs to create or facilitate:
fake reviews;
artificial ratings;
fake views;
artificial favorites;
automated clicks;
fraudulent inquiries;
fake accounts; or
other artificial engagement.
49. Review Manipulation
API access must not be used to manipulate marketplace reviews or ratings.
This includes automatically generating or coordinating misleading positive or negative reviews.
50. Data Resale
Unless expressly authorized, developers must not sell, license, rent, or commercially redistribute AntiqList API Data as a standalone data product.
51. Data Replication
Developers must not create a competing database or substantially reproduce AntiqList's marketplace database using API Data unless expressly authorized.
52. Caching
Developers may cache API responses only to the extent reasonably necessary for permitted functionality and in accordance with applicable API documentation and data protection requirements.
53. Data Deletion
Where API Data is required to be deleted or no longer retained, developers must take reasonable steps to remove the applicable information from their systems, subject to lawful retention obligations.
54. Data Security
Developers must implement reasonable technical and organizational safeguards appropriate to the nature of API Data they process.
55. Security Incidents
Developers should promptly notify AntiqList if they become aware of unauthorized access to AntiqList API Data or credentials that could materially affect AntiqList or its users.
56. Changes to API Data
AntiqList may modify API fields, schemas, endpoints, response formats, identifiers, limits, or functionality.
Developers are responsible for maintaining compatibility with supported versions.
57. API Versioning
Where AntiqList provides versioned APIs, developers should use supported versions and migrate when required.
AntiqList may discontinue older versions subject to applicable notice or technical requirements.
58. Deprecation
AntiqList may deprecate or discontinue API functionality.
Where reasonably practicable, AntiqList may provide information regarding material API changes or deprecations.
59. Experimental and Beta APIs
Experimental or beta APIs may be unstable and may change without the same guarantees applicable to generally available services.
Developers use experimental APIs at their own risk.
60. Service Interruptions
API access may be temporarily unavailable because of:
maintenance;
upgrades;
security incidents;
technical failures;
infrastructure problems;
excessive traffic;
third-party service failures; or
other circumstances beyond AntiqList's reasonable control.
61. No Guaranteed Availability
AntiqList does not guarantee uninterrupted, error-free, or permanently available API access unless expressly agreed otherwise in writing.
62. Developer Responsibility
Developers are responsible for their applications, integrations, infrastructure, users, and use of API Data.
63. Compliance With Laws
Developers must comply with all applicable laws and regulations relating to their applications and use of AntiqList APIs.
This may include requirements relating to:
privacy;
consumer protection;
intellectual property;
taxation;
cybersecurity;
advertising;
communications;
export controls; and
regulated goods or services.
64. International Use
Developers accessing AntiqList APIs from outside Türkiye are responsible for complying with laws applicable to their location and users.
65. Export and Sanctions Compliance
Developers must not use AntiqList APIs to violate applicable export controls, sanctions, trade restrictions, or restrictions concerning prohibited goods or persons.
66. Developer Applications
Developers must ensure that their applications provide users with accurate information about:
the developer's identity;
the application's purpose;
applicable privacy practices;
relevant third-party services; and
the application's relationship with AntiqList.
67. User Support
Unless expressly agreed otherwise, developers are responsible for providing support to users of their own applications.
AntiqList is not automatically responsible for support relating to third-party applications.
68. Developer Content
Developers remain responsible for content, code, services, and functionality they create or distribute through their applications.
69. Intellectual Property in Developer Applications
These Terms do not transfer ownership of a developer's independently created application or intellectual property to AntiqList.
However, the developer must ensure that its application does not infringe the rights of AntiqList or third parties.
70. License to Use AntiqList Materials
Where AntiqList expressly provides API documentation, SDKs, software libraries, logos, or other developer materials for integration purposes, AntiqList grants only the limited rights necessary to use those materials for the authorized integration.
71. No Reverse Engineering
Developers must not reverse engineer, decompile, disassemble, or attempt to derive source code or non-public technical information from AntiqList software, APIs, or systems, except where such restriction is prohibited by mandatory applicable law.
72. Competitive Use
Developers must not use non-public API information or restricted developer resources to build competing services or products unless expressly authorized.
73. Monitoring and Enforcement
AntiqList may monitor API usage for security, reliability, fraud prevention, abuse prevention, compliance, and operational purposes.
74. API Access Restrictions
AntiqList may temporarily restrict, suspend, revoke, or terminate API access where reasonably necessary to:
protect the platform;
protect users;
investigate abuse;
respond to security incidents;
enforce these Terms;
comply with law; or
prevent excessive infrastructure use.
75. Immediate Suspension
AntiqList may immediately suspend API access where continued access presents a significant security, legal, fraud, privacy, or operational risk.
76. Developer Appeal
Where appropriate, a developer may contact AntiqList regarding an API restriction or suspension.
AntiqList may request information necessary to evaluate the matter.
77. No Guarantee of Reinstatement
Submission of an appeal does not guarantee restoration of API access.
AntiqList may consider the nature and severity of the violation, security risks, corrective measures, and other relevant circumstances.
78. Termination by Developer
A developer may stop using an AntiqList API at any time, subject to any contractual obligations that continue after termination.
79. Effect of Termination
Following termination or revocation of API access, the developer must stop using the affected API and any API credentials associated with the terminated access.
80. Retention After Termination
Developers may retain information where legally required, but must otherwise comply with applicable data deletion, privacy, and contractual requirements following termination.
81. Fees
Some APIs or developer services may be free, while others may require payment.
Applicable fees will be communicated through the relevant service, documentation, agreement, or pricing information.
82. Changes to Fees
AntiqList may introduce, modify, or discontinue fees for developer services subject to applicable agreements and legal requirements.
83. No Guarantee of Commercial Results
API access does not guarantee:
sales;
traffic;
revenue;
marketplace visibility;
customer acquisition;
business success; or
any particular commercial outcome.
84. Disclaimer of Warranties
To the maximum extent permitted by applicable law, APIs and developer services are provided on an "as available" and, where applicable, "as is" basis.
AntiqList does not guarantee that APIs will always be uninterrupted, error-free, complete, accurate, or suitable for every particular purpose.
85. Limitation of Liability
To the maximum extent permitted by applicable law, AntiqList will not be responsible for losses arising solely from a developer's unauthorized, unlawful, negligent, or improper use of an API.
Nothing in these Terms excludes or limits liability that cannot lawfully be excluded or limited.
86. Developer Indemnification
To the extent permitted by applicable law, developers may be responsible for claims, losses, damages, liabilities, costs, or expenses arising from their unlawful use of AntiqList APIs, infringement of third-party rights, security failures, or violation of these Terms.
87. Third-Party Claims
Developers are responsible for addressing claims arising from their own applications, services, content, or business operations.
88. Government and Law Enforcement Requests
AntiqList may respond to valid government, regulatory, court, customs, tax, or law enforcement requests concerning API use or API Data in accordance with applicable law.
89. Legal Investigations
AntiqList may preserve or disclose relevant information where legally required or reasonably necessary to investigate fraud, abuse, security incidents, or other unlawful activity.
90. Privacy and Data Protection
Use of AntiqList APIs may involve processing personal information.
Developers must comply with applicable privacy and data protection laws and should review the AntiqList Privacy Policy and Data Retention & Deletion Policy where relevant.
91. Confidential Information
Non-public API documentation, credentials, technical information, security information, and other confidential materials must not be disclosed except where authorized or legally required.
92. No Agency or Partnership
API access does not create an agency, partnership, joint venture, employment, franchise, or representative relationship between AntiqList and the developer.
93. No Endorsement
The availability of an API does not constitute an endorsement, recommendation, certification, or guarantee of a developer or application.
94. Changes to Developer Services
AntiqList may modify, update, restrict, suspend, or discontinue APIs, SDKs, documentation, technical requirements, or developer services.
95. Changes to These Terms
AntiqList may update these Terms from time to time.
The updated version will become effective when published or on another effective date specified by AntiqList.
Continued use of an API after the effective date may constitute acceptance of the updated Terms where permitted by applicable law.
96. Conflict With Other Agreements
If a developer has a separate written agreement with AntiqList governing API access, that agreement may control to the extent of any conflict.
97. Relationship With Other AntiqList Policies
These Terms should be read together with applicable AntiqList policies, including:
Terms of Use;
Privacy Policy;
Cookie Policy;
Marketplace Rules / Listing Policy;
Prohibited & Restricted Items Policy;
Intellectual Property / Copyright Policy;
Notice & Takedown Policy;
Safety & Fraud Prevention Policy;
Account Suspension & Termination Policy;
Data Retention & Deletion Policy; and
other applicable policies.
98. No Waiver of Mandatory Rights
Nothing in these Terms is intended to remove or restrict rights that cannot lawfully be excluded under applicable law.
99. Severability
If any provision of these Terms is determined to be invalid or unenforceable, the remaining provisions will continue to apply to the extent permitted by law.
100. Governing Law and Jurisdiction
These Terms are intended to be interpreted in accordance with applicable laws.
Where legally permissible and subject to mandatory consumer or other applicable rights, disputes concerning these Terms may be subject to the applicable laws and courts having jurisdiction over AntiqList's operations.
101. No Professional Advice
API documentation, technical information, examples, and developer resources do not constitute legal, financial, tax, cybersecurity, or other professional advice.
Developers are responsible for obtaining appropriate professional advice where necessary.
102. Contact
Questions regarding these API & Developer Terms or AntiqList developer services may be submitted to:
AntiqList
Yenişafak Mah. Merkezefendi Denizli / Türkiye
Email: [email protected]
Website: https://www.antiqlist.com/
103. Effective Date
These API & Developer Terms are effective as of 07 September 2026.
Version: 1
Last Updated: 07 September 2026
Version: 1
Legal Name: AntiqList
Address: Yenişafak Mah. Merkezefendi Denizli / Türkiye
Email: [email protected]
Website: https://www.antiqlist.com/
1. Purpose
These API & Developer Terms govern access to and use of application programming interfaces ("APIs"), developer tools, feeds, integrations, software development resources, and other technical interfaces made available by AntiqList.
These Terms are intended to establish rules for responsible, secure, lawful, and reliable use of AntiqList's technical infrastructure.
2. Scope
These Terms apply to any person, business, organization, developer, application, service, script, integration, or other technical system that accesses or interacts with an AntiqList API or developer service.
3. Acceptance of These Terms
By accessing or using an AntiqList API or developer service, you agree to comply with these Terms and all other applicable AntiqList policies.
If you do not agree with these Terms, you must not access or use the applicable API or developer service.
4. Definitions
For purposes of these Terms:
"API" means an application programming interface made available by AntiqList.
"Developer" means a person or entity accessing or using an AntiqList API or developer service.
"Application" means software, websites, mobile applications, scripts, bots, services, or other systems using an AntiqList API.
"API Credentials" means API keys, tokens, secrets, client identifiers, access credentials, or similar authentication mechanisms.
"API Data" means information returned, transmitted, or made accessible through an AntiqList API.
5. AntiqList's Role
AntiqList may provide APIs and developer services to enable approved technical integrations with portions of the AntiqList platform.
Access to an API does not create a partnership, agency relationship, employment relationship, franchise, or other business relationship unless expressly agreed in writing.
6. API Availability
AntiqList may make APIs available on a permanent, temporary, limited, experimental, beta, or invitation-only basis.
AntiqList does not guarantee that any particular API will remain available indefinitely.
7. API Documentation
Where documentation is provided, developers must follow the applicable technical documentation, authentication requirements, endpoint rules, parameter requirements, data formats, and usage limitations.
Documentation may be updated from time to time.
8. Developer Account
Certain APIs may require a registered AntiqList account or separate developer account.
Developers are responsible for maintaining accurate account information and keeping their accounts secure.
9. API Credentials
API credentials must be treated as confidential.
Developers must not:
publicly expose API keys;
publish credentials in source-code repositories;
share private credentials with unauthorized persons;
embed confidential credentials in publicly accessible client-side applications where doing so creates a security risk; or
use another person's credentials without authorization.
10. Credential Security
Developers are responsible for implementing reasonable security controls for API credentials.
If credentials are compromised, lost, exposed, or suspected of unauthorized use, the developer should promptly notify AntiqList and rotate or revoke the affected credentials where possible.
11. Authentication
Developers must use the authentication methods specified by AntiqList.
Attempts to bypass, disable, manipulate, or circumvent authentication mechanisms are prohibited.
12. Authorization
API access is limited to the permissions expressly granted to the relevant application, account, credential, or developer.
A developer must not attempt to access information or functionality outside its authorized scope.
13. Rate Limits
AntiqList may impose rate limits, quotas, concurrency limits, request limits, bandwidth limits, or other technical restrictions.
Developers must design applications to operate within applicable limits.
14. Rate Limit Circumvention
Developers must not circumvent rate limits by using:
unauthorized API keys;
multiple accounts;
distributed requests;
rotating identities;
proxy networks;
automated credential generation; or
other mechanisms intended to avoid technical restrictions.
15. Excessive Requests
Requests that place unreasonable or harmful loads on AntiqList infrastructure may be restricted or blocked.
AntiqList may take immediate technical measures where necessary to protect platform stability and security.
16. Automated Access
Automated access is permitted only through APIs or other interfaces expressly authorized by AntiqList.
Developers must not use unauthorized scraping, crawling, reverse engineering, browser automation, or similar techniques to bypass API restrictions.
17. Web Scraping
Unless expressly authorized in writing, developers must not use automated systems to scrape, harvest, copy, systematically collect, or reproduce AntiqList data through website interfaces as a substitute for an available API.
18. Data Access
API access may provide only the data necessary for the approved functionality.
AntiqList may restrict or modify the categories of information available through an API.
19. Personal Information
Developers must handle personal information obtained through an AntiqList API in accordance with applicable privacy and data protection laws.
Developers must not collect, use, retain, disclose, sell, or otherwise process personal information for purposes that are not authorized or legally permitted.
20. Data Minimization
Developers should access and retain only the information reasonably necessary for the approved purpose of their application.
Unnecessary personal information should not be collected or retained.
21. User Consent
Where applicable law requires user consent for data access, communications, marketing, tracking, profiling, or other processing, developers are responsible for obtaining and maintaining appropriate consent.
22. User Privacy
Developers must provide appropriate privacy information to their users where required by applicable law.
A developer must not represent that AntiqList has approved its privacy practices unless AntiqList has expressly provided such approval.
23. API Data Ownership
Access to API Data does not automatically transfer ownership or intellectual property rights in that data to the developer.
The rights applicable to API Data depend on the nature of the information, applicable law, and the rights of AntiqList, users, sellers, buyers, and other third parties.
24. User-Generated Content
API Data may include user-generated content such as:
listing descriptions;
photographs;
reviews;
seller information;
comments;
marketplace information; and
other user-submitted materials.
Developers must respect applicable rights in such content.
25. Copyright
Developers must not reproduce, distribute, modify, publicly display, or commercially exploit copyrighted materials obtained through an API except where authorized by AntiqList, the relevant rights holder, or applicable law.
26. Trademarks
The AntiqList name, logo, trademarks, service marks, branding, and related materials may not be used in a manner that falsely suggests sponsorship, endorsement, affiliation, or ownership.
27. API Data Accuracy
API data may change, become unavailable, or contain inaccuracies.
Developers are responsible for appropriately handling incomplete, outdated, or changed API data.
28. Listing Information
Where APIs provide marketplace listing information, developers must not alter or present that information in a misleading manner.
Developers should preserve material context relating to listings where necessary to avoid misleading users.
29. Authenticity and Provenance Information
API access does not constitute authentication or verification of antiques, collectibles, artworks, provenance, ownership, historical claims, certificates, or other listing information.
Developers must not represent API data as an independent authenticity certification unless such certification has been expressly provided by an authorized party.
30. Pricing Information
Prices obtained through an API may change.
Developers should not represent API-provided pricing as guaranteed unless expressly indicated by AntiqList.
31. Search and Ranking Data
API results may be affected by search algorithms, ranking systems, availability, location, personalization, moderation, and other factors.
Developers must not represent API results as permanent rankings or endorsements unless expressly authorized.
32. Attribution
Where AntiqList requires attribution for particular API data or services, developers must display the required attribution accurately and in the specified manner.
33. AntiqList Branding
Developers may be required to comply with AntiqList branding guidelines when displaying AntiqList content or identifying AntiqList as a data or service provider.
34. No False Endorsement
Developers must not claim or imply that:
AntiqList endorses their application;
AntiqList certifies their services;
AntiqList guarantees their transactions;
AntiqList recommends their business; or
their application is officially affiliated with AntiqList,
unless expressly authorized.
35. Third-Party Applications
Applications using AntiqList APIs may integrate with third-party services.
Developers are responsible for ensuring that their third-party integrations comply with applicable laws and contractual obligations.
36. Third-Party API Use
Developers must not use AntiqList APIs to facilitate unauthorized access to third-party services, violate third-party terms, or circumvent third-party security controls.
37. Prohibited Uses
Developers must not use AntiqList APIs for:
fraud;
scams;
phishing;
malware;
unauthorized surveillance;
credential theft;
spam;
harassment;
illegal transactions;
prohibited goods;
counterfeit goods;
stolen property;
unauthorized scraping;
security attacks;
circumvention of platform restrictions; or
other unlawful or abusive activities.
38. High-Risk Applications
AntiqList may restrict API access for applications involving particularly sensitive, high-risk, high-volume, financial, identity-related, or security-sensitive activities.
Additional review or requirements may apply.
39. Payments
API access does not automatically authorize developers to process payments on behalf of AntiqList.
Any payment-related integration must comply with applicable payment requirements and any specific authorization provided by AntiqList.
40. Financial Services
Developers must not represent AntiqList API access as authorization to provide financial, investment, escrow, lending, payment, or other regulated financial services.
41. Marketplace Transactions
Unless expressly authorized, developers must not represent themselves as AntiqList or as an authorized transaction intermediary.
The use of API data does not alter the contractual relationship between buyers and sellers.
42. Off-Platform Transactions
Developers must not use AntiqList API access primarily to facilitate prohibited off-platform transactions, circumvent marketplace fees, bypass safety measures, or avoid applicable AntiqList policies.
43. Circumvention
Developers must not use API access to circumvent:
account restrictions;
listing restrictions;
moderation decisions;
payment controls;
verification requirements;
rate limits;
geographic restrictions;
security measures; or
other platform controls.
44. Security Testing
Security testing against AntiqList systems is prohibited unless expressly authorized.
Developers must not conduct unauthorized:
penetration testing;
vulnerability scanning;
denial-of-service testing;
credential testing;
exploitation attempts; or
other security assessments.
45. Vulnerability Reporting
Security vulnerabilities discovered in connection with an authorized integration should be reported responsibly to AntiqList at:
[email protected]
Developers should avoid unnecessary access, disclosure, modification, or destruction of data while investigating a potential vulnerability.
46. Malicious Code
Applications must not introduce malware, ransomware, spyware, viruses, destructive code, unauthorized tracking mechanisms, or other malicious functionality through an AntiqList integration.
47. Bots and Automated Agents
Bots may be used only where expressly permitted by the applicable API or developer documentation.
Automated agents must comply with rate limits, security requirements, privacy obligations, and all applicable AntiqList policies.
48. Artificial Engagement
Developers must not use APIs to create or facilitate:
fake reviews;
artificial ratings;
fake views;
artificial favorites;
automated clicks;
fraudulent inquiries;
fake accounts; or
other artificial engagement.
49. Review Manipulation
API access must not be used to manipulate marketplace reviews or ratings.
This includes automatically generating or coordinating misleading positive or negative reviews.
50. Data Resale
Unless expressly authorized, developers must not sell, license, rent, or commercially redistribute AntiqList API Data as a standalone data product.
51. Data Replication
Developers must not create a competing database or substantially reproduce AntiqList's marketplace database using API Data unless expressly authorized.
52. Caching
Developers may cache API responses only to the extent reasonably necessary for permitted functionality and in accordance with applicable API documentation and data protection requirements.
53. Data Deletion
Where API Data is required to be deleted or no longer retained, developers must take reasonable steps to remove the applicable information from their systems, subject to lawful retention obligations.
54. Data Security
Developers must implement reasonable technical and organizational safeguards appropriate to the nature of API Data they process.
55. Security Incidents
Developers should promptly notify AntiqList if they become aware of unauthorized access to AntiqList API Data or credentials that could materially affect AntiqList or its users.
56. Changes to API Data
AntiqList may modify API fields, schemas, endpoints, response formats, identifiers, limits, or functionality.
Developers are responsible for maintaining compatibility with supported versions.
57. API Versioning
Where AntiqList provides versioned APIs, developers should use supported versions and migrate when required.
AntiqList may discontinue older versions subject to applicable notice or technical requirements.
58. Deprecation
AntiqList may deprecate or discontinue API functionality.
Where reasonably practicable, AntiqList may provide information regarding material API changes or deprecations.
59. Experimental and Beta APIs
Experimental or beta APIs may be unstable and may change without the same guarantees applicable to generally available services.
Developers use experimental APIs at their own risk.
60. Service Interruptions
API access may be temporarily unavailable because of:
maintenance;
upgrades;
security incidents;
technical failures;
infrastructure problems;
excessive traffic;
third-party service failures; or
other circumstances beyond AntiqList's reasonable control.
61. No Guaranteed Availability
AntiqList does not guarantee uninterrupted, error-free, or permanently available API access unless expressly agreed otherwise in writing.
62. Developer Responsibility
Developers are responsible for their applications, integrations, infrastructure, users, and use of API Data.
63. Compliance With Laws
Developers must comply with all applicable laws and regulations relating to their applications and use of AntiqList APIs.
This may include requirements relating to:
privacy;
consumer protection;
intellectual property;
taxation;
cybersecurity;
advertising;
communications;
export controls; and
regulated goods or services.
64. International Use
Developers accessing AntiqList APIs from outside Türkiye are responsible for complying with laws applicable to their location and users.
65. Export and Sanctions Compliance
Developers must not use AntiqList APIs to violate applicable export controls, sanctions, trade restrictions, or restrictions concerning prohibited goods or persons.
66. Developer Applications
Developers must ensure that their applications provide users with accurate information about:
the developer's identity;
the application's purpose;
applicable privacy practices;
relevant third-party services; and
the application's relationship with AntiqList.
67. User Support
Unless expressly agreed otherwise, developers are responsible for providing support to users of their own applications.
AntiqList is not automatically responsible for support relating to third-party applications.
68. Developer Content
Developers remain responsible for content, code, services, and functionality they create or distribute through their applications.
69. Intellectual Property in Developer Applications
These Terms do not transfer ownership of a developer's independently created application or intellectual property to AntiqList.
However, the developer must ensure that its application does not infringe the rights of AntiqList or third parties.
70. License to Use AntiqList Materials
Where AntiqList expressly provides API documentation, SDKs, software libraries, logos, or other developer materials for integration purposes, AntiqList grants only the limited rights necessary to use those materials for the authorized integration.
71. No Reverse Engineering
Developers must not reverse engineer, decompile, disassemble, or attempt to derive source code or non-public technical information from AntiqList software, APIs, or systems, except where such restriction is prohibited by mandatory applicable law.
72. Competitive Use
Developers must not use non-public API information or restricted developer resources to build competing services or products unless expressly authorized.
73. Monitoring and Enforcement
AntiqList may monitor API usage for security, reliability, fraud prevention, abuse prevention, compliance, and operational purposes.
74. API Access Restrictions
AntiqList may temporarily restrict, suspend, revoke, or terminate API access where reasonably necessary to:
protect the platform;
protect users;
investigate abuse;
respond to security incidents;
enforce these Terms;
comply with law; or
prevent excessive infrastructure use.
75. Immediate Suspension
AntiqList may immediately suspend API access where continued access presents a significant security, legal, fraud, privacy, or operational risk.
76. Developer Appeal
Where appropriate, a developer may contact AntiqList regarding an API restriction or suspension.
AntiqList may request information necessary to evaluate the matter.
77. No Guarantee of Reinstatement
Submission of an appeal does not guarantee restoration of API access.
AntiqList may consider the nature and severity of the violation, security risks, corrective measures, and other relevant circumstances.
78. Termination by Developer
A developer may stop using an AntiqList API at any time, subject to any contractual obligations that continue after termination.
79. Effect of Termination
Following termination or revocation of API access, the developer must stop using the affected API and any API credentials associated with the terminated access.
80. Retention After Termination
Developers may retain information where legally required, but must otherwise comply with applicable data deletion, privacy, and contractual requirements following termination.
81. Fees
Some APIs or developer services may be free, while others may require payment.
Applicable fees will be communicated through the relevant service, documentation, agreement, or pricing information.
82. Changes to Fees
AntiqList may introduce, modify, or discontinue fees for developer services subject to applicable agreements and legal requirements.
83. No Guarantee of Commercial Results
API access does not guarantee:
sales;
traffic;
revenue;
marketplace visibility;
customer acquisition;
business success; or
any particular commercial outcome.
84. Disclaimer of Warranties
To the maximum extent permitted by applicable law, APIs and developer services are provided on an "as available" and, where applicable, "as is" basis.
AntiqList does not guarantee that APIs will always be uninterrupted, error-free, complete, accurate, or suitable for every particular purpose.
85. Limitation of Liability
To the maximum extent permitted by applicable law, AntiqList will not be responsible for losses arising solely from a developer's unauthorized, unlawful, negligent, or improper use of an API.
Nothing in these Terms excludes or limits liability that cannot lawfully be excluded or limited.
86. Developer Indemnification
To the extent permitted by applicable law, developers may be responsible for claims, losses, damages, liabilities, costs, or expenses arising from their unlawful use of AntiqList APIs, infringement of third-party rights, security failures, or violation of these Terms.
87. Third-Party Claims
Developers are responsible for addressing claims arising from their own applications, services, content, or business operations.
88. Government and Law Enforcement Requests
AntiqList may respond to valid government, regulatory, court, customs, tax, or law enforcement requests concerning API use or API Data in accordance with applicable law.
89. Legal Investigations
AntiqList may preserve or disclose relevant information where legally required or reasonably necessary to investigate fraud, abuse, security incidents, or other unlawful activity.
90. Privacy and Data Protection
Use of AntiqList APIs may involve processing personal information.
Developers must comply with applicable privacy and data protection laws and should review the AntiqList Privacy Policy and Data Retention & Deletion Policy where relevant.
91. Confidential Information
Non-public API documentation, credentials, technical information, security information, and other confidential materials must not be disclosed except where authorized or legally required.
92. No Agency or Partnership
API access does not create an agency, partnership, joint venture, employment, franchise, or representative relationship between AntiqList and the developer.
93. No Endorsement
The availability of an API does not constitute an endorsement, recommendation, certification, or guarantee of a developer or application.
94. Changes to Developer Services
AntiqList may modify, update, restrict, suspend, or discontinue APIs, SDKs, documentation, technical requirements, or developer services.
95. Changes to These Terms
AntiqList may update these Terms from time to time.
The updated version will become effective when published or on another effective date specified by AntiqList.
Continued use of an API after the effective date may constitute acceptance of the updated Terms where permitted by applicable law.
96. Conflict With Other Agreements
If a developer has a separate written agreement with AntiqList governing API access, that agreement may control to the extent of any conflict.
97. Relationship With Other AntiqList Policies
These Terms should be read together with applicable AntiqList policies, including:
Terms of Use;
Privacy Policy;
Cookie Policy;
Marketplace Rules / Listing Policy;
Prohibited & Restricted Items Policy;
Intellectual Property / Copyright Policy;
Notice & Takedown Policy;
Safety & Fraud Prevention Policy;
Account Suspension & Termination Policy;
Data Retention & Deletion Policy; and
other applicable policies.
98. No Waiver of Mandatory Rights
Nothing in these Terms is intended to remove or restrict rights that cannot lawfully be excluded under applicable law.
99. Severability
If any provision of these Terms is determined to be invalid or unenforceable, the remaining provisions will continue to apply to the extent permitted by law.
100. Governing Law and Jurisdiction
These Terms are intended to be interpreted in accordance with applicable laws.
Where legally permissible and subject to mandatory consumer or other applicable rights, disputes concerning these Terms may be subject to the applicable laws and courts having jurisdiction over AntiqList's operations.
101. No Professional Advice
API documentation, technical information, examples, and developer resources do not constitute legal, financial, tax, cybersecurity, or other professional advice.
Developers are responsible for obtaining appropriate professional advice where necessary.
102. Contact
Questions regarding these API & Developer Terms or AntiqList developer services may be submitted to:
AntiqList
Yenişafak Mah. Merkezefendi Denizli / Türkiye
Email: [email protected]
Website: https://www.antiqlist.com/
103. Effective Date
These API & Developer Terms are effective as of 07 September 2026.
Version: 1