Cloudflare R2 | Operate As Docs

Connect your client's Cloudflare R2 with a key they paste, and call its API through Operate As.

Website: cloudflare.com/developer-platform/products/r2
Connects by: Pasting a Access key ID
Category: Files and docs
Services: 1
Tools: 77

Service	Key	Base URL
Cloudflare R2	`cloudflare-r2`	`https://{account_id}.r2.cloudflarestorage.com`

Your client also types their account id (In the Cloudflare dashboard, on the R2 overview page).

Connecting

Your client makes a Access key ID in their Cloudflare R2 settings and pastes it on their link. Operate As tries it with Cloudflare R2 before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "cloudflare-r2"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "cloudflare-r2"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Cloudflare R2 key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Cloudflare R2's typed package for your language:

pip install operate-as-cloudflare-r2

pip install operate-as-cloudflare-r2

Run cloudflare-r2.abort_multipart_upload

curl -X POST https://api.operate.as/v1/actions/cloudflare-r2.abort_multipart_upload \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "bucket": "<bucket>",
      "key": "<key>",
      "upload_id": "<upload_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/cloudflare-r2.abort_multipart_upload \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "bucket": "<bucket>",      "key": "<key>",      "upload_id": "<upload_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/cloudflare-r2.abort_multipart_upload

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://{account_id}.r2.cloudflarestorage.com, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../cloudflare-r2/" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../cloudflare-r2/" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Cloudflare R2. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}