Skip to main content
The StoreRocket REST API lets you list your projects and create, read, update, and delete their locations. Location operations require a project with API access, available on the Business plan.

​
Base URL

Use an API token in the Authorization header. Send JSON request bodies with Content-Type: application/json. Accept: application/json is recommended; V2 errors return JSON even when it is omitted.
Project and location IDs are the public IDs returned by the API. Keep them as strings.

​
Endpoints

​
Use PATCH for partial updates

Fields you omit keep their saved values. A successful update returns 200 and the location. Invalid input returns 422 with field errors and saves no part of the update. POST and PUT retain their existing requirements, including name and city. PUT can replace supplied custom-field and call-to-action attachments and reset omitted marker/type selections to project defaults. Use PATCH when you want to preserve everything you leave out.

​
Locations without opening hours

Omit hours, or send "hours": {}, when creating a coming-soon location. Empty hours are accepted on POST, PUT, and PATCH; they leave any existing schedule unchanged. Use "hours": null with PATCH to remove an existing schedule. See opening hours for weekday updates and explicit clearing.

​
Rate limits

The current API uses a shared limit of 1,000 requests per minute. Read the response’s rate-limit headers. If a request returns 429, wait for the Retry-After interval before retrying. See errors.

​
Existing integrations

V1 remains a separate legacy contract. These pages do not change your existing URLs or require an API migration. The examples use placeholders. Replace YOUR_TOKEN, PROJECT_ID, and LOCATION_ID with your own values before running a request.