REQeV Developer and API Terms

These Developer and API Terms (“Developer Terms”) govern your access to and use of the application programming interfaces, software development kits, sample code, documentation, API credentials and developer sandbox made available by ECDG, Inc., a California corporation, doing business as REQeV (“REQeV”, “we”, “us” or “our”).

Please read these Developer Terms carefully. They include a disclaimer of warranties, a limitation of liability and an indemnity from you.

1. Acceptance and Relationship to Other Agreements

You accept these Developer Terms when you click to accept them, create a developer account, request or use API Credentials, or otherwise access the Developer Tools. If you accept on behalf of a company or other organization, you represent that you have authority to bind it, and “you” means that organization.

These Developer Terms supplement the agreement that governs your organization’s use of the Services. That is the Master Subscription Agreement or another signed agreement with REQeV, or, if neither applies, the Terms of Service (each, your “Agreement”). The Acceptable Use Policy also applies to all use of the Developer Tools.

If you are a paying REQeV customer and these Developer Terms conflict with your Agreement or the Data Processing Addendum, your Agreement and the Data Processing Addendum control. Otherwise, these Developer Terms control on the subject of the Developer Tools. A signed agreement with REQeV that expressly overrides these Developer Terms controls over them. Nothing in these Developer Terms reduces REQeV’s commitments to its customers about Customer Data under their Agreements or the Data Processing Addendum.

2. Definitions

• “API” means any REQeV application programming interface, webhook or related endpoint made available to you.
• “API Credentials” means API keys, client IDs, client secrets, access tokens, OAuth credentials, webhook signing secrets and any other credential REQeV issues for access to the APIs.
• “Application” means any software, integration, script, service or tool that you build or operate and that accesses the APIs or uses the SDKs.
• “Beta Features” has the meaning given in Section 12.
• “Customer” means a REQeV customer whose account or Customer Data your Application accesses, which may be you or a third party.
• “Customer Data” has the meaning given in the applicable Agreement and includes candidate and contact personal information stored in the Services.
• “Developer Tools” means the APIs, SDKs, Documentation, API Credentials, Sandbox and any related tools or materials REQeV provides to developers.
• “Documentation” means REQeV’s then-current developer documentation, API reference, changelog and usage guides.
• “End User” means any individual who uses, or whose information is processed by, your Application.
• “Sandbox” means any non-production test environment, test tenant or test account REQeV provides for development and testing.
• “SDK” means any software development kit, client library or sample code REQeV provides.
• “Services” means REQeV ATS, REQeV Sourcing, REQeV Mission Control and related APIs, integrations, browser extensions and AI features.

3. Eligibility and Developer Accounts

You must be at least 18 years old and able to form a binding contract to use the Developer Tools. You may not use the Developer Tools if you are located in, or organized under the laws of, a country or region subject to comprehensive U.S. sanctions, or if you are named on a U.S. government restricted-party list.

You must provide accurate registration information and keep it current. You are responsible for all activity under your developer account, including activity by your employees and contractors, and for making sure they comply with these Developer Terms.

REQeV may approve or decline any developer account or access request at its discretion. Access to some APIs may require an active paid subscription, a separate approval or additional terms that REQeV presents to you.

4. API Credentials

API Credentials are REQeV’s Confidential Information and are issued for your use only. You must keep them secure. You must not share, sell or publish them, or embed them in client-side code, public repositories, mobile applications or any other place where third parties can access them.

You are responsible for all API calls and other activity made with your API Credentials, whether or not you authorized that activity. You must use API Credentials only for the Application and environment for which they were issued. Sandbox credentials must not be used in production, and production credentials must not be used in the Sandbox.

You must rotate API Credentials promptly if you suspect they have been exposed, when personnel with access to them leave your organization, and whenever REQeV asks you to. REQeV may revoke, rotate or expire API Credentials at any time to protect the Services, Customers or End Users.

Where REQeV signs webhooks or other requests, for example with an HMAC signature, you must verify the signature before trusting or acting on the payload. If you learn or suspect that API Credentials have been compromised, you must revoke them and notify support@reqev.com without undue delay.

5. License Grant

Subject to your compliance with these Developer Terms and your Agreement, REQeV grants you a limited, non-exclusive, non-transferable, non-sublicensable and revocable license, during the term of these Developer Terms, to:

