HTTP destination acceptable use

Hello, I was wondering if you could be provided around the terms for sending http requests. The docs say both:

This can be an endpoint you own and operate, or a URL tied to a service you use

and

Do not use Pipedream to send HTTP requests to a service you do not own or operate

Does this mean I can or can’t use it for a third-party service that I don’t own/operate? Does it make any difference what CORS headers are returned by that service?

The reason I ask is that it can be useful to create a workflow that acts as a cors proxy and retrieves some information that I want to act on programmatically. I’ve done this with single requests to services in the past, but I hadn’t seen the acceptable use requirements.

With a workflow I was currently working on I’d like to send multiple requests to a service and massage the JSON data returned. This multiple requests should be under any noticeable traffic amounts for the service, but it’s not a service I own/operate and I’m not sure how to interpret a ‘service I use’.

Thanks!

@KenMacD thanks for raising this and I can understand why the second section is confusing. The Acceptable Use section just means “don’t use the platform to abuse others”, e.g. you shouldn’t use Pipedream to launch a DOS attack on a service. But your use case sounds perfectly legitimate and using Pipedream to connect to another third-party service that you use is completely acceptable.

I’ll go ahead and remove the Acceptable Use section from that section of the docs, since this is covered under our Terms of Service.

1 Like