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. API Reference

Data stores

PreviousCustom properties > Structure itemsNextData stores > Data

Data stores are used to store data from scenarios or for transferring data in between individual scenarios or scenario runs. The following endpoints allow you to create and manage data stores.

Get data store details

get

Retrieves details of a data store with a given ID.

Authorizations
Path parameters
dataStoreIdintegerRequired

The ID of the data store. Get the dataStoreId from the List data stores endpoint.

Example: 137
Query parameters
Responses
200
Successful response
application/json
get
GET /api/v2/data-stores/{dataStoreId} HTTP/1.1
Host: eu1.make.com
Accept: */*
200

Successful response

{
  "dataStore": {
    "id": 137,
    "name": "Customers",
    "records": "0",
    "size": "0",
    "maxSize": "1048576",
    "teamId": 212
  }
}
  • GETList data stores
  • POSTCreate data store
  • DELETEDelete data stores
  • GETGet data store details
  • PATCHUpdate data store

List data stores

get

Retrieves a collection of all data stores for a team with a given ID. Returned data stores are sorted by name in ascending order.

Authorizations
Query parameters
teamIdintegerRequired

The unique ID of the team whose data stores will be retrieved.

Example: 1
pg[sortBy]string · enumOptional

The value that will be used to sort returned entities by.

Possible values:
pg[offset]integerOptional

The number of entities you want to skip before getting entities you want.

pg[sortDir]string · enumOptional

The sorting order. It accepts the ascending and descending direction specifiers.

Possible values:
pg[limit]integerOptional

The maximum number of entities you want to get in the response.

Responses
200
Successful response
application/json
get
GET /api/v2/data-stores HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
200

Successful response

{
  "dataStores": [
    {
      "id": 137,
      "name": "Customers",
      "records": "0",
      "size": "0",
      "maxSize": "1048576",
      "teamId": 212,
      "datastructureId": 123
    }
  ],
  "pg": {
    "sortBy": "name",
    "sortDir": "asc",
    "offset": 0,
    "limit": 10
  }
}

Create data store

post

Creates a new data store with data passed in the request body. In the response, it returns all details of the created data store.

Authorizations
Body
namestringRequired

The data store name. The name must be at most 128 characters long and does not need to be unique.

teamIdintegerRequired

The unique ID of the team in which the data store will be created.

datastructureIdintegerRequired

The unique ID of the data structure that will be included in the data store. All data structures IDs for a given team can be retrieved from the List data structures endpoint.

maxSizeMBintegerRequired

The maximum size of the data store (defined in MB).

Responses
200
Successful response
application/json
post
POST /api/v2/data-stores HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 69

{
  "name": "Customers",
  "teamId": 212,
  "datastructureId": 178,
  "maxSizeMB": 1
}
200

Successful response

{
  "dataStore": {
    "id": 137,
    "name": "Customers",
    "records": "0",
    "size": "0",
    "maxSize": "1048576",
    "teamId": 212
  }
}

Delete data stores

delete

Deletes data stores with given IDs and returns their IDs in the response. This endpoint allows deleting one or more data stores at once.

Authorizations
Query parameters
confirmedbooleanOptional

Confirms the deletion if a data store is included in at least one scenario. Confirmation is required because the scenario will stop working without the data store. If the parameter is missing or it is set to false an error code is returned and the resource is not deleted.

Example: true
teamIdintegerRequired

The unique ID of the team from which the data store will be deleted.

Example: 1
Body
one ofOptional
or
Responses
200
Successful response
application/json
delete
DELETE /api/v2/data-stores HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 18

{
  "ids": [
    137,
    1399
  ]
}
200

Successful response

{
  "dataStores": [
    137,
    1399
  ]
}

Update data store

patch

Updates properties of a data store with a given ID in a team with a given ID by passing new values in the request body. In the response, it returns all details of the updated data store including properties that were not changed. Any property that is not provided will be left unchanged. This endpoint cannot be used to update data included in the data store - for this use the endpoints for managing data stores data.

Authorizations
Path parameters
dataStoreIdintegerRequired

The ID of the data store. Get the dataStoreId from the List data stores endpoint.

Example: 137
Query parameters
teamIdintegerRequired

The unique ID of the team whose data stores will be retrieved.

Example: 1
Body
namestringOptional

The data store name. The name must be at most 128 characters long and does not need to be unique.

datastructureIdintegerOptional

The unique ID of the data structure included in the data store. All data structures IDs for a given team can be retrieved from the List data structures endpoint.

maxSizeMBintegerOptional

The maximum size of the data store (defined in MB).

Responses
200
Successful response
application/json
patch
PATCH /api/v2/data-stores/{dataStoreId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 57

{
  "name": "Data store 2",
  "datastructureId": 9,
  "maxSizeMB": 3
}
200

Successful response

{
  "dataStore": {
    "id": 137,
    "name": "Customers",
    "records": "0",
    "size": "0",
    "maxSize": "1048576",
    "teamId": 212
  }
}