1. use the Documentation to develop, test and support your Application;
2. access and use the APIs, with your API Credentials, to make your Application interoperate with the Services; and
3. use, reproduce and distribute the SDKs, in object code form, solely as incorporated into your Application.

Some SDKs or sample code may be provided under an open-source license. For those components, the open-source license governs to the extent it grants you broader rights than these Developer Terms.

6. License Restrictions

Except as these Developer Terms expressly permit, you must not:

• copy, modify or create derivative works of the Developer Tools, other than SDK sample code as its license permits;
• sublicense, sell, rent, lease or otherwise transfer access to the Developer Tools or your API Credentials;
• access the APIs by any means other than those described in the Documentation;
• remove or obscure any proprietary notices in the Developer Tools;
• use the Developer Tools in a way that violates applicable law, your Agreement or the rights of any third party; or
• use the Developer Tools to access any Customer’s account or Customer Data without that Customer’s authorization.

7. Developer Sandbox

REQeV may provide a Sandbox so you can build and test your Application. The Sandbox is provided for development, testing and demonstration purposes only.

Test data only

You must use only fictitious or synthetic data in the Sandbox. You must not upload, import or process real personal information in the Sandbox, including real candidate, contact, employee or customer information. You must not use the Sandbox for production workloads or live recruiting activity.

If real personal information is placed in the Sandbox in breach of this section, you are responsible for it and REQeV may delete it without notice. REQeV’s service level and data retention commitments do not apply to the Sandbox.

Resets and deletion

REQeV may reset, refresh, modify or delete the Sandbox, and any data, configurations, Applications or content in it, at any time and without notice. REQeV does not back up Sandbox data, so you should keep your own copies of anything you need.

Usage limits, availability and suspension

The Sandbox is subject to usage limits, including limits on API calls, records, storage, users and AI feature usage. Those limits may be lower than production limits and may change at any time.

The Sandbox is not covered by the Service Level Agreement or any other uptime or support commitment. REQeV provides Sandbox support, if any, on a commercially reasonable efforts basis.

REQeV may suspend, limit or discontinue the Sandbox, or your access to it, at any time. Reasons may include inactivity, excessive usage, suspected misuse or changes to the Developer Tools.

8. Rate Limits and Fair Use

REQeV sets rate limits, quotas and other usage limits for the APIs, which are described in the Documentation or otherwise communicated to you. Limits may vary by API, endpoint, plan and environment. REQeV may change them to protect the stability, security and performance of the Services.

You must stay within the applicable limits and must not attempt to exceed or circumvent them, including by using multiple accounts or API Credentials. You should design your Application to handle rate-limit responses gracefully, for example by backing off and retrying.

If your usage is unusually heavy or degrades the Services for others, REQeV may throttle, queue or suspend your requests. Where practical, REQeV will contact you first to discuss options, such as optimizing your integration or moving to a plan with higher limits.

9. Data Protection and Security

Customer Data

If your Application accesses, stores or otherwise processes Customer Data, you may do so only on the documented instructions and authorization of the relevant Customer. You may use Customer Data only as needed to provide the functionality that Customer has requested. As between you and REQeV, you are solely responsible for your Application’s handling of Customer Data.

You must:

• obtain and maintain every authorization and consent required for your Application to access and process Customer Data;
• publish and follow a privacy notice that accurately describes what data your Application collects, how it is used and shared, and how End Users can exercise their rights;
• implement and maintain appropriate technical and organizational security measures, including encryption in transit, access controls, logging and secure storage of API Credentials;
• collect and keep only the Customer Data needed for your Application’s disclosed purpose;
• delete Customer Data promptly when the Customer asks, when the Customer disconnects your Application or when the data is no longer needed, unless law requires you to keep it;
• not use Customer Data to build or enrich your own databases, profiles, models or products for any purpose outside the Customer’s instructions; and
• comply with all applicable privacy, data protection, consumer protection, employment and anti-discrimination laws.

Data processing terms

Where you are a REQeV customer, the Data Processing Addendum applies to REQeV’s processing of your Customer Data, including through the APIs. If you process personal information on REQeV’s behalf, you must sign and comply with the data processing terms REQeV provides.

