1. Acceptance
Creating an account, or calling the gateway with an API token, constitutes acceptance of these terms. If you are acting for an organisation, you confirm you are authorised to bind it.
2. Your account
One account per user. You are responsible for everything done with your credentials, including your API token — gateway calls are authenticated by token alone, so a leaked token is indistinguishable from you. Rotate it from the console if you suspect exposure. Sharing an account or reselling access without a written agreement is not permitted.
3. Lawful basis for identity queries
This is the central obligation of these terms. Our endpoints return personal data about identifiable individuals held by national registries and institutions. Before you submit an identifier, you must have a lawful basis for querying it under the law applying to that individual — in Mexico the Ley Federal de Protección de Datos Personales en Posesión de los Particulares, in Colombia Ley 1581 de 2012, in Chile the applicable personal-data law — including any consent those laws require. You, not API Pull, make that determination, and you must be able to evidence it. We may require you to demonstrate it and may suspend access if you cannot.
4. Prohibited use
- Querying an individual without a lawful basis, or beyond the purpose you obtained consent for.
- Building a resale database, people-search product, or bulk directory out of query results.
- Using results to harass, stalk, intimidate, or locate an individual against their interest.
- Discriminating on the basis of data returned, where that discrimination is unlawful.
- Automated enumeration — iterating identifier ranges to harvest records rather than verifying a specific subject you have a relationship with.
- Circumventing rate limits, metering, or billing; sharing tokens across organisations.
- Reproducing our documentation or site content as your own.
5. Credits and billing
The gateway is prepaid and metered per call. Each endpoint has its own unit price, shown on its detail page. A call is authorised only if your balance covers it; when it does not, the gateway returns HTTP 402 and the call is not made. Balance is consumed at the time of the call, including for calls that return no matching record, unless the endpoint's own free-allowance setting covers that case. Enterprise arrangements, custom limits, and any service-level commitment exist only where a separate signed agreement says so — nothing on the pricing page creates one by itself.
6. Availability
The service is provided as-is, without an uptime commitment. Response time depends heavily on the upstream institution: across all production calls to date the mean response time is about 10.0 seconds, and individual endpoints are materially slower than that. Plan for timeouts, treat HTTP 504 as expected rather than exceptional, and do not put a synchronous call to us on a path where a user is waiting without a fallback.
7. Accuracy and permitted reliance
We pass through what the upstream source returns. We do not warrant that a record is accurate, current, or complete, and an empty result is not proof that a person or record does not exist — it may equally mean the upstream source was unavailable or holds the record under different identifiers. Across production calls to date 74.9% returned a substantive business result. Accordingly, you must not use a result from our API as the sole basis for a decision that adversely affects an individual, such as denying credit, employment, housing, or a benefit. Corroborate, and give the individual a route to contest.
8. Intellectual property
The site, documentation, and client code are ours. The data returned by an endpoint is not ours — it originates with the issuing institution and your rights to it derive from your lawful basis for the query, not from these terms.
9. Suspension and termination
We may suspend or close an account for breach of section 3 or 4, for non-payment, or where continued access would expose us or a data subject to legal risk. You may close your account at any time. Remaining prepaid balance on voluntary closure is handled case by case through the contact channels below. Sections 7, 8, and 10 survive termination.
10. Limitation of liability
To the extent permitted by applicable law, we are not liable for indirect or consequential loss, for lost profits, or for decisions you made on the basis of an API result. Our aggregate liability is limited to the amount you paid us in the three months preceding the claim. Nothing here limits liability that cannot lawfully be limited.
11. Governing law and disputes Pending confirmation
Governing law and the forum for disputes follow the registered entity, which is pending confirmation. Until it is published, no choice of law or forum is asserted here, and any mandatory protections available to you under your own local law continue to apply.
12. Changes
We will update the “Last updated” date when these terms change. Continued use after a change means acceptance; if a change is unacceptable, stop calling the gateway and close your account.
Registered entity Pending confirmation
The registration details for the entity operating API Pull have not been published yet. Rather than print a placeholder here, we are leaving the table empty and keeping this page out of search indexing until the details are confirmed. Until then, the contact channels below are the authoritative way to reach a responsible party.
How to reach us
Questions about this document, requests about your own data, and requests about a record returned by one of our endpoints all go to the same two channels. Written requests by email are preferred because they leave a record on both sides.
- partner@apipull.com
- Telegram
- https://t.me/Api_pull