LogoLogo
Get support
  • Home
  • Make API
  • Make Bridge
  • White Label
  • MCP Server
  • Make API documentation
  • Getting started
    • Make API structure
    • HTTP methods
    • Making your first API request
    • Rate limiting
    • Resources
  • Authentication
    • Make roles and API scopes
    • Creating API token
    • Managing API token
    • Requesting an OAuth 2.0 client
    • OAuth 2.0 flow in the Make API
  • Pagination, sorting and filtering
    • Pagination and sorting
    • Filtering
  • Troubleshooting and error handling
    • HTTP status error codes
    • Troubleshooting
  • Client libraries
  • API Reference
    • Affiliate
    • Agents
    • Analytics
    • Audit logs
    • Cashier
    • Connections
    • Custom properties
    • Custom properties > Structure items
    • Data stores
    • Data stores > Data
    • Data structures
    • Devices
    • Devices > Incomings
    • Devices > Outgoing
    • Incomplete executions
    • Enums
    • Custom functions
    • General
    • Hooks
    • Hooks > Incomings
    • Hooks > Logs
    • Keys
    • Notifications
    • Organizations
    • Organizations > User organization roles
    • Remote procedures
    • Scenarios
    • Scenarios > Logs
    • Scenarios > Blueprints
    • Scenarios > Consumptions
    • Scenarios > Custom properties data
    • Scenarios folders
    • SDK Apps
    • SDK Apps > Invites
    • SDK Apps > Modules
    • SDK Apps > RPCs
    • SDK Apps > Functions
    • SDK Apps > Connections
    • SDK Apps > Webhooks
    • SSO certificates
    • Teams
    • Teams > User team roles
    • Templates
    • Templates > Public
    • Users
    • Users > Me
    • Users > API Tokens
    • Users > User team roles
    • Users > User team notifications
    • Users > User organization roles
    • Users > Roles
    • Users > Unread notifications
    • Users > User email preferences Mailhub
Powered by GitBook

Resources

  • Academy
  • Community
  • Help Center

Useful links

  • Support
  • Privacy Notice
  • Status Page
  • make.com

Follow us

  • LinkedIn
  • X (Twitter)
  • Facebook
  • Instagram

© 2025 make.com

On this page
Export as PDF
  1. Getting started

Making your first API request

PreviousHTTP methodsNextRate limiting

Last updated 4 months ago

This start guide will take you through making your first request to the Make API.

Example: Let's imagine that you would like to list all data stores available in your team. Your team ID is 35. Returned data should be ordered in descending order.

To make your first API call, you need to perform the following actions:

1

Create an authentication token. The token gives you access to Make API resources depending on your . You must include the token in the Authorization header of all requests. Add the word Token and a space before the token itself:

'Authorization: Token {Your authentication token}'
2

Choose the that corresponds to the resource you want to interact with. For this example, you need the /data-stores endpoint. The endpoint requires the teamId query parameter. Place the parameter after the question mark in the endpoint URL. To filter results, you also need the - pg[sortDir]:

{zone_url}/api/v2/data-stores?teamId={teamId}&pg%5BsortDir%5D=asc

The zone_url refers to the Make zone you interact with. For example, https://eu1.make.com.

3

Prepare the full request and send it. In this case, use cURL to making the request. You want to retrieve data without modifying it - use the GET method. Let's put elements from the previous steps together.

The following request example contains a sample authentication token. Don't use it in your requests. .

Request:

curl --location \
--request GET 'https://eu1.make.com/api/v2/data-stores?teamId=35&pg%5BsortDir%5D=asc' \
--header 'Content-Type: application/json' \
--header 'Authorization: Token 93dc8837-2911-4711-a766-59c1167a974d'

Response:

{
  "dataStores": [
    {
      "id": 15043,
      "name": "Old data store",
      "records": 10,
      "size": "620",
      "maxSize": "1048576",
      "teamId": 35
    },
    {
      "id": 13433,
      "name": "New data store",
      "records": 1,
      "size": "48",
      "maxSize": "1048576",
      "teamId": 35
    }
  ],
  "pg": {
    "sortBy": "name",
    "limit": 10000,
    "sortDir": "asc",
    "offset": 0
  }
}

Always include a request body in POST, PUT, or PATCH requests.

4

Evaluate the response. The API returns 200 OK and a list of all data stores for the specified team. If your request failed, you receive an error code. Refer to to troubleshoot the issue.

Make role and assigned scopes
endpoint
parameter for ordering data
Generate your own token
Troubleshooting and error handling