If you process Customer Data on behalf of a third-party Customer, you are responsible for entering into any data processing terms that Customer or applicable law requires. REQeV is not a party to those terms.

Security incidents

You must notify REQeV at support@reqev.com without undue delay, and in any event within 72 hours, after becoming aware of any unauthorized access to, or loss, disclosure or alteration of, Customer Data, API Credentials or the Services in connection with your Application. Your notice should describe the incident, the data and Customers affected, and the steps you are taking to contain it.

You must cooperate with REQeV and affected Customers to investigate and remediate the incident and to meet any notification obligations. You must not notify Customers or regulators on REQeV’s behalf, or make public statements naming REQeV in connection with the incident, without REQeV’s prior written consent, unless the law requires you to.

Vulnerabilities

If you discover a security vulnerability in the Services or the Developer Tools, report it to support@reqev.com as described in our Responsible Disclosure Policy. Do not test for vulnerabilities outside the scope of that policy. More information about how REQeV protects the Services is available on our Security page.

10. User-Facing Applications and Branding

If your Application is available to anyone other than your own personnel, you must:

• clearly identify yourself, not REQeV, as the provider of your Application and the party responsible for it;
• give End Users your own support contact details and terms of use;
• accurately describe how your Application interacts with the Services and what data it accesses; and
• not state or imply that REQeV sponsors, endorses, certifies or is affiliated with your Application, unless REQeV has agreed in writing.

You may make factual references to REQeV to explain that your Application works with the Services, such as “works with REQeV”, if you follow any branding guidelines that REQeV publishes or provides to you on request. Otherwise, you may not use REQeV’s names, logos, trademarks or other brand features (“REQeV Marks”) without REQeV’s prior written permission.

You must not use REQeV Marks, or any confusingly similar name, logo or domain, in your Application name, company name, domain name or social media handles. REQeV may review your use of REQeV Marks and may require you to change or stop any use at any time.

With your permission, REQeV may list or describe your Application in its directories or marketing materials and use your name and logo for that purpose.

11. Prohibited Uses

You must not, and must not allow anyone else to, use the Developer Tools to:

• build, train or support a product or service that competes with the Services, or benchmark the Services for competitive purposes without REQeV’s written consent;
• scrape, crawl, harvest or bulk-extract data from the Services, other than Customer Data that a Customer has authorized you to export through documented APIs;
• reverse engineer, decompile, disassemble or attempt to derive the source code, models, algorithms or non-public APIs of the Services, except to the extent applicable law expressly permits despite this restriction;
• circumvent or attempt to circumvent rate limits, usage limits, credit metering, authentication, access controls or other security measures;
• sell, rent, license or otherwise commercialize data obtained through the APIs, including candidate or contact information, or share it with data brokers;
• make, or support, high-risk or consequential decisions about individuals, including employment decisions, without the human review, notices and safeguards required by applicable law and the Acceptable Use Policy;
• send spam or unsolicited communications, or contact candidates or contacts in violation of applicable law or their stated preferences;
• introduce malware, or interfere with or disrupt the integrity or performance of the Services;
• impersonate REQeV, a Customer or any other person, or misrepresent the source of any request;
• access the Services or Customer Data without authorization; or
• engage in any unlawful, harmful, discriminatory or fraudulent activity.

12. Changes, Beta Features and Deprecation

REQeV continually improves the Services and may add, change or remove APIs, endpoints, fields, SDKs and Documentation. Many changes, such as new endpoints or optional fields, are backward-compatible, and you should build your Application to tolerate them.

Breaking changes to generally available APIs

For generally available APIs, REQeV will use reasonable efforts to give reasonable advance notice before making a breaking change or discontinuing the API. A breaking change is one that REQeV reasonably expects to require changes to a correctly built Application, such as removing an endpoint or field or changing authentication methods.

REQeV may give notice through the Documentation, a changelog, email to your developer account or a notice in the Services. REQeV may make breaking changes with shorter notice, or without notice, when needed to address a security risk, a legal or regulatory requirement, a change by a third-party provider or a threat to the stability of the Services.

Beta and preview APIs

APIs, SDKs and features labeled alpha, beta, preview, early access, experimental or similar (“Beta Features”) are provided for evaluation. Beta Features may change, be suspended or be discontinued at any time without notice. They may not be supported and are excluded from any service level or deprecation commitment.

