Connect Cloudflare with Human Managed via API

huma
huma
  • Updated

This article covers the step-by-step procedure to send data such as User, Account, and Zone from your Cloudflare instance to the Human Managed platform via API.

 

Human Managed will establish a connection to pull Cloudflare data from your instance. Some parts of this this guide is derived from Cloudflare’s Developer Website.

 

connect diagram.png

 

Step 1: Create a service request for Human Managed to configure the API Receiver

  1. Submit a request 
  2. In the Subject, type or select Connect Cloudflare via API
  3. Once the ticket has been accepted by Human Managed and the ticket status has been updated, follow the next steps.

Step 2: Find your Cloudflare Zone and Account IDs

  1. Log in to the Cloudflare dashboard and select your account and domain.
  2. On the Overview page (the landing page for your domain), find the API section.

    cloudflare1.png
  3. The API section contains your Zone ID and Account ID. To copy these values for API commands or other tasks, select Click to copy.

    cloudflare2.png

Step 3: Create Cloudflare API Token

  1. From the Cloudflare dashboard, go to My Profile > API Tokens.
  2. Select Create Token.
  3. Select Read All Resources template from the available API Token Templates or create a custom token.
  4. Add or edit the token name to describe why or how the token is used. Templates are prefilled with a token name and permissions.

    cloudflare3.png
  5. Modify the token’s permissions. After selecting a permissions group (AccountUser, or Zone), choose what level of access to grant the token. Most groups offer Edit or Read options. Edit is full CRUDL (create, read, update, delete, list) access, while Read is the read permission and list where appropriate. You may refer to Cloudflare’s available token permissions for more information.
  6. Select which resources the token is authorized to access. For example, granting Zone DNS Read access to a zone example.com will allow the token to read DNS records only for that specific zone. Any other zone will return an error for DNS record reads operations. Any other operation on that zone will also return an error.
  7. (Optional) Restrict how a token is used in the Client IP Address Filtering and TTL (time to live) fields.
  8. Select Continue to summary.
  9. Review the token summary. Select Edit token to make adjustments. You can also edit a token after creation.

    cloudflare4.png
  10. Select Create Token to generate the token’s secret.
  11. Copy the secret to a secure place.
    cloudflare5.png

 

⚠️Warning: The token secret is only shown once. Do not store the secret in plaintext where others can access it. Anyone with this token can perform the authorized actions against the resources that the token has access to.

Step 4: Submit your credentials to Human Managed  

  1. In the same service request ticket you opened in Step 1, update the ticket with the following details:

     

    • Cloudflare Zone ID and Account ID – see Step 2

    To be added to Cloudflare Base URLhttps://api.cloudflare.com/client/v4/

    • Cloudflare API Token - see Step 3

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.