hi, do you have API documentation to Clay?
no table for this one
Hi Ilya, our HTTP API integration could help. Quick video on how HTTP API works: https://www.loom.com/share/114ff06973bd4ed7985b32fa031be867 -Bonus! troubleshooting example of failed body parse issues: https://www.loom.com/share/678e4c40e8c14894a6cd53948176e434
Looks helpful - thank you!
Stefan K. could you please tell me what is your policy on users who want to integrate clay data into their products? I was reading your ToS and the only applicable section seems to be number 6 https://www.clay.com/terms-of-service#section-6 [which, according to my reading - explicitly says that the data you're selling is (almost) never yours but coming from the data providers you're working with -> i.e. I read it is something greenlighting the use of this data]
Hey Ilya! That's correct, we just provide access to many data providers and aggregate them into one place, but in the vast majority of cases, the data depends on what each provider has and not us. You should be able to use it since it's collected via a paid service they offer and thus we offer access to. Quick note though, we don't currently offer a white labeling service, if that also helps approach this
hey there Arturo! It means I'd have to state
my data is coming from Clay/brightdata etc, or does it mean something else?
I don't think it's necessary, but also not a legal expert and can't give proper advice for that. Perhaps, if people do ask about it you can mention it, otherwise it's fine(?)
maybe you guys have a lawyer and/or compliance specialist
so that I can circle-in with them to confirm and expand on this topic?
or maybe there're some cases of other companies using your data to power their product
that I can read about and/or check with
Sure! there are some users doing something similar, but for more detailed compliance info, maybe Matthew Q. could help us with more specific resources around this that would help you.
Hey Boydric - you don’t need to state where the data comes from. The providers we work with are GDPR compliant already