Versioning

Where REQeV versions its APIs, it may retire older versions after the notice period described above. You are responsible for migrating your Application to supported versions.

13. Fees and Credits

Access to the Sandbox and the Documentation is currently free of charge. REQeV may introduce fees for the Developer Tools with advance notice, and you may stop using them if you do not accept those fees.

Production use of the APIs takes place under a Customer’s subscription. It may count toward that Customer’s plan limits or consume prepaid usage credits (“credit packs”), as described in the applicable plan, Order Form or Documentation. For example, API calls that perform sourcing, enrichment or AI actions may consume credits in the same way as the equivalent action in the Services.

The account holder is responsible for all fees, credits and taxes incurred through the APIs under its account, including usage generated by any Application it has connected. Fees are governed by the applicable Agreement.

14. Feedback

If you give REQeV suggestions, ideas, bug reports or other feedback about the Developer Tools or the Services (“Feedback”), REQeV may use it for any purpose without restriction or payment to you. REQeV will not publicly identify you as the source of Feedback without your permission.

15. Confidentiality

Non-public information that REQeV discloses to you through the Developer Tools is REQeV’s “Confidential Information”. This includes API Credentials, non-public Documentation, Beta Features, roadmap information and security information.

You must use Confidential Information only to develop and operate your Application under these Developer Terms and protect it with at least reasonable care. You may disclose it only to your personnel and contractors who need to know it and who are bound by confidentiality obligations at least as protective as these.

These obligations do not apply to information that is or becomes public through no fault of yours, that you already knew without a confidentiality obligation, that you developed independently, or that you rightfully received from a third party without restriction. You may disclose Confidential Information when the law requires it, after giving REQeV reasonable advance notice where legally permitted.

If your Agreement contains confidentiality terms, those terms also apply, and they control if they conflict with this section.

16. Ownership

REQeV and its licensors own all right, title and interest in the Developer Tools, the Services and the REQeV Marks, including all related intellectual property rights. All rights not expressly granted in these Developer Terms are reserved.

As between you and REQeV, you own your Application, excluding the Developer Tools and any other REQeV materials incorporated into it. Customers keep their rights in Customer Data as set out in their Agreements.

17. Monitoring and Audit

REQeV may monitor use of the Developer Tools, including API call volumes, request patterns, errors and request contents. REQeV does this to operate and secure the Services, enforce these Developer Terms, prevent abuse and improve the Developer Tools. You must not interfere with this monitoring.

On REQeV’s reasonable request, you must provide information about your Application and its use of the APIs and Customer Data. This may include a description of its data flows and security practices and a demonstration of the Application.

If REQeV reasonably believes you have breached these Developer Terms, REQeV, or an independent auditor bound by confidentiality, may audit your relevant records and systems. Audits will take place on reasonable notice, during normal business hours and no more than once in any 12-month period, unless a previous audit revealed a material breach.

REQeV may tell affected Customers about your Application’s access to their accounts, including which Customer Data your Application accessed.

18. Suspension and Termination

You may terminate these Developer Terms at any time by revoking your API Credentials and stopping all use of the Developer Tools. A Customer may revoke your Application’s access to its account at any time.

REQeV may suspend or revoke your access to any Developer Tools, or terminate these Developer Terms, at any time. REQeV may do so with or without notice if you breach these Developer Terms or your Agreement, if your Application poses a security, legal or reputational risk, if the law requires it, or if REQeV discontinues the Developer Tools. Where practical and legally permitted, REQeV will give you notice and a chance to fix the problem before suspending your access.

Your access to the Developer Tools also ends automatically when the Agreement under which you access the Services ends. When these Developer Terms end:

• all licenses granted to you end and you must stop using the Developer Tools;
• you must delete your API Credentials, any non-public Documentation and any other REQeV Confidential Information;
• you must delete Customer Data obtained through the APIs, unless the relevant Customer instructs otherwise or the law requires you to keep it; and
• Sections 4, 9, 11 and 14 through 25, and any other terms that by their nature should survive, remain in effect.

19. Disclaimers

THE DEVELOPER TOOLS, INCLUDING THE SANDBOX AND ANY BETA FEATURES, ARE PROVIDED “AS IS” AND “AS AVAILABLE.” TO THE MAXIMUM EXTENT PERMITTED BY LAW, REQeV AND ITS LICENSORS AND SUPPLIERS DISCLAIM ALL WARRANTIES, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.

REQeV does not warrant that the Developer Tools will be uninterrupted, error-free or secure, that they will be compatible with your Application, or that data returned through the APIs will be accurate or complete. You are solely responsible for your Application, including its compliance with law, and for any decisions made using it.

20. Limitation of Liability

For production use of the APIs under a paid subscription, the limitation of liability in your Agreement applies to claims arising from that use.

FOR USE OF THE SANDBOX, BETA FEATURES AND ANY OTHER DEVELOPER TOOLS PROVIDED WITHOUT CHARGE, TO THE MAXIMUM EXTENT PERMITTED BY LAW, REQeV’S TOTAL LIABILITY ARISING OUT OF OR RELATING TO THESE DEVELOPER TERMS WILL NOT EXCEED US $100.

FOR USE OF THE SANDBOX AND OTHER DEVELOPER TOOLS PROVIDED WITHOUT CHARGE, TO THE MAXIMUM EXTENT PERMITTED BY LAW, REQeV WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL OR DATA, ARISING OUT OF OR RELATING TO THE DEVELOPER TOOLS, EVEN IF REQeV HAS BEEN ADVISED OF THE POSSIBILITY OF THOSE DAMAGES.

These limitations apply to all theories of liability, including contract, tort (including negligence) and strict liability. Some jurisdictions do not allow certain limitations, so some of them may not apply to you.

21. Indemnity

You will defend, indemnify and hold harmless REQeV and its affiliates, officers, directors, employees and agents from and against any third-party claim, and all related losses, damages, liabilities, fines, costs and expenses (including reasonable attorneys’ fees), arising out of or relating to your Application, your breach of these Developer Terms, your processing of Customer Data or other personal information, your violation of law or third-party rights, or any security incident affecting your Application or API Credentials.

REQeV will give you prompt notice of the claim, allow you to control its defense and settlement, and provide reasonable cooperation at your expense. You may not settle a claim in a way that imposes any obligation on REQeV or admits fault on its behalf without REQeV’s prior written consent. REQeV may participate in the defense with counsel of its choice at its own expense.

22. Governing Law and Disputes

These Developer Terms are governed by the laws of the State of California, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

The state and federal courts located in San Francisco County, California have exclusive jurisdiction over any dispute arising out of or relating to these Developer Terms, and each party consents to personal jurisdiction there. If your Agreement sets out a different dispute resolution procedure, that procedure also applies to disputes under these Developer Terms.

Either party may seek injunctive or other equitable relief in any court of competent jurisdiction to protect its intellectual property rights or Confidential Information.

23. Changes to These Terms

REQeV may update these Developer Terms from time to time. REQeV will post the updated version on this page with a new effective date.

If a change is material, REQeV will give you reasonable advance notice, for example by email to your developer account or through the Documentation. Your continued use of the Developer Tools after a change takes effect means you accept the updated Developer Terms.

24. General

You must comply with all applicable export control and sanctions laws in connection with the Developer Tools and your Application. You may not assign or transfer these Developer Terms without REQeV’s prior written consent, and any attempt to do so is void. REQeV may assign these Developer Terms in connection with a merger, acquisition or sale of all or substantially all of its relevant assets.

The parties are independent contractors, and these Developer Terms create no agency, partnership or joint venture. There are no third-party beneficiaries of these Developer Terms. Neither party is liable for delays caused by events beyond its reasonable control, other than payment obligations.

If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the rest of these Developer Terms will remain in effect. A failure to enforce a provision is not a waiver. These Developer Terms, together with your Agreement and the documents referenced in them, are the entire agreement between you and REQeV about the Developer Tools.

REQeV may send notices to the email address associated with your developer account. You must send legal notices to support@reqev.com and to the mailing address below. The Developer Tools are commercial computer software, and any U.S. government use is subject to these Developer Terms.

25. Contact

ECDG, Inc., a California corporation, doing business as REQeV, 236 West Portal Ave #390, San Francisco, CA 94127.

• Legal notices: support@reqev.com
• Developer and API support: support@reqev.com
• Security incidents and vulnerability reports: support@reqev.com
• Privacy requests: support@reqev.com